User Fixable Errors - There are two basic types of errors: those an application user can remedy, and those he cannot and a user should never see an error that is not user-fixable.

Here is a list of user-fixable errors:

WSAEINTR (10004) Interrupted function call
A blocking operation was interrupted by a call to WSACancelBlockingCall

WSAEBADF (10009) Bad file number

WSAEACCES (10013) Permission denied
An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt (SO_BROADCAST).

WSAEFAULT (10014) Bad address
The system detected an invalid pointer address in attempting to use a pointer argument of a call.

This error occurs if an application passes an invalid pointer value, or if the length of the buffer is too small. For instance, if the length of an argument which is a struct sockaddr is smaller than sizeof(struct sockaddr).

In some instances, it also refers to the current state of the socket - for instance, calling accept on a socket that is not listening.
 

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, for example recv when no data is queued to be read from the socket.

It is a non-fatal error, and the operation should be retried later. It is normal for WSAEWOULDBLOCK to be reported as the result from calling connects on a non-blocking SOCK_STREAM socket, since some time must elapse for the connection to be established.

WSAEINPROGRESS (10036) Operation now in progress
A blocking operation is currently executing. Windows Sockets only allows a single blocking operation to be outstanding per task (or thread), and if any other function call is made (whether or not it references that or any other socket) the function fails with the WSAEINPROGRESS error.

WSAEALREADY (10037) Operation already in progress
An operation was attempted on a non-blocking socket that already had an operation in progress - i.e. calling connect a second time on a non-blocking socket that is already connecting, or canceling an asynchronous request WSAAsyncGetXbyY that has already been canceled or completed.
 

WSAENOTSOCK (10038) Socket operation on non-socket
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.
 

WSAEDESTADDRREQ (10039)
Destination address required
A required address was omitted from an operation on a socket. For example, this error will be returned if sendto is called with the remote address of ADDR_ANY

WSAEMSGSIZE (10040) Message too long
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.

WSAEPROTOTYPE (10041)
Protocol wrong type for socket A protocol was specified in the socketfunction call that does not support the semantics of the socket type requested.
For example, the ARPA Internet UDP protocol cannot be specified with a socket type of SOCK_STREAM
 

WSAENOPROTOOPT (10042) Bad protocol option
An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockoptcall

WSAEPROTONOSUPPORT (10043)
Protocol not supported The requested protocol has not been configured into the system, or no implementation for it exists. For example, a socketcall requests a SOCK_DGRAM socket, but specifies a stream protocol.

WSAESOCKTNOSUPPORT (10044)
Socket type not supported The support for the specified socket type does not exist in this address family. For example, the optional type SOCK_RAW might be selected in a socketcall, and the implementation does not support SOCK_RAW sockets at all.

WSAEOPNOTSUPP (10045) Operation not supported
The attempted operation is not supported for the type of object referenced.

Usually this occurs when a socket descriptor to a socket that cannot support this operation, for example, trying to accept a connection on a datagram socket.

List of user-fixable errors - Continue Next Page 3/3