Tabla de Socket Errors

Interrupted function call

Una operación de bloqueo fue interrumpida por una llamada a WSACancelBlockingCall.

File handle is not valid

Se recibió un identificador de archivo no válido. Posible problema de disco.

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

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

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.

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.

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 callingconnect on a nonblocking SOCK_STREAM socket, since some time must elapse for the connection to be established.

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.

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.

Socket operation on non-socket

An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.

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.

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.

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.

Bad protocol option

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

Protocol not supported

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

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.

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.

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.

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.

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—connectchooses 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, includingconnect, listen, WSAConnect, or WSAJoinLeaf.

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

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.

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.

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 setSO_KEEPALIVE on a connection that has already failed.

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.

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.

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.

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.

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, setsockoptsetting SO_KEEPALIVE if the connection has been reset.

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.

Too many references

Too many references to some kernel object.

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.

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.

Cannot translate name

Cannot translate a name.

Name too long

A name component or a name was too long.

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.

No route to host

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

Directory not empty

Cannot remove a directory that is not empty.

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.

User quota exceeded.

Ran out of user quota.

Disk quota exceeded.

Ran out of disk quota.

Stale file handle reference.

The file handle reference is no longer available.

Item is remote.

The item is not available locally.

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.

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.

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.

Graceful shutdown in progress

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

No more results

No more results can be returned by theWSALookupServiceNext function.

Call has been canceled

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

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. 

Service provider is invalid

The requested service provider is invalid. This error is returned by the WSCGetProviderInfo and WSCGetProviderInfo32functions 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. 

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. 

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.

Service not found

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

Class type not found

The specified class was not found.

No more results

No more results can be returned by the WSALookupServiceNext function. 

Call was canceled

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

Database query was refused

A database query failed because it was actively refused. 

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.

Non-authoritative 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.

This is a non-recoverable 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.

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.

QoS receivers

At least one QoS reserve has arrived.

QoS senders

At least one QoS send path has arrived.

No QoS senders

There are no QoS senders. 

QoS no receivers

There are no QoS receivers. 

QoS request confirmed

The QoS reserve request has been confirmed. 

QoS admission error

A QoS error occurred due to lack of resources. 

QoS policy failure

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

QoS bad style

An unknown or conflicting QoS style was encountered. 

QoS bad object

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

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. 

QoS generic error

A general QoS error. 

QoS service type error

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

QoS flowspec error

An invalid or inconsistent flowspec was found in the QOSstructure. 

Invalid QoS provider buffer

An invalid QoS provider-specific buffer. 

Invalid QoS filter style

An invalid QoS filter style was used. 

Invalid QoS filter type

An invalid QoS filter type was used. 

Incorrect QoS filter count

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

Invalid QoS object length

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

Incorrect QoS flow count

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

Unrecognized QoS object

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

Invalid QoS policy object

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

Invalid QoS flow descriptor

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

Invalid QoS provider-specific flowspec

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

Invalid QoS provider-specific filterspec

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

Invalid QoS shape discard mode object

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

Invalid QoS shaping rate object

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

Reserved policy QoS element type

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