CBI Consulting

Communication Errors -30081

TCP/IP - Windows(winsock2.h)

WSAEINVAL	10022	Invalid argument. It can also mean that the current state of the socket is not compatible with TCP function being called, or the socket may no longer be valid.
WSAEMFILE	10024	Too many open files. Too many open sockets. Each implementation may have a maximum number of socket handles available, either globally, per process, or per thread.
WSAEWOULDBLOCK	10035	Resource temporarily unavailable. This error is returned from operations on non-blocking sockets that cannot be completed immediately.
WSAEINPROGRESS	10036	A blocking Windows Sockets operation is in progress. Window Sockets only allows a single blocking operation to be outstanding per task(or thread), and if other function call is made, the function fails with WSAEINPROGRESS.
WSAENOPROTOOPT	10042	Bad protocol option. An unknown, invalid, or unsupported option or level was specified in a getsockopt() or setsockopt() call.
WSAEADDRINUSE	10048	Address already in use. Only one usage of each socket address(protocol/IP address/port) is normally permitted. This error occurs if an application attempts to bind() a socket to an IP address/port that has already been used for an existing socket, or a socket that wasn't closed properly, or one that is still in the process of closing.
WSAENETDOWN	10050	Network is down. A socket operation encountered a dead network. This could indicate a serious failure of the network system(i.e. the protocol stack that the WinSock DLL runs over), the network interface, or the local network itself.
WSAENETUNREACH	10051	Network is unreachable. A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host.
WSAENETRESET	10052	Network dropped connection on reset. The connection has been broken due to "keep-alive" activity detecting a failure while the operation was in progress. May also be returned by stsockopt() if an attempt is made to set SO_KEEPALIVE on a connection that has already failed.
WSAECONNABORTED	10053	Software caused connection abort. An established connection was aborted by the software on your machine, possibly due to a data transmission timeout or protocol error.
WSAECONNRESET	10054	Connection reset by peer. An existing connection was forcibly closed by the remote peer. This normally results if the peer application on the remote machine is suddenly stopped, the machine is rebooted, or the peer application is used a "hard close" on the remote socket. This error may also result if a connection was broken due to "keep-alive" activity detecting a failure while one or more operations are in progress. Operations in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.
WSAENOBUFS	10055	No buffer space available. An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
WSAENOTCONN	10057	The socket is not connected.
WSAETIMEDOUT	10060	Connection timed out. A connection attempt failed because the connected party did not properly respond after a period of time.
WSAECONNREFUSED	10061	The connection has been refused. If you are trying to attach to the instance or connect to the database, check that the database manager and TCP/IP protocol support at the server has been started successfully.
WSAEHOSTUNREACH	10065	No route to host. A socket operation was attempted to an unreachable machine.
WSASYSNOTREADY	10091	The underlying network subsystem is not ready for network communication. User should check that the appropriate Windows Sockets DLL is in the current path and that they are not trying to use more than one WinSock implementation simultaneously. If there is more than one WinSock DLL on your system, be sure the first one in the path is appropriate for the network subsystem currently loaded and that all necessary components are currently installed and configured correctly.
WSAVERNOTSUPPORTED	10092	The version of Windows Sockets API support requested is not provided by this particular Windows Sockets implementation. Check that no old Windows Sockets DLL files are being accessed.
WSAE_E_NO_MORE	10110	There is no more data available. In Windows Sockets Version 2, conflicting error codes are defined for WSAENOMORE and WS_E_NO_MORE. The errorcode WSAENOMORE will be removed in future version and only WSA_E_NO_MORE will remain.
WSAENOMORE	10102	There is no more data available. In Windows Sockets Version 2, conflicting error codes are defined for WSAENOMORE and WS_E_NO_MORE. The errorcode WSAENOMORE will be removed in future version and only WSA_E_NO_MORE will remain.
WSAHOST_NOT_FOUND	11001	Host not found.
WSATRY_AGAIN	11002	Host not found. Request to retrieve the hostname's IP address from the nameserver failed because the local machine did not receive a response from the name server.
WSANO_DATA	11004	Valid name, no data record of requested type. The name server or hosts file does not recognize the hostname, or the service name is not specified in the services file.