Error messages | PRA

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
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 associated Gateway is not currently online.	The Gateway designated as the Gateway Proxy is offline before mass deployment is generated.
The associated Gateway-proxy no longer exists.	The Gateway designated as the Gateway Proxy is deleted before mass deployment is generated.
Taking an Action on a Jump Client besides connecting (Set Comments, etc.)	The Jump Client does not exist.	Race condition: A Jump Client has been deleted, but another access console has attempted to connect to that Jump Client before being notified.
The Jump Client is offline.	Race condition: A Jump Client has gone offline, but an access console has attempted to connect to that Jump Client before being notified.
The specified Jump Client has been uninstalled.	Race condition: A Jump Client has been uninstalled, but an access console has attempted to connect to that Jump Client before being notified.
Connecting	Permission denied joining existing access session.	Simultaneous user access to a Jump Client is disabled while connecting into a Jump Client which already has a session. The simultaneous connections permission is managed either through an Asset Policy on > Asset Policies or by the global setting configured under > Assets > Asset Settings.
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 access session.	Internal for active Jump Client starts.
An internal operation was taking too long while trying to spawn an access session.	Internal for active Jump Client starts.
The active Jump Client is not connected.	Race condition: An active Jump Client disconnected before the access 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 identification check failed. This may indicate that a new system has obtained the network address of the Jump Client you are attempting to access.	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. Try again after the upgrade completes.	BeyondTrust 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 access console has attempted to connect to that Jump Client before being notified.
The Jump Client is offline.	Race condition: A Jump Client has gone offline, but an access console has attempted to connect to that Jump Client before being notified.
The specified Jump Client has been uninstalled.	Race condition: A Jump Client has been uninstalled, but an access console has attempted to connect to that Jump Client before being notified.

⚠️
Important
When upgrading to a newly built site software package, verify that all certificate stores are managed appropriately and are up-to-date prior to upgrading to a new BeyondTrust version. Failure to do so may cause a majority of your existing Jump Clients to appear offline.

Updated about 2 months ago