Product Documentation

Database Administrator's Guide

Previous Topic

Next Topic

Communications Errors (127/128)

When a communication error such as VDP_ERROR (127 or 128) occurs, the FairCom Server logs an entry in the Server Status Log CTSTATUS.FCS. This is not a serious situation unless the client application is also getting errors such as 127, 128, or similar errors.

The context of the communications error is that a server thread gets a notification that a message is available, but when the server performs a read, nothing is returned.

This can be caused by:

  • Physical network problems
  • An overworked network transport layer that is timing out and doing retries
  • Clients exit without calling CloseISAM() or StopUser(), or end users that turn their machines off without properly logging out of the application. This category includes client application crashes.

To ensure the errors are not serious, try to reconcile the communications errors in the log with the client events that triggered them. Since these errors do not usually happen frequently and user names are provided, it should be easy to determine which event caused this situation.

To avoid these errors, ensure the FairCom Server’s host machine is not burdened beyond its capacity. Using a more powerful machine or limiting the number and types of applications on a machine can improve performance and limit errors at the communication level. Also, ensure no specific application is over-using resources on the host machine. If appropriate in the server's operating environment, increasing the priority of the FairCom Server can eliminate or reduce communications errors. This should be done cautiously as it will affect other applications running on the same machine.

The error messages in the Server Status Log can be turned off, but unless they are an inconvenience, this is NOT recommended. The messages serve as a good health check on the state of your network and may be an early warning of more serious network and system problems. To disable the messages, add


to the ctsrvr.cfg file and restart the FairCom Server.