Error Message |
Cause |
Solution |
Failed to connect to Enterprise Server: [IPaddress] or invalid session ID |
Bad proxy server settings |
Check the proxy server settings in the Axeda Access Viewer - Proxy Properties dialog. Adjust if incorrect. |
Failed to connect to Enterprise Server: [IPaddress] or invalid session ID |
Enterprise server down |
Check whether the Access Viewer computer can communicate with the Enterprise Server; try opening the Session Status page. If unable to communicate, inform your Platform Administrator. |
Failed to connect to Enterprise Server: [IPaddress] or invalid session ID |
Invalid session ID |
Request a new session. Copy the new session id from the Enterprise Server page, and paste it into the Axeda Access Viewer - New Connection dialog. |
Failed to connect to Enterprise Server: [IPaddress] or invalid session ID |
The Access Remote computer did not connect to the session within the defined timeout period. When this is the cause, this error message appears after an Enterprise Server user either views the status of all sessions, or attempts to create a session ID. |
Try connecting again later. Call the Access Remote asset site to ensure that the machine is running and their Internet connection is working. |
Axeda Access Viewer authentication failed, Invalid password |
Invalid password |
Request a new session, and try to connect again using the correct password. Contact the Access Remote operator to verify that you have the correct password. |
Unknown Axeda Access Viewer authentication result |
Invalid application versions. |
Check whether your version of Access Viewer is compatible with the installed version of Access Remote. Install the correct version of Access Viewer, if needed. You can download that program from the Access application, or obtain it from your Platform Administrator. |
Error Message |
Cause |
Solution |
Connection lost |
Enterprise Server shut down |
Check whether the Access Viewer computer can communicate with the Enterprise Server; try opening the Session Status page. If unable to communicate, inform your Platform Administrator. |
Connection lost |
The Access Remote computer stops communicating with the Enterprise Server. |
Check whether the asset running Access Remote still appears in the Manage Remote Hosts page. If yes, start a new session (and adjust your timeout period if necessary). If not, contact your Platform Administrator. |