Knowledgebase

Clients Lose Connection to Server

A connected client may lose its connection to FairCom DB for various reasons. If a client loses its connection to the server, subsequent calls to FairCom DB functions that send requests to the server return an error indicating that the connection has been lost. The topics below list errors a FairCom DB API function may return in the event of a lost connection and describes possible causes and troubleshooting steps for each:

In This Section FairCom DB Error 7: TUSR_ERR FairCom DB Error 127: ARQS_ERR FairCom DB Error 128: ARSP_ERR FairCom DB Error 150: SHUT_ERR FairCom DB Error 162: SGON_ERR

FairCom DB Error 7: TUSR_ERR

Error description:
Terminate user. FairCom DB or server administrator has terminated the client’s connection to the server.

Possible causes:

1. An administrator may have terminated the client connection.
2. FairCom DB may have terminated the client connection (for example, when the server is shutting down or when the server aborts a transaction).

Troubleshooting steps:
Examine CTSTATUS.FCS to determine the reason the connection was terminated. See the discussion of FairCom DB error 127 for additional details about reconnecting to FairCom DB after a client connection is terminated.

FairCom DB Error 127: ARQS_ERR

Error description:
Could not send request. A communication error occurred while sending a request to the server.

Possible causes:

1. The server may have shut down.
2. The server may have terminated abnormally.
3. An administrator may have terminated the client connection.
4. A network error may have occurred that terminated the connection to the server.

Troubleshooting steps:

1. Verify that the server is operational. Restart the server if it is not operational.
2. When a client loses its connection to FairCom DB and the server detects the lost connection, the server aborts the client’s active transaction (if any) and closes any files that the client had open. If the server is still operational, use the ctadmn utility to confirm that the server thread for the lost connection has been terminated. If necessary, terminate the old connection using ctadmn.
3. To determine if the connection was terminated by an administrator, check CTSTATUS.FCS for messages of the form:

External kill request posted against user #<taskID>

where <taskID> is a server-assigned thread task ID.

1. Attempt to reconnect to the server.
2. If this communication error occurs at logon time, consider using the DIAGNOSTICS LOGON_COMM server configuration keyword to monitor logon process as described in the discussion of FairCom DB error 133.
3. If this communication error occurs frequently without explanation (for example, connections are lost but FairCom DB remains active), investigate the possibility of network connectivity errors.

FairCom DB Error 128: ARSP_ERR

Error description:
Could not receive answer. A communication error occurred while receiving a response from the server.

Possible causes and troubleshooting steps:
The possible causes and troubleshooting steps are the same as for error 127.

FairCom DB Error 150: SHUT_ERR

Error description:
Server is shutting down. The client connected to the server but the server closed the connection.

Possible causes:
FairCom DB is refusing new connections because it is in the process of shutting down.

Troubleshooting steps:
Check the status of FairCom DB process. Restart the c tree Server if necessary. When the server is operational, retry the connection attempt.

FairCom DB Error 162: SGON_ERR

Error description:
Server has gone away. The client connected to the server but the server closed the connection.

Possible causes and troubleshooting steps:
The possible causes and troubleshooting steps for this error are the same as described for FairCom DB error 150.