A blocking operation is currently executing and takes a long time to complete. 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.

Winsock description: The Windows Sockets definition of this error is very different from Berkeley Sockets. Winsock only allows a single blocking operation to be outstanding per task (or thread), and if you make any other function call (whether or not it references that or any other socket) the function fails with the WSAEINPROGRESS error. It means that there is a blocking operation outstanding.

It is also possible that Winsock might return this error after an application calls connect a second time on a non-blocking socket while the connection is pending (i.e. after the first failed with WSAEWOULDBLOCK). This is what occurs in Berkeley Sockets.

WSAEINPROGRESS – Error 10036

This error happens when the winsock buffer of either the client or server side become full. It is a nonfatal error, and it is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a nonblocking SOCK_STREAM socket, since some time must elapse for the connection to be established.

Which are the causes for error 10035?
• You’re trying to send a massive amount of information through the socket, so the output buffer of the system becomes full.
• You’re trying to send data through the socket to the remote host, but the remote host input buffer is full (because it’s receiving data slower than you’re sending it).

When you send data – you really send it to the TCP/IP subsystem of your machine (ie winsock). The system buffers this data (in the OutBuffer) and begins sending it to the remote host as fast as it can (which of course is only as fast as the receiver can receive it). If the OutBuffer gets filled, because you are sending data faster than the system can send it – you’ll get Winsock error 10035.
In order to deal with this when using IPPort or IPDaemon, just catch the Winsock 10035 error and wait for the component’s ReadyToSend event to fire (this fires when the system is able to send data again). At that time, you can continue sending your data, starting with that which failed. For example (C# – if you need help with other languages let me know), the code below will loop until the length of the data to be sent is 0. If all goes normally, this loop will only be entered once and all of the data will be sent. After a while, if the input buffer fills up, the SetDataToSend inside the loop will fail with the Winsock 10035 error. The code will wait for the ReadyToSend event (the ready boolean flag), and loop. SetDataToSend will be called again, successfully.

Resources:

Winsock error 10035 means “Resource not available” or “Operation would block”

Download the Socket Error Repair Tool

No process may have more than a system-defined number of file descriptors open at a time. No more file handles are available, so no more files can be opened. Generically, the error means the network system has run out of socket handles.

Hot fix this error

There may be too many Winsock applications running simultaneously, but this is unlikely since most network systems have many socket handles available. This error also could occur if an application opens and closes sockets often, but doesn’t properly close the sockets (so it leaves them open, as “orphans”). To recover the orphaned sockets, you can try closing the application and restarting it to recover the open sockets; you may have to end all Winsock applications (to force an unload of the Winsock DLL). The source

Download the Socket Error Repair Tool

Solution: Some invalid argument was supplied (for example, specifying an invalid level to the setsockopt function). In some instances, it also refers to the current state of the socket.

Download the Socket Error Repair Tool

The system detected an invalid pointer address in attempting to use a pointer argument of a call. This error occurs if an application passes an invalid pointer value, or if the length of the buffer is too small. For instance, if the length of an argument, which is a sockaddr structure, is smaller than the sizeof(sockaddr).

The sockaddr structure varies depending on the protocol selected. Except for the sa_family parameter, sockaddr contents are expressed in network byte order.

In Windows Sockets 2, the name parameter is not strictly interpreted as a pointer to a sockaddr structure. It is presented in this manner for Windows Sockets compatibility. The actual structure is interpreted differently in the context of different address families. The only requirements are that the first u_short is the address family and the total size of the memory buffer in bytes is namelen.

Download Error 10014 Repair Tool for Free

Download the Socket Error Repair Tool

Errors on your system may be caused by invalid registry entries and outdated, corrupt drivers or an attempt was made to access a file (or, in some cases, a directory) in a way that is incompatible with the file’s attributes. For example, the error can occur when an attempt is made to read from a file that is not open, to open an existing read-only file for writing, or to open a directory instead of a file.

How to fix socket error 10013 :

1. In your firewall program, check your program permissions settings.

2. To identify errors in your system run a free registry scan. We recommend DriverScanner to check your PC for outdated drivers.

Another free program for scanning and fixing the socket error 10013

]]> http://www.fixerror.net/2009/05/socket-error-10013-permission-denied-error-code-0x271d/feed/ 2 http://www.fixerror.net/2009/05/socket-error-10004/ http://www.fixerror.net/2009/05/socket-error-10004/#comments Mon, 11 May 2009 07:48:54 +0000 Ezu http://www.fixerror.net/?p=107 Socket error 10004 – Interrupted function call

Solutions:A blocking operation was interrupted by a call to WSACancelBlockingCall.

The WSACancelBlockingCall function has been removed in compliance with the Windows Sockets 2 specification, revision 2.2.0.

The function is not exported directly by WS2_32.DLL and Windows Sockets 2 applications should not use this function. Windows Sockets 1.1 applications that call this function are still supported through the WINSOCK.DLL and WSOCK32.DLL.

Fix Error-10004. Download and install Regcure, a Microsoft Windows tool that will analyze your registry for missing, obsolete, and corrupt entries resulting from failed installations, incomplete un-installations, disabled drivers, and spyware applications.

Definition: A socket is one endpoint of a two-way communication link between two programs running on the network. A socket is bound to a port number so that the TCP layer can identify the application that data is destined to be sent.

A server application normally listens to a specific port waiting for connection requests from a client. When a connection request arrives, the client and the server establish a dedicated connection over which they can communicate. During the connection process, the client is assigned a local port number, and binds a socket to it. The client talks to the server by writing to the socket and gets information from the server by reading from it. Similarly, the server gets a new local port number (it needs a new port number so that it can continue to listen for connection requests on the original port). The server also binds a socket to its local port and communicates with the client by reading from and writing to it.

How we can fix socket error

Socket error 0 – Directly send error

Socket error 10004 – Interrupted function call

Socket error 10013 – Permission denied

Socket error 10014 – Bad address

Socket error 10022 - Invalid argument

Socket error 10024 – Too many open files

Socket error 10035 – Resource temporarily unavailable

Socket error 10036 – Operation now in progress

Socket error 10037 - Operation already in progress

Socket error 10038 – Socket operation on non-socket

Socket error 10039 – Destination address required

Socket error 10040 – Message too long

Socket error 10041 – Protocol wrong type for socket

Socket error 10042 – Bad protocol option

Socket error 10043 – Protocol not supported

Socket error 10044 – Socket type not supported

Socket error 10045 – Operation not supported

Socket error 10046 – Protocol family not supported

Socket error 10047 – Address family not supported by protocol family

Socket error 10048 – Address already in use

Socket error 10049 – Cannot assign requested address

Socket error 10050 – Network is down

Socket error 10051 - Network is unreachable

Socket error 10052 - Network dropped connection on reset

Socket error 10053 – Software caused connection abort

Socket error 10054 – Connection reset by peer

Socket error 10055 – No buffer space available

Socket error 10056 - Socket is already connected

Socket error 10057 – Socket is not connected

Socket error 10058 – Cannot send after socket shutdown

Socket error 10060 – Connection timed out

Socket error 10061 – Connection refused

Socket error 10064 – Host is down

Socket error 10065 – No route to host

Socket error 10067 – Too many processes

Socket error 10091 – Network subsystem is unavailable

Socket error 10092 - WINSOCK.DLL version out of range

Socket error 10093 – Successful WSAStartup not yet performed

Socket error 10094 – Graceful shutdown in progress

Socket error 11001 – Host not found

Socket error 11002 – Non-authoritative host not found

Socket error 11003 – This is a non-recoverable error

Socket error 11004 – Valid name, no data record of requested type

Here you can find the description of these errors