Windows Sockets Error Codes (Windows)

191 out of 358 rated this helpful

Most Windows Sockets 2 functions do not return the specific cause of an error when the function returns.
For information, see the Handling Winsock Errors topic.

The WSAGetLastError function returns the last error that occurred for the calling thread. When a
particular Windows Sockets function indicates an error has occurred, this function should be called
immediately to retrieve the extended error code for the failing function call. These error codes and a short
text description associated with an error code are defined in the Winerror.h header file. The
FormatMessage function can be used to obtain the message string for the returned error.

For information on how to handle error codes when porting socket applications to Winsock, see Error
Codes - errno, h_errno and WSAGetLastError.

The following list describes the possible error codes returned by the WSAGetLastError function. Errors are
listed in numerical order with the error macro name. Some error codes defined in the Winsock2.h header
file are not returned from any function.

Return code/value Description

WSA_INVALID_HANDLE Specified event object handle is invalid.

6 An application attempts to use an event object, but the
specified handle is not valid. Note that this error is
returned by the operating system, so the error number
may change in future releases of Windows.

WSA_NOT_ENOUGH_MEMORY Insufficient memory available.

8 An application used a Windows Sockets function that
directly maps to a Windows function. The Windows
function is indicating a lack of required memory resources.
Note that this error is returned by the operating system,
so the error number may change in future releases of
Windows.

WSA_INVALID_PARAMETER One or more parameters are invalid.

87 An application used a Windows Sockets function which
directly maps to a Windows function. The Windows
function is indicating a problem with one or more
parameters. Note that this error is returned by the
operating system, so the error number may change in
future releases of Windows.
WSA_OPERATION_ABORTED Overlapped operation aborted.
995 An overlapped operation was canceled due to the closure
of the socket, or the execution of the SIO_FLUSH
command in WSAIoctl. Note that this error is returned by
the operating system, so the error number may change in
future releases of Windows.

WSA_IO_INCOMPLETE Overlapped I/O event object not in signaled state.

996 The application has tried to determine the status of an
overlapped operation which is not yet completed.
Applications that use WSAGetOverlappedResult (with
the fWait flag set to FALSE) in a polling mode to
determine when an overlapped operation has completed,
get this error code until the operation is complete. Note
that this error is returned by the operating system, so the
error number may change in future releases of Windows.

Overlapped operations will complete later.

WSA_IO_PENDING
997 The application has initiated an overlapped operation that
cannot be completed immediately. A completion indication
will be given later when the operation has been completed.
Note that this error is returned by the operating system,
so the error number may change in future releases of
Windows.

WSAEINTR Interrupted function call.

10004 A blocking operation was interrupted by a call to
WSACancelBlockingCall.

WSAEBADF File handle is not valid.

10009 The file handle supplied is not valid.

WSAEACCES Permission denied.

10013 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).
Another possible reason for the WSAEACCES error is that
when the bind function is called (on Windows NT 4.0 with
SP4 and later), another application, service, or kernel mode
 SP4 and later), another application, service, or kernel mode
driver is bound to the same address with exclusive access.
Such exclusive access is a new feature of Windows NT 4.0
with SP4 and later, and is implemented by using the
SO_EXCLUSIVEADDRUSE option.

WSAEFAULT Bad address.

10014 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 sockaddr structure, is
smaller than the sizeof(sockaddr).

WSAEINVAL Invalid argument.

10022 Some invalid argument was supplied (for example,
specifying an invalid level to the setsockopt function). 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 Too many open files.

10024 Too many open sockets. Each implementation may have a
maximum number of socket handles available, either
globally, per process, or per thread.

WSAEWOULDBLOCK Resource temporarily unavailable.

10035 This error is returned from operations on nonblocking
sockets that cannot be completed immediately, for
example recv when no data is queued to be read from the
socket. It is a nonfatal error, and the operation should be
retried later. It is normal for WSAEWOULDBLOCK to be
reported as the result from calling connect on a
nonblocking SOCK_STREAM socket, since some time must
elapse for the connection to be established.

WSAEINPROGRESS Operation now in progress.

10036 A blocking operation is currently executing. Windows
Sockets only allows a single blocking operation—per- task
or thread—to be outstanding, 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 Operation already in progress.
10037 An operation was attempted on a nonblocking socket with
an operation already in progress—that is, calling connect
a second time on a nonblocking socket that is already
connecting, or canceling an asynchronous request
(WSAAsyncGetXbyY) that has already been canceled or
completed.

WSAENOTSOCK Socket operation on nonsocket.

10038 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 Destination address required.

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

WSAEMSGSIZE Message too long.

10040 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 was smaller than the
datagram itself.

WSAEPROTOTYPE Protocol wrong type for socket.

10041 A protocol was specified in the socket function 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 Bad protocol option.

10042 An unknown, invalid or unsupported option or level was
specified in a getsockopt or setsockopt call.

WSAEPROTONOSUPPORT Protocol not supported.

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

WSAESOCKTNOSUPPORT Socket type not supported.

10044 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 socket call, and the
implementation does not support SOCK_RAW sockets at
all.

WSAEOPNOTSUPP Operation not supported.

10045 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
is trying to accept a connection on a datagram socket.

WSAEPFNOSUPPORT Protocol family not supported.

10046 The protocol family has not been configured into the
system or no implementation for it exists. This message
has a slightly different meaning from
WSAEAFNOSUPPORT. However, it is interchangeable in
most cases, and all Windows Sockets functions that return
one of these messages also specify WSAEAFNOSUPPORT.

WSAEAFNOSUPPORT Address family not supported by protocol family.

10047 An address incompatible with the requested protocol was
used. All sockets are created with an associated address
family (that is, AF_INET for Internet Protocols) and a
generic protocol type (that is, SOCK_STREAM). This error is
returned if an incorrect protocol is explicitly requested in
the socket call, or if an address of the wrong family is used
for a socket, for example, in sendto.

WSAEADDRINUSE Address already in use.

10048 Typically, only one usage of each socket address
(protocol/IP address/port) is 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 was not closed properly, or one
that is still in the process of closing. For server applications
that need to bind multiple sockets to the same port
number, consider using setsockopt (SO_REUSEADDR).
 number, consider using setsockopt (SO_REUSEADDR).
Client applications usually need not call bind at all
—connect chooses an unused port automatically. When
bind is called with a wildcard address (involving
ADDR_ANY), a WSAEADDRINUSE error could be delayed
until the specific address is committed. This could happen
with a call to another function later, including connect,
listen, WSAConnect, or WSAJoinLeaf.

WSAEADDRNOTAVAIL Cannot assign requested address.

10049 The requested address is not valid in its context. This
normally results from an attempt to bind to an address
that is not valid for the local computer. This can also result
from connect, sendto, WSAConnect, WSAJoinLeaf, or
WSASendTo when the remote address or port is not valid
for a remote computer (for example, address or port 0).

WSAENETDOWN Network is down.

10050 A socket operation encountered a dead network. This
could indicate a serious failure of the network system (that
is, the protocol stack that the Windows Sockets DLL runs
over), the network interface, or the local network itself.

WSAENETUNREACH Network is unreachable.

10051 A socket operation was attempted to an unreachable
network. This usually means the local software knows no
route to reach the remote host.

WSAENETRESET Network dropped connection on reset.

10052 The connection has been broken due to keep-alive activity
detecting a failure while the operation was in progress. It
can also be returned by setsockopt if an attempt is made
to set SO_KEEPALIVE on a connection that has already
failed.

WSAECONNABORTED Software caused connection abort.

10053 An established connection was aborted by the software in
your host computer, possibly due to a data transmission
time-out or protocol error.

WSAECONNRESET Connection reset by peer.

10054 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 (see setsockopt for more
information on the SO_LINGER option 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 that
were in progress fail with WSAENETRESET. Subsequent
operations fail with WSAECONNRESET.

WSAENOBUFS No buffer space available.

10055 An operation on a socket could not be performed because
the system lacked sufficient buffer space or because a
queue was full.

WSAEISCONN Socket is already connected.

10056 A connect request was made on an already-connected
socket. Some implementations also return this error if
sendto is called on a connected SOCK_DGRAM socket (for
SOCK_STREAM sockets, the to parameter in sendto is
ignored) although other implementations treat this as a
legal occurrence.

WSAENOTCONN Socket is not connected.

10057 A request to send or receive data was disallowed because
the socket is not connected and (when sending on a
datagram socket using sendto) no address was supplied.
Any other type of operation might also return this error—
for example, setsockopt setting SO_KEEPALIVE if the
connection has been reset.

WSAESHUTDOWN Cannot send after socket shutdown.

10058 A request to send or receive data was disallowed because
the socket had already been shut down in that direction
with a previous shutdown call. By calling shutdown a
partial close of a socket is requested, which is a signal that
sending or receiving, or both have been discontinued.

WSAETOOMANYREFS Too many references.

10059 Too many references to some kernel object.
10059 Too many references to some kernel object.

WSAETIMEDOUT Connection timed out.

10060 A connection attempt failed because the connected party
did not properly respond after a period of time, or the
established connection failed because the connected host
has failed to respond.

WSAECONNREFUSED Connection refused.

10061 No connection could be made because the target
computer actively refused it. This usually results from
trying to connect to a service that is inactive on the
foreign host—that is, one with no server application
running.

WSAELOOP Cannot translate name.

10062 Cannot translate a name.

WSAENAMETOOLONG Name too long.

10063 A name component or a name was too long.

WSAEHOSTDOWN Host is down.

10064 A socket operation failed because the destination host is
down. A socket operation encountered a dead host.
Networking activity on the local host has not been
initiated. These conditions are more likely to be indicated
by the error WSAETIMEDOUT.

WSAEHOSTUNREACH No route to host.

10065 A socket operation was attempted to an unreachable host.
See WSAENETUNREACH.

WSAENOTEMPTY Directory not empty.

10066 Cannot remove a directory that is not empty.

WSAEPROCLIM Too many processes.

10067 A Windows Sockets implementation may have a limit on
the number of applications that can use it simultaneously.
WSAStartup may fail with this error if the limit has been
 WSAStartup may fail with this error if the limit has been
reached.

WSAEUSERS User quota exceeded.

10068 Ran out of user quota.

WSAEDQUOT Disk quota exceeded.

10069 Ran out of disk quota.

WSAESTALE Stale file handle reference.

10070 The file handle reference is no longer available.

WSAEREMOTE Item is remote.

10071 The item is not available locally.

WSASYSNOTREADY Network subsystem is unavailable.

10091 This error is returned by WSAStartup if the Windows
Sockets implementation cannot function at this time
because the underlying system it uses to provide network
services is currently unavailable. Users should check:

That the appropriate Windows Sockets DLL file is in the

current path.
That they are not trying to use more than one Windows
Sockets 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.
The Windows Sockets implementation documentation to
be sure all necessary components are currently installed
and configured correctly.

WSAVERNOTSUPPORTED Winsock.dll version out of range.

10092 The current Windows Sockets implementation does not
support the Windows Sockets specification version
requested by the application. Check that no old Windows
Sockets DLL files are being accessed.

WSANOTINITIALISED Successful WSAStartup not yet performed.

10093 Either the application has not called WSAStartup or
10093 Either the application has not called WSAStartup or
WSAStartup failed. The application may be accessing a
socket that the current active task does not own (that is,
trying to share a socket between tasks), or WSACleanup
has been called too many times.

WSAEDISCON Graceful shutdown in progress.

10101 Returned by WSARecv and WSARecvFrom to indicate
that the remote party has initiated a graceful shutdown
sequence.

WSAENOMORE No more results.

10102 No more results can be returned by the
WSALookupServiceNext function.

WSAECANCELLED Call has been canceled.

10103 A call to the WSALookupServiceEnd function was made
while this call was still processing. The call has been
canceled.

WSAEINVALIDPROCTABLE Procedure call table is invalid.

10104 The service provider procedure call table is invalid. A
service provider returned a bogus procedure table to
Ws2_32.dll. This is usually caused by one or more of the
function pointers being NULL.

WSAEINVALIDPROVIDER Service provider is invalid.

10105 The requested service provider is invalid. This error is
returned by the WSCGetProviderInfo and
WSCGetProviderInfo32 functions if the protocol entry
specified could not be found. This error is also returned if
the service provider returned a version number other than
2.0.

WSAEPROVIDERFAILEDINIT Service provider failed to initialize.

10106 The requested service provider could not be loaded or
initialized. This error is returned if either a service
provider's DLL could not be loaded (LoadLibrary failed) or
the provider's WSPStartup or NSPStartup function failed.
WSASYSCALLFAILURE System call failure.
10107 A system call that should never fail has failed. This is a
generic error code, returned under various conditions.
Returned when a system call that should never fail does
fail. For example, if a call to WaitForMultipleEvents fails
or one of the registry functions fails trying to manipulate
the protocol/namespace catalogs.
Returned when a provider does not return SUCCESS and
does not provide an extended error code. Can indicate a
service provider implementation error.

WSASERVICE_NOT_FOUND Service not found.

10108 No such service is known. The service cannot be found in
the specified name space.

WSATYPE_NOT_FOUND Class type not found.

10109 The specified class was not found.

WSA_E_NO_MORE No more results.

10110 No more results can be returned by the
WSALookupServiceNext function.

WSA_E_CANCELLED Call was canceled.

10111 A call to the WSALookupServiceEnd function was made
while this call was still processing. The call has been
canceled.

WSAEREFUSED Database query was refused.

10112 A database query failed because it was actively refused.

WSAHOST_NOT_FOUND Host not found.

11001 No such host is known. The name is not an official host
name or alias, or it cannot be found in the database(s)
being queried. This error may also be returned for protocol
and service queries, and means that the specified name
could not be found in the relevant database.

WSATRY_AGAIN Nonauthoritative host not found.

11002 This is usually a temporary error during host name
resolution and means that the local server did not receive
a response from an authoritative server. A retry at some
time later may be successful.

WSANO_RECOVERY This is a nonrecoverable error.

11003 This indicates that some sort of nonrecoverable error
occurred during a database lookup. This may be because
the database files (for example, BSD-compatible HOSTS,
SERVICES, or PROTOCOLS files) could not be found, or a
DNS request was returned by the server with a severe
error.

WSANO_DATA Valid name, no data record of requested type.

11004 The requested name is valid and was found in the
database, but it does not have the correct associated data
being resolved for. The usual example for this is a host
name-to-address translation attempt (using
gethostbyname or WSAAsyncGetHostByName) which
uses the DNS (Domain Name Server). An MX record is
returned but no A record—indicating the host itself exists,
but is not directly reachable.

WSA_QOS_RECEIVERS QoS receivers.

11005 At least one QoS reserve has arrived.

WSA_QOS_SENDERS QoS senders.

11006 At least one QoS send path has arrived.

WSA_QOS_NO_SENDERS No QoS senders.

11007 There are no QoS senders.

WSA_QOS_NO_RECEIVERS QoS no receivers.

11008 There are no QoS receivers.

WSA_QOS_REQUEST_CONFIRMED QoS request confirmed.

11009 The QoS reserve request has been confirmed.
WSA_QOS_ADMISSION_FAILURE QoS admission error.
11010 A QoS error occurred due to lack of resources.

WSA_QOS_POLICY_FAILURE QoS policy failure.

11011 The QoS request was rejected because the policy system
couldn't allocate the requested resource within the existing
policy.

WSA_QOS_BAD_STYLE QoS bad style.

11012 An unknown or conflicting QoS style was encountered.

WSA_QOS_BAD_OBJECT QoS bad object.

11013 A problem was encountered with some part of the
filterspec or the provider-specific buffer in general.

WSA_QOS_TRAFFIC_CTRL_ERROR QoS traffic control error.

11014 An error with the underlying traffic control (TC) API as the
generic QoS request was converted for local enforcement
by the TC API. This could be due to an out of memory
error or to an internal QoS provider error.

WSA_QOS_GENERIC_ERROR QoS generic error.

11015 A general QoS error.

WSA_QOS_ESERVICETYPE QoS service type error.

11016 An invalid or unrecognized service type was found in the
QoS flowspec.

WSA_QOS_EFLOWSPEC QoS flowspec error.

11017 An invalid or inconsistent flowspec was found in the QOS
structure.

WSA_QOS_EPROVSPECBUF Invalid QoS provider buffer.

11018 An invalid QoS provider-specific buffer.

WSA_QOS_EFILTERSTYLE Invalid QoS filter style.

WSA_QOS_EFILTERSTYLE Invalid QoS filter style.
11019 An invalid QoS filter style was used.

WSA_QOS_EFILTERTYPE Invalid QoS filter type.

11020 An invalid QoS filter type was used.

WSA_QOS_EFILTERCOUNT Incorrect QoS filter count.

11021 An incorrect number of QoS FILTERSPECs were specified in
the FLOWDESCRIPTOR.

WSA_QOS_EOBJLENGTH Invalid QoS object length.

11022 An object with an invalid ObjectLength field was specified
in the QoS provider-specific buffer.

WSA_QOS_EFLOWCOUNT Incorrect QoS flow count.

11023 An incorrect number of flow descriptors was specified in
the QoS structure.

WSA_QOS_EUNKOWNPSOBJ Unrecognized QoS object.

11024 An unrecognized object was found in the QoS provider-
specific buffer.

WSA_QOS_EPOLICYOBJ Invalid QoS policy object.

11025 An invalid policy object was found in the QoS provider-
specific buffer.

WSA_QOS_EFLOWDESC Invalid QoS flow descriptor.

11026 An invalid QoS flow descriptor was found in the flow
descriptor list.

WSA_QOS_EPSFLOWSPEC Invalid QoS provider-specific flowspec.

11027 An invalid or inconsistent flowspec was found in the QoS
provider-specific buffer.

WSA_QOS_EPSFILTERSPEC Invalid QoS provider-specific filterspec.

11028 An invalid FILTERSPEC was found in the QoS provider-
specific buffer.
 specific buffer.

WSA_QOS_ESDMODEOBJ Invalid QoS shape discard mode object.

11029 An invalid shape discard mode object was found in the
QoS provider-specific buffer.

WSA_QOS_ESHAPERATEOBJ Invalid QoS shaping rate object.

11030 An invalid shaping rate object was found in the QoS
provider-specific buffer.

WSA_QOS_RESERVED_PETYPE Reserved policy QoS element type.

11031 A reserved policy element was found in the QoS provider-
specific buffer.

Requirements

Winsock2.h;
Header
Winerror.h

See also
Error Codes - errno, h_errno and WSAGetLastError
Handling Winsock Errors
FormatMessage
WSAGetLastError

Send comments about this topic to Microsoft

Build date: 11/29/2012

Community Additions

Don't use http...

I kept getting this error: