Integrations hub error codes

101

The integration stopped and can no longer sync.

This error occurs when GravityZone tries to sync an integration that was stopped.

To resolve this issue, start the integration from the Integrations hub page.

103

A valid license is required to use this feature.

This error occurs when the user or company does not have a valid license for this feature.

To resolve this issue, add a valid license.

104

The BEST agent used as an integrator cannot be found or no longer exists.

This issue occurs when the BEST agent that's set as the integrator can't be found.

To resolve the issue, make sure the endpoint is still managed and turned on. If it's not available, set a different endpoint as the integrator.

107

The integration is a duplicate and cannot be synchronized.

This error occurs when an integration with the same configuration already exists, preventing synchronization of the duplicate.

To resolve this issue, you must remove or update the duplicate integration.

108

Integration instance mismatch.

This issue occurs when the vCenter server address has been changed in the vCenter profile card.

To resolve this issue, make sure the information on the vCenter profile card is correct.

4001

The integration has been stopped.

This message is displayed when a user stops the integration in the GravityZone Console.

4003

There was an issue connecting to the integration.

This error occurs when the integrator can't connect to the integration server due to a network issue.

To resolve the issue, check your network connection.

If the issue continues after verifying your connection, contact support.

4004

The integration's certificate could not be verified.

This error occurs when the integrator’s certificate could not be verified.

To fix this issue, make sure that the endpoint has installed the certification authority (CA) that issued the certificate.

4008

The system you're integrating with uses an unsupported API version.

This error occurs when the vCenter server uses an API version that isn't compatible with the integrator. As a result, the integrator can't retrieve inventory data or receive updates from the server.

To fix this issue, make sure that the vCenter version is supported.

4009

The integration credentials are invalid.

This error occurs when the integration credentials entered for the integration are invalid.

To resolve the issue, check that your credentials are correct.

If the issue continues after verifying your credentials, contact support.

4051

The maximum number of integrations has been reached.

This error occurs when the maximum number of integrations has been reached for the integration associated with this profile card.

4101

The GravityZone service or proxy connection has failed.

This error occurs when the integrator can't connect to GravityZone due to a network issue, a problem with the GravityZone service, or a proxy connection failure.

To resolve the issue, check the network connection on the endpoint set as the integrator.

4102

The GravityZone service host or proxy name resolve has failed.

This error occurs when the integrator can't report the collected inventory because it can't resolve the GravityZone service host or proxy name.

To resolve the issue, check the network connection on the endpoint set as the integrator.

4103

Connection to the GravityZone service has timed out.

This error occurs when the connection to the GravityZone services times out.

To resolve the issue, make sure the GravityZone IP or address is whitelisted.

For more information, refer to GravityZone (cloud) communication ports.

If the issue continues after whitelisting the IP or address, contact support.

5000

The integration is no longer linked to an integrator.

This issue occurs when the integrator is unassigned or deleted.

To resolve the issue, select a new integrator.

5001

The connection to the integrator has been lost.

This issue occurs when GravityZone detects that the integrator is offline.

To resolve the issue, make sure the integrator is turned on.