Winsock xp fix how to#

Overlapped I/O event object not in signaled state. An overlapped operation was canceled due to the closure of the socket, or the execution of the SIO_FLUSH command in WSAIoctl. The Windows function is indicating a problem with one or more parameters.

An application used a Windows Sockets function which directly maps to a Windows function. The Windows function is indicating a lack of required memory resources. An application used a Windows Sockets function that directly maps to a Windows function. An application attempts to use an event object, but the specified handle is not valid. Specified event object handle is invalid. Some error codes defined in the Winsock2.h header file are not returned from any function. Errors are listed in numerical order with the error macro name. The following list describes the possible error codes returned by the WSAGetLastError function.

Winsock xp fix how to#

The FormatMessage function can be used to obtain the message string for the returned error.įor information on how to handle error codes when porting socket applications to Winsock, see Error Codes - errno, h_errno and WSAGetLastError. These error codes and a short text description associated with an error code are defined in the Winerror.h header file.

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. The WSAGetLastError function returns the last error that occurred for the calling thread. For information, see the Handling Winsock Errors topic. Most Windows Sockets 2 functions do not return the specific cause of an error when the function returns.