WinSock functions: accept(), close socket(), connect(), recv(), recvfrom(), send(), sendto(), WSAAsyncGetHostByAddr(), WSAAsyncGetHostByName(), WSAAsyncGetProtoByName(), WSAAsyncGetProtoByNumber(), WSAAsyncGetServByName(), WSAAsyncGetServByPort() WSAHOST_NOT_FOUND (11001) Host not found Berkeley description: No such host is known. This error apparently also takes the place of WSAEPFNOSUPPORT (which means "protocol family not supported"), since that error is not listed for socket() in the v1.1 WinSock specification. No such service is known. You can attempt to avoid the error by calling WSAIsBlocking() before making any WinSock function calls.
WinSock description: No equivalent. Note that the v1.1 WinSock specification does not explicitly state that this error occurs if the value you request is larger than the WSAData.iMaxUdpDg returned from WSAStartup(). WinSock description: Same as Berkeley. WinSock description: Similar to Berkeley & Microsoft C, the generic meaning is that an application passed invalid input parameter in a function call.
Every error description contains at least: Summary Info: Error macro: manifest constant, as defined in WINSOCK.H Error value: as defined in v1.1 WINSOCK.H Short description Berkeley description: text describing the equivalent Berkeley description: An attempt was made to access a file in a way forbidden by its file access permissions. WSAECONNREFUSED 10061 Connection refused.
- Added to that, this article will allow you to diagnose any common error alerts associated with Wsaetoomanyrefs error code you may be sent.
- 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.
- For example, the ARPA Internet UDP protocol cannot be specified with a socket type of SOCK_STREAM.
- There are 2 methods in which to resolve Wsaetoomanyrefs error code: Advanced Solution (advanced): 1) Start your computer and then log on as an administrator. 2) Click on the Get started
- A protocol was specified in the socket function call that does not support the semantics of the socket type requested.
- No more results can be returned by the WSALookupServiceNext function.
- WinSock description: NOT same as Berkeley, but analogous.
Berkeley description: A bad option or level was specified in a getsockopt()(2) or setsockopt(2) call. If an application sends a UDP packet to a host/port that does not have a datagram socket "listening," the network system may respond by sending back an ICMP Port Unreachable packet Here is a link to a different Wsaetoomanyrefs repair program you can try if the previous tool doesn’t work. The QoS request was rejected because the policy system couldn't allocate the requested resource within the existing policy.
The server application might need to call htons() to translate the port to network byte order in the sockaddr structure. Macro Definition Documentation #define EADDRINUSEWSAEADDRINUSE #define EADDRNOTAVAILWSAEADDRNOTAVAIL #define EAFNOSUPPORTWSAEAFNOSUPPORT #define EALREADYWSAEALREADY #define EBUSYETIME #define ECANCELED125 #define ECOMMECONNABORTED #define ECONNABORTEDWSAECONNABORTED #define ECONNREFUSEDWSAECONNREFUSED #define ECONNRESETWSAECONNRESET #define EDEADLK1000 /* Some large number.... */ #define Clearly, this oversight was not intentional. WSA_INVALID_PARAMETER 87 One or more parameters are invalid.
It may also make explicit mention of other functions that can fail with this error. Berkeley description: An operation that takes a long time to complete (such as a connect()) was attempted on a non-blocking socket. (see ioctl()). User suggestions: Do you have the WinSock DLL that supports the version of the WinSock specification required by the application? WinSock functions: Any function which allocates a new descriptor: accept(), listen(), & socket().
You may have to register or Login before you can post: click the register link above to proceed. WinSock description: No equivalent. Developer suggestions: Chances are, that if you encounter this error, your application ignored the failure of some previous function. However, because a BSD socket is equivalent to a file handle, some Windows Sockets platforms provide some file handle and socket equivalency.
Additional functions: With a datagram socket: send() or sendto(), or FD_READ. Ping a host on the same subnet as the host you were connected to (if you know one). By calling shutdown() you do a partial close of a socket, which means you have discontinued sending. If it doesn't respond, it might be off-line or there may be a network problem along the way.
A socket operation encountered a dead host. Any one of the preceeding actions can end up in the removal or data corruption of Windows system files. Developer suggestions: You need to be prepared to handle this error on any functions that reference blocking sockets, or any calls to blocking functions, if you allow the user to cancel WSA_OPERATION_ABORTED 995 Overlapped operation aborted.
Thirteen errors have "
An address incompatible with the requested protocol was used.
Developer suggestions: WSAStartup() failed, and you didn't detect it, or it wasn't called for the current task at all, or you called WSACleanup() too many times. It also occurs with functions that take a socket handle and a sockaddr structure as input parameters. WSA_QOS_EOBJLENGTH 11022 Invalid QoS object length. WSAEBADF 10009 File handle is not valid.
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. The Windows Sockets errors are listed in alphabetical order below (they're cross-referenced in a list in numerical order further below). The QoS reserve request has been confirmed. The v1.1 specification also lists connect(), although it does not allocate a descriptor.
You are unlikely to encounter them. The application has initiated an overlapped operation that cannot be completed immediately. This particular code can be used by the supplier to identify the error made. WinSock functions: With a datastream socket: connect() and FD_CONNECT WSAAsyncelect() notification message.
Berkeley description: The protocol has not been configured into the system, or no implementation for it exists. WSAEMSGSIZE (10040) Message too long. An invalid QoS filter style was used.