Sockets Errors

Sockets errors appear onscreen and in the log file. If tracing is enabled, messages are captured in the trace file.

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 DBServer. 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 DBServer parameter file.

Is the host running? If so, is DATABridge Engine and DBServer running?

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

This message appears when the Client cannot resolve any of the host names supplied to the Client via the define command. Check the following:

Did you enter the correct host name?

If you entered the host name, did you set up your domain name resolution parameters correctly in the Windows Network folder (in control panel)?

If you entered the host name, is the domain name server running? If the domain name server is down, change the host name in the DATASOURCES table to the IP address and try the command again.

SOCKETS ERROR: recv call detected a closed { server | console } 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 DBServer is closed.

SOCKETS ERROR: recv call failed for { server | console } connection, 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 DBServer aborts or resets the TCP/IP connection. In your Winsock documentation, look up the error code indicated by ddd.

SOCKETS ERROR: recv call returned 0 after select reported data available

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

SOCKETS ERROR: send call failed for { server | console } connection, 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 DBServer aborts or resets the TCP/IP connection. In your Winsock documentation, look up the error code indicated by ddd.

SOCKETS ERROR: 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. When the connection is idle, the keep-alive option prompts a message to be sent so that the Client can determine if the connection is still live.

SOCKETS ERROR: 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.

SOCKETS ERROR: 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.