Sockets Error Messages

Sockets error messages appear onscreen. These messages are also written to the log file. If tracing is enabled, these messages are captured in the trace file. See Log and Trace Files.

Sockets errors typically indicate the following:

• LAN problems
• Host TCP/IP problems (for example, you have reached the maximum TCP/IP session quota)

SOCKETS ERROR: connect call failed, errno = ddd (errortext)

The Client is unable to connect to the DATABridge Server Accessory. In this case, check the following:

• Did you enter the correct host name or IP address?
• Did you enter the correct port number? The port number you enter must match the port number as it is defined in the Server Accessory parameter file.
• Is the host running? If so, is DATABridge Engine and the Server Accessory running?

gethostbyname call failed, errno = ddd (errortext)

Make sure that you entered the correct host name and set up your domain name resolution parameters correctly in your Windows Network folder (in control panel). Check that the domain name server is running. If the domain name server is down, change the host name in the DATASOURCES table to the IP address and try the dbutility command again.

recv call detected a closed connection

This message appears when the Client is reading TCP data, and indicates that the Client received an abnormal status that indicates the connection to the Server Accessory is closed.

recv call failed, errno = ddd (errortext)

This message can occur during a define, process, clone, or switchaudit command. It indicates that the Client encountered an error while receiving data. This error typically occurs when the Server Accessory aborts or resets the TCP/IP connection. In your Winsock documentation, look up the error code indicated by ddd.

recv call returned 0 after select reported data available

This message, which only occurs when the connection to the Server Accessory is being initialized, indicates that the Client could not obtain the requested data. This occurs only when the Server Accessory closes the connection.

send call failed, errno = ddd (errortext)

This message can occur during a define, process, clone, or switchaudit command. It indicates that the Client encountered an error while sending data. This error typically occurs when the Server Accessory aborts or resets the TCP/IP connection. In your Winsock documentation, look up the error code indicated by ddd.

setsockopt(SO_KEEPALIVE) call failed for TCP port, errno=number (errortext)

This message, which can occur during any command that involves a TCP/IP connection, indicates that the Client was unable to set the keep-alive option for the socket. The keep alive option is deigned to force a message to be sent on idle connection so that the Client can determine if the connection is still alive.

socket call failed, errno = ddd (errortext)

This message can occur at the beginning of a define, process, clone, or switchaudit command. It indicates a problem in the Windows sockets software. In your Winsock documentation, look up the error code indicated by ddd.

WSAStartup error ddd

This message applies only to the Windows Client. This message can occur at the beginning of a define, process, clone, or switchaudit command. It indicates that the Windows sockets software is incompatible with that used by the Client.

In your Winsock documentation, look up the error code indicated by ddd. If you cannot resolve the problem, contact Attachmate Technical Support.