Appendix: Jump Client Error Message Reference for Connect

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 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.

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 an 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 an representative console has attempted to Jump to that Jump Client before being notified.

The number of active Jump Clients has been reached. The build limit has been reached when changing from passive to active.
Jumping The server is currently too busy. Please try again later. More than twenty users 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.
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 cause 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 an 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 an representative console has attempted to Jump to that Jump Client before being notified.