Error messages are produced in a thin client environment as a result of the following basic scenarios: AcuConnect cannot be started, a server connection cannot be made, or a remote application cannot be started via AcuConnect. See AcuConnect Error Messages for the messages generated when AcuConnect cannot be started. The following table provides links to the messages in the other two categories.
If you try to connect to a Windows server, limitations in Windows can prevent a child runtime from starting, resulting in a "Connection failed" error message. See Diagnosing Connection Refused Errors on a Windows Server to help determine whether you have reached this Windows limit and how to work around it.
| Connection failed. General socket error. | A server connection cannot be established, possibly because of a busy socket. |
| Connection failed. Connection to server refused. | A server connection cannot be established. Specific reasons for this error message include a missing or invalid license file (acurcl.alc), an AcuAccess file that is missing or not allowing access for this particular user, or the use of a port number that is not available for some reason. |
| Connection failed. Alias does not exist. | A server connection cannot be established, because an alias file does not exist or the alias file does not contain the requested alias. |
| Connection failed. Unknown error. | Invalid working directory is specified in your alias file (when running on VMS). |
| Connection failed. Server failed to start remote process. Check messages on the server. | Invalid error file path and/or name in the alias file. |
| prog-name: Program missing or inaccessible. | The specified remote application could not be started. |
| You have exceeded the licensed number of users for ACUCOBOL-GT. If you would like to add users, please contact your customer service representative. | Indicates that the maximum number of runtime users in thin client has been exceeded. |