Microsoft Winsock Errors Unfortunately, there is currently no routine that translates Windows socket error numbers to text. Therefore, a partial table is included here for reference. Error Description Symbolic Name Code A blocking operation was interrupted by a call to WSAEINTR WSACancelBlockingCall An attempt was made to access a socket in a way WSAEACCES forbidden by its access permissions The system detected an invalid pointer address in WSAEFAULT attempting to use a pointer argument in a call An invalid argument was supplied WSAEINVAL Too many open sockets WSAEMFILE A non-blocking socket operation could not be WSAEWOULDBLOCK completed immediately A blocking operation is currently executing WSAEINPROGRESS An operation was attempted on a non-blocking socket WSAEALREADY that already had an operation in progress An operation was attempted on something that is not a WSAENOTSOCK socket A required address was omitted from an operation on a WSAEDESTADDRREQ socket A message sent on a datagram socket was larger than WSAEMSGSIZE the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself A protocol was specified in the socket function call that WSAEPROTOTYPE does not support the semantics of the socket type requested An unknown, invalid, or unsupported option or level was WSAENOPROTOOPT specified in a getsockopt or setsockopt call The requested protocol has not been configured into the system, or no implementation for it exists The support for the specified socket type does not exist in this address family The attempted operation is not supported for the type of WSAEOPNOTSUPP object referenced The protocol family has not been configured into the WSAEPFNOSUPPORT system or no implementation for it exists
Microsoft Winsock Errors Unfortunately, there is currently no routine that translates Windows socket error numbers to text. Therefore, a partial table is included here for reference. Error Code Description Symbolic Name A blocking operation was interrupted by a call to WSACancelBlockingCall WSAEINTR An attempt was made to access a socket in a way forbidden by its access permissions WSAEACCES The system detected an invalid pointer address in attempting to use a pointer argument in a call WSAEFAULT An invalid argument was supplied WSAEINVAL Too many open sockets WSAEMFILE A non-blocking socket operation could not be completed immediately WSAEWOULDBLOCK A blocking operation is currently executing WSAEINPROGRESS An operation was attempted on a non-blocking socket that already had an operation in progress WSAEALREADY An operation was attempted on something that is not a socket WSAENOTSOCK A required address was omitted from an operation on a socket WSAEDESTADDRREQ A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself WSAEMSGSIZE A protocol was specified in the socket function call that does not support the semantics of the socket type requested WSAEPROTOTYPE An unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call WSAENOPROTOOPT The requested protocol has not been configured into the system, or no implementation for it exists The support for the specified socket type does not exist in this address family The attempted operation is not supported for the type of object referenced WSAEOPNOTSUPP The protocol family has not been configured into the system or no implementation for it exists WSAEPFNOSUPPORT
PI_SiTeleXPXU_2.5.6.20.docx