Session Connection Errors Codes

If you are attempting to Connect to a remote host and receiving a connection error code, then this typically means that PAM was unable to connect with the remote host by one of the reasons. We use a common set of numeric status codes. These codes denote success or failure of operations, and can be rendered by user interfaces in a human-readable way.

0 (SUCCESS)

The operation succeeded. No error.

256 (UNSUPPORTED)

The requested operation is unsupported.

512 (SERVER_ERROR)

An internal error occurred, and the operation could not be performed.

513 (SERVER_BUSY)

The operation could not be performed because the server is busy.

514 (UPSTREAM_TIMEOUT)

The upstream server is not responding. In most cases, the upstream server is the remote desktop server.

515 (UPSTREAM_ERROR)

The upstream server encountered an error. In most cases, the upstream server is the remote desktop server.

516 (RESOURCE_NOT_FOUND)

An associated resource, such as a file or stream, could not be found, and thus the operation failed.

517 (RESOURCE_CONFLICT)

A resource is already in use or locked, preventing the requested operation.

518 (RESOURCE_CLOSED)

The requested operation cannot continue because the associated resource has been closed.

519 (UPSTREAM_NOT_FOUND)

The upstream server does not appear to exist, or cannot be reached over the network. In most cases, the upstream server is the remote desktop server. Troubleshooting.

520 (UPSTREAM_UNAVAILABLE)

The upstream server is refusing to service connections. In most cases, the upstream server is the remote desktop server.

521 (SESSION_CONFLICT)

The session within the upstream server has ended because it conflicts with another session. In most cases, the upstream server is the remote desktop server.

522 (SESSION_TIMEOUT)

The session within the upstream server has ended because it appeared to be inactive. In most cases, the upstream server is the remote desktop server.

523 (SESSION_CLOSED)

The session within the upstream server has been forcibly closed. In most cases, the upstream server is the remote desktop server.

768 (CLIENT_BAD_REQUEST)

The parameters of the request are illegal or otherwise invalid.

769 (CLIENT_UNAUTHORIZED)

Permission was denied, because the user is not logged in. Note that the user may be logged into PAM, but still not logged in with respect to the remote desktop server.

771 (CLIENT_FORBIDDEN)

Permission was denied, and logging in will not solve the problem.

776 (CLIENT_TIMEOUT)

The client (usually the user of PAM or their browser) is taking too long to respond.

781 (CLIENT_OVERRUN)

The client has sent more data than the protocol allows.

783 (CLIENT_BAD_TYPE)

The client has sent data of an unexpected or illegal type.

797 (CLIENT_TOO_MANY)

The client is already using too many resources. Existing resources must be freed before further requests are allowed.