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

10004 "Interrupted function call."

WSAEINTR (Winsock error number: 10004)

Microsoft say this about Winsock error 10004 - WSAEINTR:

A blocking operation was interrupted by a call to WSACancelBlockingCall.

Full details of Winsock TCP error 10004 - WSAEINTR:

Berkeley description: An asynchronous signal (such as SIGINTor SIGQUIT) was caught by the process during the execution of an interruptible function. If the signal handler performs a normal return, the interrupted function call will seem to have returned the error condition.

WinSock description: NOT same as Berkeley, but analogous. In WinSock it means a blocking operation was interrupted by a call to.

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 a blocking call. Whether to handle it as a fatal error or non-fatal error depends on the application and the context, so it's entirely up to you to decide.

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

Programming declarations for 10004 (WSAEINTR):

C#
long WSAEINTR = 10004 ;

VB.net
Dim WSAEINTR As Long = 10004

VB6
Dim WSAEINTR As Long
WSAEINTR = 10004