Troubleshooting Thin Client Error Messages



July 2003

This document describes errors that may occur when installing and using ACUCOBOL-GT® Thin Client. The exact error messages vary depending on where they are displayed (server or client) and the server operating system (Windows NT Server, Windows 2000 Server or UNIX).

Alias Does Not Exist

Problem: Thin Client is unable to launch a server program and receives the error "connection failure, Alias does not exist".

Diagnostics: This error indicates a problem with the Alias file (acurcl.ini).

  • Verify that the Alias exists by performing an "acurcl -alias".
  • Ensure that the Alias file that is created is the same one that AcuRCL is using. If the file does not reside in the default directory, set the AcuRCL server configuration variable SERVER_ALIAS_FILE to the correct location.

Connection Failed

Problem: Thin Client fails to connect to the server with the error "connection failed" or "connection to server undefined".

Diagnostics: This message is seen when AcuRCL is not started correctly or when the client has not specified the correct port.

  • If not using the default port, ensure the port is specified in the acuthin command (e.g. "acuthin server:port alias").
  • Verify that you are using the correct IP address or server name.
  • Ensure that the Windows service or UNIX daemon is executing on the server by performing "acurcl -info".
  • On Windows servers, ensure the service is installed by performing "acurcl -query servername".
  • Verify that the client can communicate with the server by doing "ping servername" or "acuthin -p servername:port". If this fails, it would indicate a network configuration problem.
  • Verify that the client can communicate with AcuRCL by performing "acuthin -p servername:port.
  • Ensure that a valid AcuRCL configuration file is available and that the DEFAULT_USER is set.
  • If the previous checks are successful, check to determine if AcuRCL is generating errors. Stop AcuRCL on the server by performing "acurcl -kill" and restart AcuRCL with a log file "acurcl -start -le trace.log -t 7". Log files are very helpful in diagnosing AcuRCL errors.

Connection to Server Refused

Problem: Thin Client fails to connect to the server with the error "connection to server refused".

Diagnostics: This error is generated on all platforms for a variety of reasons, including setup, permissions and firewall issues.

  • On UNIX servers, check that the server name is specified in the hosts file, located in the /etc/hosts directory. The UNIX command "uname -a" will identify the server name (e.g. AIX rs6000 3 4 000168871000) and the hosts file should contain an entry for "rs6000".
  • Ensure that version of the runtime, AcuRCL and Acuthin are the same.
  • Follow the diagnostic steps outlined in the Connection Failed Error.
  • If you suspect a firewall problem, refer to the General Socket Error.

Connection to Server Refused, Error 267

Problem: Thin Client fails to connect to the server with the error "connection to server refused, error 267".

Diagnostics: Error 267 in Windows environment means Invalid Directory. An invalid directory path/name or inadequate permissions on one of the directories or sub directories causes this error.

  • Ensure the working directory specified in the Alias entry is correct.
  • Check the permissions for all leading directories to both the runtime and object files.
  • Check the AcuRCL configuration file (acurcl.cfg) to ensure the correct path specification is set for SERVER-RUNTIME. This must be set if the remote runtime is installed in a different directory than AcuRCL.

Exceeded Licensed Number of Users

Problem: Unable to start a server runtime and are receiving the warning message "exceeded licensed number of users".

Diagnostics: This error indicates a licensing restriction or an orphan runtime condition.

  • To determine the maximum number of licensed AcuRCL users, perform "acurcl -v". To determine the maximum number of licensed runtime users, perform "wrun32 -v" in Windows environments or "runcbl -v" in UNIX environments.
  • On UNIX, AcuShare will identify the number of runtime users currently on the system. AcuRCL handles its user count internally. Suppose you own a license for 35 users of the runtime and 15 users of AcuRCL. If you reach the AcuRCL limit with Thin Client connections and perform an "acushare -info" you will see 15 users. In this situation, you are correctly receiving this error due to reaching AcuRCL's license limit, although 20 runtime instances are still available.
  • In Windows, check the number of runtime users currently on the system using the Task Manager, Process tab.
  • Orphan runtimes result when a program terminates abnormally. When AcuRCL determines that a socket has closed, it will terminate any runtime process associated with the socket. It assumes that there might be a resulting orphan runtime process under these conditions. Use the command "acurcl -kill -p pid", where PID is the Process Id of the child runtime that was orphaned through abnormal termination, to terminate orphan processes.

Failed to start a runtime: chdir() failed (error 2)

Problem: Inability to launch server application.

Diagnostics: This error indicates a problem with the working directory on a UNIX server. The Change Directory command failed to execute. When the AcuRCL spawns a runtime, it changes to the directory specified as the working directory in the Alias entry.

  • Ensure that the working directory exists that is specified for the Alias and that the correct permissions have been set.

Failed to start a runtime exec (): (error 8)

Problem: Inability to launch server application.

Diagnostics: This error indicates the inability to launch server runtime on a UNIX server.

  • Check the AcuRCL configuration file (acurcl.cfg) to ensure the correct path specification is set for SERVER-RUNTIME. This must be set if the remote runtime is installed in a different directory than AcuRCL.
  • The permissions for the runtime should be executable.

Failed to start a runtime: chdir() failed (error 13)

Problem: Inability to launch server application.

Diagnostics: This error indicates a permissions problem on the working directory on a UNIX server. The Change Directory command failed to execute.

  • Ensure that the Alias has Execute permissions on the working directory.
  • Ensure that version of the runtime, AcuRCL and Acuthin are the same.

General Socket Error

Problem: Thin Client fails to connect to the server with the error connection failed "general socket error".

Diagnostics: A General Socket error is generated because of AcuRCL setup and firewall issues.

  • Follow the diagnostic steps outlined in the Connection Failed Error for setup issues.
  • SOCKS is a protocol that a proxy server can use to accept requests from client users in a company's network so that it can forward them across the Internet. The most common type of proxy server is a SOCKS proxy. Thin Client will not automatically connect through a SOCKS proxy. This is typical of many applications that communicate using TCP Sockets. With proxy servers, there is a need to wrap the commands to get past the proxy permissions. Third-party tools are available that allow client applications to connect through proxy servers. See SocksCap at http://www.socks.nec.com/reference/sockscap.html, or Hummingbird SOCKS at http://www.hummingbird.com/products/nc/socks/index.html.

No Entry for Product AcuRCL or AcuRCL.alc Inaccessible

Problem: AcuRCL fails to start and performing "acurcl -v" returns the error "no entry for product acuRCL".

Diagnostics: This error indicates a licensing problem.

  • Ensure the correct product code and key were entered when using the Activator license utility.
  • Ensure the Activator license utility has created the license file acurcl.alc.
  • Verify that the version of AcuRCL on the server is the same version as Thin Client on the client PC.

Service Error 3

Problem: When the "acurcl -start" command is performed on a Windows server, the error "AcuRCL Service Error: 3" is displayed and AcuRCL fails to start.

Diagnostics: This error is encountered when upgrading to a newer version of AcuRCL without removing the prior service.

  • Perform "acurcl -remove" to remove Windows service from memory and then start the new version "acurcl -start". If not using the default port, indicate the port number when removing and starting the service: "acurcl -remove -n portnumber" and "acurcl -start -n portnumber".

Service Error 997

Problem: When the "acurcl -start" command is performed at the Command Prompt on a Windows server, the error "AcuRCL Service Error: 997" is displayed and AcuRCL fails to start.

Diagnostics: This error is encountered when upgrading to a newer version of AcuRCL without removing the prior service.

  • Perform "acurcl -remove" to remove Windows service from memory and then start the new version "acurcl -start". If not using the default port, indicate the port number when removing and starting the service: "acurcl -remove -n portnumber" and "acurcl -start -n portnumber".
  • This error may also indicate an expired evaluation license.

Socket Error 10102

Problem: The commands "acurcl -info" or "acurcl -kill" generate a "socket error 10102".

Diagnostics: Error 10102 is displayed on UNIX operating systems and stands for "unknown error".

  • The most common cause is that the server's machine name is not the same as the host-name. The UNIX command "uname -a" will identify the server name (e.g. AIX rs6000 3 4 000168871000) and the hosts file should contain an entry for "rs6000".
  • Ensure that server and client have different IP addresses.

Unable to start remote process

Problem: Thin Client fails to launch server program and the error "connection failed, unable to start remote process" is displayed.

Diagnostics: This error is caused by permissions, system resources and other reasons.

  • Ensure that the working directory specified for the Alias exists and that the correct permissions are set.
  • Check the AcuRCL configuration file (acurcl.cfg) to ensure the correct path specification is set for SERVER-RUNTIME. This must be set if the remote runtime is installed in a different directory than AcuRCL.
  • Ensure that the remote runtime has a valid runtime license.
  • If many instances of the server application are running successfully, this indicates a lack of resources on the server.
Your Session will expire in 90 minutes
Notification will be shown in:
600 seconds