ConnectR Outbound Interface Connectivity Errors

There are a number of error codes that may appear in the message log for outbound interfaces in ConnectR that generally indicate some sort of connectivity issue with the target system. These errors are often caused by just a blip in connectivity and may not be of concern. However, if these errors are frequently occuring and causing issues with an interface it may require troubleshooting the network connectivity with the target vendor.

Below are a few of the error codes commonly seen and brief details about the error codes.

• Error Code 10054 is a winsock error.
  • Connection reset by peer.
  • An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close.

• Error Code 10053 means that an established connection has been dropped.
  • Software caused connection abort.
  • An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error.

• Error Code 10038
  • Socket operation on nonsocket.
  • An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.