winsock-error.danielclarke.com
Winsock error 997 (WSA_IO_PENDING)
http://winsock-error.danielclarke.com/997.aspx
WSA IO PENDING - Overlapped operations will complete later. Basic (Microsoft) information for 997 a.k.a. WSA IO PENDING. The application has initiated an overlapped operation that cannot be completed immediately. A completion indication will be given later when the operation has been completed. Note that this error is returned by the operating system, so the error number may change in future releases of Windows. Full list of Winsock Error codes. Peer Monitor - network monitoring tool.
winsock-error.danielclarke.com
Winsock error 10024 (WSAEMFILE)
http://winsock-error.danielclarke.com/10024.aspx
WSAEMFILE - Too many open files. Basic (Microsoft) information for 10024 a.k.a. WSAEMFILE. Too many open sockets. Each implementation may have a maximum number of socket handles available, either globally, per process, or per thread. Detailed (Berkeley) information for winsock 10024, described as "Too many open files.". Too many open files. No process may have more than a system-defined number of file descriptors open at a time. Full list of Winsock Error codes. Peer Monitor - network monitoring tool.
winsock-error.danielclarke.com
Winsock error 10036 (WSAEINPROGRESS)
http://winsock-error.danielclarke.com/10036.aspx
WSAEINPROGRESS - Operation now in progress. Basic (Microsoft) information for 10036 a.k.a. WSAEINPROGRESS. 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. Detailed (Berkeley) information for winsock 10036, described as "Operation now in progress.".
winsock-error.danielclarke.com
Winsock error 10040 (WSAEMSGSIZE)
http://winsock-error.danielclarke.com/10040.aspx
WSAEMSGSIZE - Message too long. Basic (Microsoft) information for 10040 a.k.a. WSAEMSGSIZE. 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. Detailed (Berkeley) information for winsock 10040, described as "Message too long.". A message sent on a socket was larger than the internal message buffer or some other network limit. Full list of Winsock Error codes.
winsock-error.danielclarke.com
Winsock error 996 (WSA_IO_INCOMPLETE)
http://winsock-error.danielclarke.com/996.aspx
WSA IO INCOMPLETE - Overlapped I/O event object not in signaled state. Basic (Microsoft) information for 996 a.k.a. WSA IO INCOMPLETE. Detailed (Berkeley) information for winsock 996, described as "Overlapped I/O event object not in signaled state.". Full list of Winsock Error codes. Peer Monitor - network monitoring tool.
winsock-error.danielclarke.com
Winsock error 0 (No error)
http://winsock-error.danielclarke.com/0.aspx
No error - No error. Basic (Microsoft) information for 0 a.k.a. No error. Detailed (Berkeley) information for winsock 0, described as "No error". There's at least one WinSock implementation that will occasionally fail a function and report this as the error value, even though the function succeeded. You should simply ignore this error when it occurs. Full list of Winsock Error codes. Peer Monitor - network monitoring tool.
winsock-error.danielclarke.com
Winsock error 8 (WSA_NOT_ENOUGH_MEMORY)
http://winsock-error.danielclarke.com/8.aspx
WSA NOT ENOUGH MEMORY - Insufficient memory available. Basic (Microsoft) information for 8 a.k.a. WSA NOT ENOUGH MEMORY. An application used a Windows Sockets function that directly maps to a Windows function. The Windows function is indicating a lack of required memory resources. Note that this error is returned by the operating system, so the error number may change in future releases of Windows. Detailed (Berkeley) information for winsock 8, described as "Insufficient memory available.".
winsock-error.danielclarke.com
Winsock error 10035 (WSAEWOULDBLOCK)
http://winsock-error.danielclarke.com/10035.aspx
WSAEWOULDBLOCK - Resource temporarily unavailable. Basic (Microsoft) information for 10035 a.k.a. WSAEWOULDBLOCK. Detailed (Berkeley) information for winsock 10035, described as "Resource temporarily unavailable.". This is a temporary condition and later calls to the same routine may complete normally (also known as EAGAIN error in Berkeley Software Distribution version 4.3). The operation is underway, but as yet incomplete. Out of buffer space, so try again later or wait until FD WRITE. Peer Monitor - n...
winsock-error.danielclarke.com
Winsock error 10004 (WSAEINTR)
http://winsock-error.danielclarke.com/10004.aspx
WSAEINTR - Interrupted function call. Basic (Microsoft) information for 10004 a.k.a. WSAEINTR. A blocking operation was interrupted by a call to WSACancelBlockingCall. Detailed (Berkeley) information for winsock 10004, described as "Interrupted function call.". NOT same as Berkeley, but analogous. In WinSock it means a blocking operation was interrupted by a call to. Full list of Winsock Error codes. Peer Monitor - network monitoring tool.