Skip to content

Sockets Errors

Sockets errors appear onscreen and in the log file. If tracing is enabled, messages are also 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, error=number(errortext)

The Client is unable to connect to the Databridge server. 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?
  • If you use DBEnterprise Server, is the DBDirector service running?

SOCKETS ERROR: getaddrinfo call failed, error=number (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: gethostname call failed, error=number (errortext)

This message when DBClient or DBClntCfgServer tries to get the host name when trying to connect to the service. This is an internal that should never occur. If it does contact Micro Focus support.

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, error=number (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. The errortext that is provided should help clarify what happened.

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: select timed out after sss seconds for server connection

This message appears when the Client is starting up a connection to the Databridge server. We use an echo RPC to determine if the line is operational or not. We use a sockets select call to timeout the receipt of the response to the ATM_Echo RPC. When you get no data after the prescribed timeout period you will see this message. Normally, the client does not immediately give up, it tries to recover from this error.

SOCKETS ERROR: send call failed for {server | console} connection, error=number (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. The errortext that is provided should help clarify what happened.

SOCKETS ERROR: setsockopt(SO_KEEPALIVE) call failed for TCP port, error=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 alive.

SOCKETS ERROR: socket call failed, error=number (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. The errortext that is provided should help clarify what happened.

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 Micro Focus Technical Support.