Winsock коды ошибок - Не ошибается лишь тот, кто ничего не делает!

description	ms.assetid	title	ms.topic	ms.date
Windows Sockets (Winsock) error codes returned by the WSAGetLastError function.	50b924f3-2c88-443b-8a90-4293fe5c3048	Windows Sockets Error Codes (Winsock2.h)	reference	05/31/2018

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 6	Specified event object handle is invalid. An application attempts to use an event object, but the specified handle is not valid.
WSA_NOT_ENOUGH_MEMORY 8	Insufficient memory available. 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.
WSA_INVALID_PARAMETER 87	One or more parameters are invalid. 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.
WSA_OPERATION_ABORTED 995	Overlapped operation aborted. An overlapped operation was canceled due to the closure of the socket, or the execution of the SIO_FLUSH command in WSAIoctl.
WSA_IO_INCOMPLETE 996	Overlapped I/O event object not in signaled state. 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.
WSA_IO_PENDING 997	Overlapped operations will complete later. 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.
WSAEINTR 10004	Interrupted function call. A blocking operation was interrupted by a call to WSACancelBlockingCall.
WSAEBADF 10009	File handle is not valid. The file handle supplied is not valid.
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). 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 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 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 sockaddr structure, is smaller than the sizeof(sockaddr).
WSAEINVAL 10022	Invalid argument. 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 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 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 10036	Operation now in progress. 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 10037	Operation already in progress. 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 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.
WSAEDESTADDRREQ 10039	Destination address required. 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 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 was smaller than the datagram itself.
WSAEPROTOTYPE 10041	Protocol wrong type for socket. 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 10042	Bad protocol option. An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call.
WSAEPROTONOSUPPORT 10043	Protocol not supported. The requested protocol has not been configured into the system, or no implementation for it exists. For example, a socket call 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 socket call, 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 is trying to accept a connection on a datagram socket.
WSAEPFNOSUPPORT 10046	Protocol family not supported. 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 10047	Address family not supported by protocol family. 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 10048	Address already in use. 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). 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 10049	Cannot assign requested address. 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 10050	Network is down. 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 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. It can also be returned by setsockopt 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 in your host computer, possibly due to a data transmission time-out or protocol error.
WSAECONNRESET 10054	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 (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 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.
WSAEISCONN 10056	Socket is already connected. 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 10057	Socket is not connected. 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 10058	Cannot send after socket shutdown. 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 10059	Too many references. Too many references to some kernel object.
WSAETIMEDOUT 10060	Connection timed out. 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 10061	Connection refused. 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 10062	Cannot translate name. Cannot translate a name.
WSAENAMETOOLONG 10063	Name too long. A name component or a name was too long.
WSAEHOSTDOWN 10064	Host is down. 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 10065	No route to host. A socket operation was attempted to an unreachable host. See WSAENETUNREACH.
WSAENOTEMPTY 10066	Directory not empty. Cannot remove a directory that is not empty.
WSAEPROCLIM 10067	Too many processes. 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 reached.
WSAEUSERS 10068	User quota exceeded. Ran out of user quota.
WSAEDQUOT 10069	Disk quota exceeded. Ran out of disk quota.
WSAESTALE 10070	Stale file handle reference. The file handle reference is no longer available.
WSAEREMOTE 10071	Item is remote. The item is not available locally.
WSASYSNOTREADY 10091	Network subsystem is unavailable. 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 10092	Winsock.dll version out of range. 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 10093	Successful WSAStartup not yet performed. 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 10101	Graceful shutdown in progress. Returned by WSARecv and WSARecvFrom to indicate that the remote party has initiated a graceful shutdown sequence.
WSAENOMORE 10102	No more results. No more results can be returned by the WSALookupServiceNext function.
WSAECANCELLED 10103	Call has been canceled. A call to the WSALookupServiceEnd function was made while this call was still processing. The call has been canceled.
WSAEINVALIDPROCTABLE 10104	Procedure call table is invalid. 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 10105	Service provider is invalid. 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 10106	Service provider failed to initialize. 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 10107	System call failure. 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 10108	Service not found. No such service is known. The service cannot be found in the specified name space.
WSATYPE_NOT_FOUND 10109	Class type not found. The specified class was not found.
WSA_E_NO_MORE 10110	No more results. No more results can be returned by the WSALookupServiceNext function.
WSA_E_CANCELLED 10111	Call was canceled. A call to the WSALookupServiceEnd function was made while this call was still processing. The call has been canceled.
WSAEREFUSED 10112	Database query was refused. A database query failed because it was actively refused.
WSAHOST_NOT_FOUND 11001	Host not found. 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 11002	Nonauthoritative host not found. 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 11003	This is a nonrecoverable error. 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 11004	Valid name, no data record of requested type. 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 11005	QoS receivers. At least one QoS reserve has arrived.
WSA_QOS_SENDERS 11006	QoS senders. At least one QoS send path has arrived.
WSA_QOS_NO_SENDERS 11007	No QoS senders. There are no QoS senders.
WSA_QOS_NO_RECEIVERS 11008	QoS no receivers. There are no QoS receivers.
WSA_QOS_REQUEST_CONFIRMED 11009	QoS request confirmed. The QoS reserve request has been confirmed.
WSA_QOS_ADMISSION_FAILURE 11010	QoS admission error. A QoS error occurred due to lack of resources.
WSA_QOS_POLICY_FAILURE 11011	QoS policy failure. The QoS request was rejected because the policy system couldn’t allocate the requested resource within the existing policy.
WSA_QOS_BAD_STYLE 11012	QoS bad style. An unknown or conflicting QoS style was encountered.
WSA_QOS_BAD_OBJECT 11013	QoS bad object. A problem was encountered with some part of the filterspec or the provider-specific buffer in general.
WSA_QOS_TRAFFIC_CTRL_ERROR 11014	QoS traffic control error. 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 11015	QoS generic error. A general QoS error.
WSA_QOS_ESERVICETYPE 11016	QoS service type error. An invalid or unrecognized service type was found in the QoS flowspec.
WSA_QOS_EFLOWSPEC 11017	QoS flowspec error. An invalid or inconsistent flowspec was found in the QOS structure.
WSA_QOS_EPROVSPECBUF 11018	Invalid QoS provider buffer. An invalid QoS provider-specific buffer.
WSA_QOS_EFILTERSTYLE 11019	Invalid QoS filter style. An invalid QoS filter style was used.
WSA_QOS_EFILTERTYPE 11020	Invalid QoS filter type. An invalid QoS filter type was used.
WSA_QOS_EFILTERCOUNT 11021	Incorrect QoS filter count. An incorrect number of QoS FILTERSPECs were specified in the FLOWDESCRIPTOR.
WSA_QOS_EOBJLENGTH 11022	Invalid QoS object length. An object with an invalid ObjectLength field was specified in the QoS provider-specific buffer.
WSA_QOS_EFLOWCOUNT 11023	Incorrect QoS flow count. An incorrect number of flow descriptors was specified in the QoS structure.
WSA_QOS_EUNKOWNPSOBJ 11024	Unrecognized QoS object. An unrecognized object was found in the QoS provider-specific buffer.
WSA_QOS_EPOLICYOBJ 11025	Invalid QoS policy object. An invalid policy object was found in the QoS provider-specific buffer.
WSA_QOS_EFLOWDESC 11026	Invalid QoS flow descriptor. An invalid QoS flow descriptor was found in the flow descriptor list.
WSA_QOS_EPSFLOWSPEC 11027	Invalid QoS provider-specific flowspec. An invalid or inconsistent flowspec was found in the QoS provider-specific buffer.
WSA_QOS_EPSFILTERSPEC 11028	Invalid QoS provider-specific filterspec. An invalid FILTERSPEC was found in the QoS provider-specific buffer.
WSA_QOS_ESDMODEOBJ 11029	Invalid QoS shape discard mode object. An invalid shape discard mode object was found in the QoS provider-specific buffer.
WSA_QOS_ESHAPERATEOBJ 11030	Invalid QoS shaping rate object. An invalid shaping rate object was found in the QoS provider-specific buffer.
WSA_QOS_RESERVED_PETYPE 11031	Reserved policy QoS element type. A reserved policy element was found in the QoS provider-specific buffer.

Return code/value

Description

WSA_INVALID_HANDLE
6

Specified event object handle is invalid.: An application attempts to use an event object, but the specified handle is not valid.

WSA_NOT_ENOUGH_MEMORY
8

Insufficient memory available.: 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.

WSA_INVALID_PARAMETER
87

One or more parameters are invalid.: 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.

WSA_OPERATION_ABORTED
995

Overlapped operation aborted.: An overlapped operation was canceled due to the closure of the socket, or the execution of the SIO_FLUSH command in WSAIoctl.

WSA_IO_INCOMPLETE
996

Overlapped I/O event object not in signaled state.: 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.

WSA_IO_PENDING
997

Overlapped operations will complete later.

: 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.

WSAEINTR
10004

Interrupted function call.: A blocking operation was interrupted by a call to WSACancelBlockingCall.

WSAEBADF
10009

File handle is not valid.: The file handle supplied is not valid.

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

WSAEINVAL
10022

Invalid argument.: 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
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 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
10036

Operation now in progress.: 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
10037

Operation already in progress.: 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
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.

WSAEDESTADDRREQ
10039

Destination address required.: 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
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 was smaller than the datagram itself.

WSAEPROTOTYPE
10041

Protocol wrong type for socket.: 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
10042

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

WSAEPROTONOSUPPORT
10043

Protocol not supported.: The requested protocol has not been configured into the system, or no implementation for it exists. For example, a socket call 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 socket call, 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 is trying to accept a connection on a datagram socket.

WSAEPFNOSUPPORT
10046

Protocol family not supported.: 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
10047

Address family not supported by protocol family.: 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
10048

Address already in use.: 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). 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
10049

Cannot assign requested address.: 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
10050

Network is down.: 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
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. It can also be returned by setsockopt 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 in your host computer, possibly due to a data transmission time-out or protocol error.

WSAECONNRESET
10054

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 (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
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.

WSAEISCONN
10056

Socket is already connected.: 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
10057

Socket is not connected.: 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
10058

Cannot send after socket shutdown.: 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
10059

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

WSAETIMEDOUT
10060

Connection timed out.: 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
10061

Connection refused.: 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
10062

Cannot translate name.: Cannot translate a name.

WSAENAMETOOLONG
10063

Name too long.: A name component or a name was too long.

WSAEHOSTDOWN
10064

Host is down.: 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
10065

No route to host.: A socket operation was attempted to an unreachable host. See WSAENETUNREACH.

WSAENOTEMPTY
10066

Directory not empty.: Cannot remove a directory that is not empty.

WSAEPROCLIM
10067

Too many processes.: 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 reached.

WSAEUSERS
10068

User quota exceeded.: Ran out of user quota.

WSAEDQUOT
10069

Disk quota exceeded.: Ran out of disk quota.

WSAESTALE
10070

Stale file handle reference.: The file handle reference is no longer available.

WSAEREMOTE
10071

Item is remote.: The item is not available locally.

WSASYSNOTREADY
10091

Network subsystem is unavailable.: 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
10092

Winsock.dll version out of range.: 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
10093

Successful WSAStartup not yet performed.: 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
10101

Graceful shutdown in progress.: Returned by WSARecv and WSARecvFrom to indicate that the remote party has initiated a graceful shutdown sequence.

WSAENOMORE
10102

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

WSAECANCELLED
10103

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

WSAEINVALIDPROCTABLE
10104

Procedure call table is invalid.: 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
10105

Service provider is invalid.: 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
10106

Service provider failed to initialize.: 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
10107

System call failure.: 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
10108

Service not found.: No such service is known. The service cannot be found in the specified name space.

WSATYPE_NOT_FOUND
10109

Class type not found.: The specified class was not found.

WSA_E_NO_MORE
10110

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

WSA_E_CANCELLED
10111

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

WSAEREFUSED
10112

Database query was refused.: A database query failed because it was actively refused.

WSAHOST_NOT_FOUND
11001

Host not found.: 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
11002

Nonauthoritative host not found.: 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
11003

This is a nonrecoverable error.: 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
11004

Valid name, no data record of requested type.: 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
11005

QoS receivers.: At least one QoS reserve has arrived.

WSA_QOS_SENDERS
11006

QoS senders.: At least one QoS send path has arrived.

WSA_QOS_NO_SENDERS
11007

No QoS senders.: There are no QoS senders.

WSA_QOS_NO_RECEIVERS
11008

QoS no receivers.: There are no QoS receivers.

WSA_QOS_REQUEST_CONFIRMED
11009

QoS request confirmed.: The QoS reserve request has been confirmed.

WSA_QOS_ADMISSION_FAILURE
11010

QoS admission error.: A QoS error occurred due to lack of resources.

WSA_QOS_POLICY_FAILURE
11011

QoS policy failure.: The QoS request was rejected because the policy system couldn’t allocate the requested resource within the existing policy.

WSA_QOS_BAD_STYLE
11012

QoS bad style.: An unknown or conflicting QoS style was encountered.

WSA_QOS_BAD_OBJECT
11013

QoS bad object.: A problem was encountered with some part of the filterspec or the provider-specific buffer in general.

WSA_QOS_TRAFFIC_CTRL_ERROR
11014

QoS traffic control error.: 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
11015

QoS generic error.: A general QoS error.

WSA_QOS_ESERVICETYPE
11016

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

WSA_QOS_EFLOWSPEC
11017

QoS flowspec error.: An invalid or inconsistent flowspec was found in the QOS structure.

WSA_QOS_EPROVSPECBUF
11018

Invalid QoS provider buffer.: An invalid QoS provider-specific buffer.

WSA_QOS_EFILTERSTYLE
11019

Invalid QoS filter style.: An invalid QoS filter style was used.

WSA_QOS_EFILTERTYPE
11020

Invalid QoS filter type.: An invalid QoS filter type was used.

WSA_QOS_EFILTERCOUNT
11021

Incorrect QoS filter count.: An incorrect number of QoS FILTERSPECs were specified in the FLOWDESCRIPTOR.

WSA_QOS_EOBJLENGTH
11022

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

WSA_QOS_EFLOWCOUNT
11023

Incorrect QoS flow count.: An incorrect number of flow descriptors was specified in the QoS structure.

WSA_QOS_EUNKOWNPSOBJ
11024

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

WSA_QOS_EPOLICYOBJ
11025

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

WSA_QOS_EFLOWDESC
11026

Invalid QoS flow descriptor.: An invalid QoS flow descriptor was found in the flow descriptor list.

WSA_QOS_EPSFLOWSPEC
11027

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

WSA_QOS_EPSFILTERSPEC
11028

Invalid QoS provider-specific filterspec.: An invalid FILTERSPEC was found in the QoS provider-specific buffer.

WSA_QOS_ESDMODEOBJ
11029

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

WSA_QOS_ESHAPERATEOBJ
11030

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

WSA_QOS_RESERVED_PETYPE
11031

Reserved policy QoS element type.: A reserved policy element was found in the QoS provider-specific buffer.

Requirements

Requirement	Value
Header	Winsock2.h; Winerror.h

Return Code	Value	Description
WSAEINTR	10004	Interrupted function call. A blocking operation was interrupted by a call to WSACancelBlockingCall.
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). Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4 SP4 or 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 SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option.
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 sockaddr structure, is smaller than the sizeof(sockaddr).
WSAEINVAL	10022	Invalid argument. 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	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 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 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—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	10037	Operation already in progress. An operation was attempted on a non-blocking socket with an operation already in progress—that is, 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 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.
WSAEDESTADDRREQ	10039	Destination address required. 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	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 was smaller than the datagram itself.
WSAEPROTOTYPE	10041	Protocol wrong type for socket. 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	10042	Bad protocol option. An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call.
WSAEPROTONOSUPPORT	10043	Protocol not supported. The requested protocol has not been configured into the system, or no implementation for it exists. For example, a socket call 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 socket call, 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 is trying to accept a connection on a datagram socket.
WSAEPFNOSUPPORT	10046	Protocol family not supported. 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	10047	Address family not supported by protocol family. 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	10048	Address already in use. 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). 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	10049	Cannot assign requested address. 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	10050	Network is down. 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	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. It can also be returned by setsockopt 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 in your host computer, possibly due to a data transmission time-out or protocol error.
WSAECONNRESET	10054	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 (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. For more information see GlobalSCAPE Knowledge Base Article #10235
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. This error indicates a shortage of resources on your system. It can occur if you’re trying to run too many applications (of any kind) simultaneously on your machine. If this tends to occur after running certain applications for a while, it might be a symptom of an application that doesn’t return system resources (like memory) properly. It may also indicate you are not closing the applications properly. If it persists, exit Windows or reboot your machine to remedy the problem. Another possible solution is to increase the available virtual memory by increasing the size of the Windows paging file. For more information see GlobalSCAPE Knowledge Base Article #10234
WSAEISCONN	10056	Socket is already connected. 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	10057	Socket is not connected. 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	10058	Cannot send after socket shutdown. 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.
WSAETIMEDOUT	10060	Connection timed out. 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. For more information see GlobalSCAPE Knowledge Base Article #10384.
WSAECONNREFUSED	10061	Connection refused. 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. Sometimes a 10061 error is caused by either a firewall or anti-virus software presence on the local computer or network connection. Either one may be blocking the ports needed to make a successful FTP connection to the server. For a regular FTP session, disable the firewall or anti-virus software or configure it to allow CuteFTP to establish an FTP session over ports 20 and 21. Consult the documentation or help file for your specific firewall or antivirus software product for further instructions. Usually, the manufacturer of the device or software has specific instructions available on their website. If you continue to receive the same error after insuring ports 20 and 21 are open, contact the administrator of the server to which you are trying to connect.
WSAEHOSTDOWN	10064	Host is down. 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	10065	No route to host. A socket operation was attempted to an unreachable host. See WSAENETUNREACH.
WSAEPROCLIM	10067	Too many processes. 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 reached.
WSASYSNOTREADY	10091	Network subsystem is unavailable. 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	192	Winsock.dll version out of range. 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	10093	Successful WSAStartup not yet performed. 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	10101	Graceful shutdown in progress. Returned by WSARecv and WSARecvFrom to indicate that the remote party has initiated a graceful shutdown sequence.
WSATYPE_NOT_FOUND	10109	Class type not found. The specified class was not found.
WSAHOST_NOT_FOUND	11001	Host not found. 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	11002	Nonauthoritative host not found. 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	11003	This is a nonrecoverable error. This indicates that some sort of non-recoverable 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	11004	Valid name, no data record of requested type. 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_INVALID_HANDLE	OS Dependent	Specified event object handle is invalid. An application attempts to use an event object, but the specified handle is not valid.
WSA_INVALID_PARAMETER	OS Dependent	One or more parameters are invalid. 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.
WSA_IO_INCOMPLETE	OS Dependent	Overlapped I/O event object not in signaled state. 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.
WSA_IO_PENDING	OS Dependent	Overlapped operations will complete later. 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.
WSA_NOT_ENOUGH_MEMORY	OS Dependent	Insufficient memory available. 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.
WSA_OPERATION_ABORTED	OS Dependent	Overlapped operation aborted. An overlapped operation was canceled due to the closure of the socket, or the execution of the SIO_FLUSH command in WSAIoctl.
WSAINVALIDPROCTABLE	OS Dependent	Invalid procedure table from service provider. 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.)
WSAINVALIDPROVIDER	OS Dependent	Invalid service provider version number. A service provider returned a version number other than 2.0.
WSAPROVIDERFAILEDINIT	OS Dependent	Unable to initialize a service provider. Either a service provider’s DLL could not be loaded (LoadLibrary failed) or the provider’s WSPStartup/NSPStartup function failed.
WSASYSCALLFAILURE	OS Dependent	System call failure. 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.

Источник

Код ошибки Winsock Краткое описание сущности ошибки 10004 Операция блокирования прервана вызовом WSACancelBlockingCall.10009 Предоставленный дескриптор файла неверен. 10013 Сделана попытка доступа к сокету методом, запрещенным правами доступа. 10014 Система обнаружила недопустимый указатель адреса при попытке использовать в вызове аргумент указателя. 10022 Получен недопустимый аргумент. 10024 Открыто слишком много сокетов. 10035 Операция на незаблокированном сокете не может быть завершена немедленно. 10036 Сейчас выполняется операция блокировки. 10037 На незаблокированном сокете сделана попытка выполнить операцию при наличии другой выполняемой операции. 10038 Сделана попытка выполнить операцию на объекте, не являющемся сокетом. 10039 В операции на сокете пропущен обязательный адрес. 10040 Сообщение, отправленное на сокет датаграмм, было больше, чем буфер внутренних сообщений или был превышен иной сетевой параметр. Также возможно, что буфер для принятия сообщения был меньше, чем размер сообщения. 10041 Протокол, указанный в вызове функции сокета, не поддерживает такую семантику для требуемого типа сокета. 10042 Для вызова getsockopt или setsockopt был указан неизвестный, недопустимый или неподдерживаемый параметр или уровень. 10043 Требуемый протокол не настроен в данной системе, или не существует его реализации. 10044 Поддержка указанного типа сокетов в этом семействе адресов отсутствует. 10045 Предпринятая операция не поддерживается для выбранного типа объекта. 10046 Данное семейство протоколов не настроено в системе, или оно не реализовано. 10047 Адрес несовместим с выбранным протоколом. 10048 Обычно разрешается одно использование адреса сокета (протокол/сетевой адрес/порт). 10049 Требуемый адрес для своего контекста неверен. 10050 Операция на сокете обнаружила отключение сети. 10051 Сделана попытка выполнить операцию на сокете при отключенной сети. 10052 Подключение было разорвано из-за ошибки во время выполнения операции. 10053 Программа на вашем хост-компьютере разорвала установленное подключение. 10054 Удаленный хост принудительно разорвал существующее подключение. 10055 Невозможно выполнить операцию на сокете, т.к. буфер слишком мал или очередь переполнена. 10056 Сделан запрос на подключение для уже подключенного сокета. 10057 Запрос на отправку или получение данных (when sending on a datagram socket using a sendto call) no address was supplied. 10058 Запрос на отправку или получение данных был запрещен, т.к. сокет уже отключен в данном направлении на основании прежней запроса на его отключение. 10059 Слишком много ссылок на некоторый ключевой объект.

10060

Попытка установить соединение была безуспешной, т.к. от другого компьютера за требуемое время не получен нужный отклик, или было разорвано уже установленное соединение из-за неверного отклика уже подключенного компьютера. 10061 Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение. 10062 Не удается преобразовать имя. 10063 Компонент имени или все имя слишком длинно. 10064 Произошла ошибка операции на сокете, т.к. конечный хост выключен. 10065 Сделана попытка выполнить операцию на сокете для недоступного хоста. 10066 Нельзя удалить пустой каталог. 10067 Реализация Windows Sockets может иметь ограничения на количество одновременно выполняющихся приложений. 10068 Квота исчерпана. 10069 Дисковая квота исчерпана. 10070 Ссылка дескриптора файла более недоступна. 10071 Элемент локально недоступен. 10091 WSAStartup не может выполняться в данное время, т.к. недоступна основная система, используемая для работы сетевых служб . 10092 Указанная версия Windows Sockets не поддерживается. 10093 Или приложение не вызвало WSAStartup, или произошла ошибка в WSAStartup. 10101 Возвращено WSARecv или WSARecvFrom, чтобы показать — удаленная сторона инициировала правильную последовательность отключения. 10102 WSALookupServiceNext не может возвратить каких-либо дополнительных результатов. 10103 Был сделан вызов WSALookupServiceEnd, когда этот вызов еще обрабатывался. Обрабатываемый вызов был прерван. 10104 Недопустимая таблица вызова процедуры. 10105 Недопустимый поставщик услуг. 10106 Не удается загрузить или инициализировать нужного поставщика услуг. 10107 Произошла ошибка системного вызова, что недопустимо. 10108 Неизвестная служба. Эта служба отсутствует в указанном пространстве имен. 10109 Указанный класс не найден. 10110 WSALookupServiceNext не может возвратить каких-либо дополнительных результатов. 10111 Был сделан вызов WSALookupServiceEnd, когда этот вызов еще обрабатывался. Обрабатываемый вызов был прерван. 10112 Произошла ошибка запроса к базе данных, т.к. запрос был активно отвергнут. 11001 Этот хост неизвестен.Возможно, отсутствует связь, или не указан прокси сервер. 11002 Обычно — это временная ошибка, возникающая во время разрешения имени узла, и означающая, что локальный сервер не получил ответа от заслуживающего доверие сервера. 11003 При просмотре базы данных произошла неисправимая ошибка. 11004 Затребованное имя допустимо и оно найдено в базе данных, но для имени отсутствуют связанные с ним данные, которые были разрешены для него. 11005 Получен по меньшей мере один резерв. 11006 Получен по меньшей мере один путь. 11007 Отправители отсутствуют. 11008 Получатели отсутствуют. 11009 Резерв подтвержден. 11010 Произошла ошибка из-за недостатка ресурсов. 11011 Отвергнуто по административным причинам — неправильные учетные данные. 11012 Неизвестный или вызывающий конфликты стиль. 11013 Обнаружена проблема общего типа с буфером filterspec или providerspecific. 11014 Обнаружена проблема с частью «flowspec». 11015 Общая ошибка QOS. 11016 В спецификаторах потока найден недопустимый или нераспознанный тип службы. 11017 Недопустимый или нераспознанный спецификатор потока был найден в структуре QOS. 11018 Недопустимый буфер QOS, определяемый поставщиком. 11019 Использован недопустимый стиль фильтра QOS. 11020 Использован недопустимый стиль фильтра QOS. 11021 В FLOWDESCRIPTOR был задан неверный номер QOS FILTERSPEC. 11022 В определяемом поставщиком буфере QOS задан объект с неверным полем ObjectLength. 11023 В структуре QOS заданы неверные номера дескрипторов потока. 11024 В буфере QOS, задаваемом поставщиком, найден нераспознанный объект. 11025 В буфере QOS, задаваемом поставщиком, найден объект с недопустимой политикой. 11026 В списке дескрипторов потока обнаружен недопустимый дескриптор потока QOS. 11027 Недопустимый или нераспознанный спецификатор потока обнаружен в буфере QOS, определяемом поставщиком. 11028 Недопустимый FILTERSPEC обнаружен в буфере QOS, определяемом поставщиком. 11029 Недопустимый объект режима изменения формы обнаружен в буфере QOS, определяемом поставщиком. 11030 Недопустимый объект формирования уровня обнаружен в буфере QOS, определяемом поставщиком. 11031 Зарезервированный элемент политики обнаружен в буфере QOS, определяемом поставщиком.

Источник

Все
ошибки, которые происходят
при соединениях с
серверами и клиентами в
процессе работы программы
BSB регистрируются, как и
многие другие моменты
работы, в файле-журнале bsb.log.
Но в целях упрощения в
журнал пишутся только коды
ошибок, а не их текстовое
описание. Аналогично
обстоит ситуация и с
клиентской программой «BSB Client Informer»
— она выдает номер ошибки.

Программа BSB для связи
по протоколу TCP/IP
использует библиотеку Windows
Sockets, и далее приведено
очень краткое текстовое
описание на русском языке
кодов тех ошибок, которые
могут возникать при работе
с функциями этой
библиотеки WinSocks.

Код	Краткое описание сущности ошибки
10004	Выполнение операции с сокетом, блокирующей выполнение программы, прервано вызовом специальной функции.
10013	Нет разрешения на доступ к сокету.
10014	Неверный адрес указателя при вызове функции.
10022	Неправильный аргумент при вызове функции для работы с сокетами.
10024	Слишком много открытых сокетов на нить, процесс или глобальных.
10035	Ресурс временно недоступен, при выполнении функции работы с сокетом, которая не может выполнить операцию немедленно.
10036	Одна блокирующая операция сейчас уже выполняется.
10037	Одна операция с неблокирующим сокетом уже выполняется.
10038	Попытка вызвать функцию, работающую с сокетами, при передаче ей в аргументе значения, которое не является правильным значением сокета. Обычно возникает, при попытке работы с уже закрытым сокетом.
10039	Требуется адрес назначения
10040	Сообщение слишком длинное при передаче дейтаграммы.
10041	Тип протокол не поддерживается для данного сокета.
10042	Неправильная опция или уровень заданы в функциях опций сокетов
10043	Запрошенный протокол не сконфигурирован для работы с системе
10044	Тип сокета не поддерживается
10045	Операция с сокетом не поддерживается
10046	Семейство протоколов не поддерживается
10047	Адрес не поддерживается на выбранном протоколе сокета
10048	Адрес+порт уже используется на этом хосте. Очень распространённая ошибка, когда две программы-серверы пытаются использовать один и тот же порт для приема запросов клиентов.
10049	Невозможно использовать запрошенный адрес для привязки в порту
10050	Сеть неработоспособна
10051	Сеть недоступна, аппаратура не знает как туда переслать пакет, возможно из-за ненастроенной маршрутизации.
10052	Соединение разорвано из-за сбоя при выполнении операции
10053	Программное обеспечение компьютера, на котором выполняется данная программа, разорвало соединение.
10054	Соединение разорвано с удаленного компьютера, возможно, что так оно и задумано было, и клиент завершил всю передачу информации по сокету.
10055	Не места в буфере или очереди.
10056	Сокет уже подсоединен.
10057	Сокет не подсоединенный
10058	Невозможно послать или получить данные по сокету, из-за того, что эта операция уже запрещена функцией shutdown
10060	Timeout
10061	Удаленный компьютер отказал в соединении, возможно не нём не запущен соответствующая программа сервер.
10064	Компьютер, с которым производится попытка соединения выключен.
10065	К удаленному компьютеру не найдет маршрут пересылки пакетов.
10067	Запущено слишком много процессов, использующих Windows Socket
10091	Сетевая подсистема недоступна.
10092	Неверная версия winsock.dll
10093	Не выполнена функция WSAStartup перед использованием любой другой фукнции работы с сокетами.
10109	Запрошенный тип класса не найден.
10101	Удаленный компьютер инициировал завершение соединения
11001	Запрошенное имя компьютера не найдено
11002	Временная ошибка при разрешении имени компьютера в адрес, возможно её не будет при повторе операции через некоторое время.
11003	Невосстанавливаемая ошибка при разрешении имени в адрес.
11004	С запрошенным именем компьютера не связано никакой правильной информации об адресе, хотя само имя присутствует в соответствующих базах данных имён.

Источник

Requirements

See also