Appendix: Jump Client Error Message Reference

This appendix provides a reference for error messages that may occur while working with Jump Clients. Below is a list of actions that may take place with Jump Clients along with error messages that may occur during each action. Each error message is accompanied by a brief description.

Action Error Message Explanation and Reproduction Notes
Pinning a Jump Client from within a Session The total number of deployable Jump Clients for this site has been reached.

The build limit has been reached.

The total number of deployable active Jump Clients for this site has been reached.

The build limit has been reached.

The total number of deployable passive Jump Clients for this site has been reached.

The build limit has been reached.

The support session already has a pending request to pin.

Race condition (Reproduction is UI-limited).

The support client is already pinned.

Race condition (Reproduction is UI-limited).

No customer could be found within the support conference.

Race condition (Reproduction is UI-limited).

The customer within the support conference is not online.

Race condition (Reproduction is UI-limited).

Deploying a Jump Client from the Mass Deployment Wizard The total number of deployable Jump Clients for this site has been reached.

The build limit has been reached.

The total number of deployable active Jump Clients for this site has been reached.

The build limit has been reached.

The total number of deployable passive Jump Clients for this site has been reached.

The build limit has been reached.

The associated Jumpoint is not currently online. The Jumpoint designated as the Jumpoint Proxy is offline before mass deployment is generated.
The associated Jumpoint-proxy no longer exists. The Jumpoint designated as the Jumpoint Proxy is deleted before mass deployment is generated.
Bad Password: The password must contain at least __ characters and contain at least one uppercase letter, one lowercase letter, one number, and one special character. The password designated for the Jump Client does not meet security standards. (Reproduction is UI-limited.)
Bad Password: The password must contain at least __ character(s). The password designated for the Jump Client does not meet security standards. (Reproduction is UI-limited.)
Taking an Action on a Jump Client besides Jumping (Set Comments, etc.) The Jump Client does not exist. Race condition: A Jump Client has been deleted, but another representative console has attempted to Jump to that Jump Client before being notified.
The Jump Client is offline. Race condition: A Jump Client has gone offline, but a representative console has attempted to Jump to that Jump Client before being notified.
The specified Jump Client has been uninstalled. Race condition: A Jump Client has been uninstalled, but a representative console has attempted to Jump to that Jump Client before being notified.
The password is incorrect. The provided password is incorrect.
The number of active Jump Clients has been reached. The build limit has been reached when changing from passive to active.
The number of passive Jump Clients has been reached. The build limit has been reached when changing from active to passive.
Bad Password: The password must contain at least __ characters and contain at least one uppercase letter, one lowercase letter, one number, and one special character.

The password designated for the Jump Client does not meet security standards.

Bad Password: The password must contain at least __ character(s).

The password designated for the Jump Client does not meet security standards.

Jumping Permission denied joining existing support session. Simultaneous representative access to a Jump Client is disabled while Jumping into a Jump Client which already has a session. This permission is controlled by the Allow simultaneous representative access to a single Jump Client setting under /login > Configuration > Jump Clients :: Jump Client Settings.
The server is currently too busy. Please try again later. More than twenty representatives are starting sessions at the same time on different Jump Clients.
An internal error occurred while spawning the support session. Internal for active Jump Client starts.
An internal operation was taking too long while trying to spawn a support session. Internal for active Jump Client starts.
The active Jump Client is not connected. Race condition: An active Jump Client disconnected before the representative console was notified.
Timeout while trying to connect to the Jump Client. Took too long to connect to any of the hostnames or IPs.
Failed to connect to the Jump Client. Could not connect to any IP address or hostname of a passive Jump Client.
Timeout while communicating with the Jump Client. Timeout during a passive connect handshake.
The Jump Client sent a bad protocol version. The Jump Client has informed the server of a protocol version error during a passive connect handshake.
The Jump Client identification check failed. This may indicate that a new system has obtained the network address of the Jump Client you are attempting to access. Or, there is possibly more than one passive Jump Client deployed to the system, and only one of them can acquire the listen port (____) at a time. The server was able to connect and handshake, but the Jump Client gave the wrong identification token, meaning that it is not the Jump Client you are attempting to reach or that the Jump Client has lost its token.
The Jump Client has been disabled by the user and will not allow a session to start at this time. The Jump Client has been disabled on the remote computer.
The Jump Client is running a different version and will not attempt to upgrade. Please try again after the upgrade completes. Bomgar version mismatch. This should case a check-in, which causes an upgrade.
The Jump Client does not exist. Race condition: A Jump Client has been deleted, but another representative console has attempted to Jump to that Jump Client before being notified.
The Jump Client is offline. Race condition: A Jump Client has gone offline, but a representative console has attempted to Jump to that Jump Client before being notified.
The specified Jump Client has been uninstalled. Race condition: A Jump Client has been uninstalled, but a representative console has attempted to Jump to that Jump Client before being notified.
The password is incorrect. The provided password is incorrect.