Winsock Error Codes - Brought to you by Winsock-Error.com

10037 "Operation already in progress."

WSAEALREADY (Winsock error number: 10037)

Microsoft say this about Winsock error 10037 - WSAEALREADY:

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.

Full details of Winsock TCP error 10037 - WSAEALREADY:

Berkeley description: An operation was attempted on a non-blocking object that already had an operation in progress.

WinSock description: Unlike Berkeley Sockets, in WinSock WSAEALREADY means that the asynchronous operation you attempted to cancel has already been canceled. However, there's little distinction between WSAEALREADY and WSAEINVAL since a WinSock DLL cannot tell the difference between an asynchronous operation that has been cancelled and one that was never valid.

   
This page is designed to help you to understand Winsock TCP error 10037. It will not necessarily mean you can instantly fix issues when your computer tells you that Winsock is having problems with code 10037, rather it will give you the necessary background information to help solve the matter.

Programming declarations for 10037 (WSAEALREADY):

C#
long WSAEALREADY = 10037 ;

VB.net
Dim WSAEALREADY As Long = 10037

VB6
Dim WSAEALREADY As Long
WSAEALREADY = 10037