Sock error error = 10058

sock error error = 10058

It means that you have a connection timeout error with the server. Please check your Proxy settings and whether the Proxy Server has opened the SSL 443 port. ·. Hello, there could be some NT errors concerning tcpip - some are described in solution 105481. We got 10058 socket shutdown error (with a. This indicates some sort of non-recoverable error occurred during a database lookup. This may be because the database files (e.g. BSD-compatible. sock error error = 10058

watch the thematic video

ERROR 2002 (HY000): Can't connect to local MySQL socket'/var/run/mysqld/mysqld.sock'(2) Ubuntu

Summary of socket error codes (Windows and unix)

Article published: http://blog.csdn.net/hairetz/archive/2009/04/28/4129164.aspx

 
First count the error codes under windows

To query on the host, like a windows system, directly enter the command line: net helpmsg 1xxx.


A network connection error occurred Socket error #11001

It means that your computer cannot connect to the server. Please check your proxy settings and proxy-related accounts, or temporarily cancel the "personal firewall" of your anti-virus software.

· A network connection error Socket error #11004 occurred

It should be a network connection status problem, please check whether the network connection is normal.

· Socket error #10060 Connection Timed Out

It means that you have a connection timeout error with the server. Please check your Proxy settings and whether the Proxy Server has opened the SSL 443 port.

· Socket error #10061

Indicates that the server cannot establish a connection with you while the server is busy. Please try again later.

· Socket error #10022

Please update the Windows operating system components online. For users of Windows NT version 4.0, please download and install Service Pack 5 (inclusive) and above.

· Internal Server Error appears

The host is busy, please try again later.

· Socket error #10022 Invalid argument occurred during upload.

Please go online to update Windows operating system components (windows update). For users of Windows NT version 4.0, please download and install Service Pack 5 (inclusive) and above.

· Socket error #10054 Connection reset by peer occurred during upload

The reason is that the connection is interrupted by fire protection or proxy" or because you have installed an ip sharing device, please remove the ip sharing device first, and directly connect the computer to the adsl line and upload again.

· Socket error #10057 Connection reset by peer occurred during upload

The reason is that the system files are damaged. Please perform antivirus of the system and turn off antivirus software and firewall.


Socket Errors feedback in the INDY9 development program

The following is the error code and description of 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 sock error error = 10058 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 sock error error = 10058 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

 

WSAEADDRINUSE (10048) Address already in use

WSAECONNABORTED (10053) Software caused connection abort

WSAECONNREFUSED (10061) Connection refused

WSAECONNRESET (10054) Connection reset by peer

WSAEDESTADDRREQ (10039) Destination address required

WSAEHOSTUNREACH (10065) No route to host

WSAEMFILE (10024) Too many open files

WSAENETDOWN (10050) Network is down

WSAENETRESET (10052) Network dropped connection

WSAENOBUFS (10055) No buffer space available

WSAENETUNREACH (10051) Network is unreachable

WSAETIMEDOUT (10060) Connection timed out

WSAHOST_NOT_FOUND (11001) Host not found

WSASYSNOTREADY (10091) Network sub-system is unavailable

WSANOTINITIALISED (10093) WSAStartup() not performed

WSANO_DATA (11004) Valid name, no data of that type

WSANO_RECOVERY (11003) Non-recoverable query error

WSATRY_AGAIN (11002) Non-authoritative host found

WSAVERNOTSUPPORTED (10092) Wrong WinSock DLL version

 

The error codes of the unix platform are relatively few available on the Internet.

10001<o:p></o:p>
 EPERM<o:p></o:p>
 Not super-user<o:p></o:p>
 
10002           <o:p></o:p>
 ENOENT<o:p></o:p>
 No such file or directory<o:p></o:p>
 
10003<o:p></o:p>
 ESRCH<o:p></o:p>
 No such process<o:p></o:p>
 
10004<o:p></o:p>
 EINTR<o:p></o:p>
 interrupted system call<o:p></o:p>
 
10005<o:p></o:p>
 EIO<o:p></o:p>
 I/O error<o:p></o:p>
 
10006<o:p></o:p>
 ENXIO<o:p></o:p>
 No such device or address<o:p></o:p>
 
10007<o:p></o:p>
 E2BIG<o:p></o:p>
 Arg list too long<o:p></o:p>
 
10008<o:p></o:p>
 ENOEXEC<o:p></o:p>
 Exec format error <o:p></o:p>
 
10009<o:p></o:p>
 EBADF   sock error error = 10058 file number          <o:p></o:p>
 
10010<o:p></o:p>
 ECHILD  <o:p></o:p>
 No children                 <o:p></o:p>
 
10011<o:p></o:p>
 EAGAIN  <o:p></o:p>
 No more processes     <o:p></o:p>
 
10012<o:p></o:p>
 ENOMEM      <o:p></o:p>
 Not enough core<o:p></o:p>
 
10013<o:p></o:p>
 EACCES       <o:p></o:p>
 Permission denied<o:p></o:p>
 
10014<o:p></o:p>
 EFAULT <o:p></o:p>
 Bad address               <o:p></o:p>
 
10015<o:p></o:p>
 ENOTBLK<o:p></o:p>
 Block device required<o:p></o:p>
 
10016<o:p></o:p>
 EBUSY   <o:p></o:p>
 Mount device busy      <o:p></o:p>
 
10017<o:p></o:p>
 EEXIST  <o:p></o:p>
 File exists                    <o:p></o:p>
 
10018<o:p></o:p>
 EXDEV   <o:p></o:p>
 Cross-device link <o:p></o:p>
 
10019<o:p></o:p>
 ENODEV       <o:p></o:p>
 No such device           <o:p></o:p>
 
10020<o:p></o:p>
 ENOTDIR      <o:p></o:p>
 Not a directory            <o:p></o:p>
 
10021<o:p></o:p>
 EISDIR<o:p></o:p>
 Is a directory        <o:p></o:p>
 
10022<o:p></o:p>
 EINVAL<o:p></o:p>
 Invalid argument         <o:p></o:p>
 
10023<o:p></o:p>
 ENFILE<o:p></o:p>
 File table overflow       <o:p></o:p>
 
10024<o:p></o:p>
 EMFILE<o:p></o:p>
 Too many open files   <o:p></o:p>
 
10025<o:p></o:p>
 ENOTTY<o:p></o:p>
 Not a typewriter           <o:p></o:p>
 
10026<o:p></o:p>
 ETXTBSY<o:p></o:p>
 Text file busy<o:p></o:p>
 
10027<o:p></o:p>
 EFBIG    <o:p></o:p>
 File too large<o:p></o:p>
 
10028<o:p></o:p>
 ENOSPC<o:p></o:p>
 No space left on device<o:p></o:p>
 
10029<o:p></o:p>
 ESPIPE<o:p></o:p>
 Illegal seek<o:p></o:p>
 
10030<o:p></o:p>
 EROFS<o:p></o:p>
 Read only file system<o:p></o:p>
 
10031<o:p></o:p>
 EMLINK<o:p></o:p>
 Too many links<o:p></o:p>
 
10032<o:p></o:p>
 EPIPE<o:p></o:p>
 Broken pipe<o:p></o:p>
 
10033<o:p></o:p>
 <o:p> </o:p>
 <o:p> </o:p>
 
10034<o:p></o:p>
 <o:p> </o:p>
 <o:p> </o:p>
 
10035<o:p></o:p>
 ENOMSG<o:p></o:p>
 No message of desired type<o:p></o:p>
 
10036<o:p></o:p>
 EIDRM   <o:p></o:p>
 Identifier removed<o:p></o:p>
 
10037<o:p></o:p>
 ECHRNG       <o:p></o:p>
 Channel number out of range<o:p></o:p>
 

 

This article is from the CSDN blog, please indicate the source for reprinting: http://blog.csdn.net/hairetz/archive/2009/04/28/4129164.aspx

Socket Error table

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 sock error error = 10058 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

WSAEADDRINUSE (10048) Address already in use
WSAECONNABORTED (10053) Software caused connection abort
WSAECONNREFUSED (10061) Connection refused
WSAECONNRESET (10054) Connection reset by peer
WSAEDESTADDRREQ (10039) Destination address required
WSAEHOSTUNREACH (10065) No route to host
WSAEMFILE (10024) Too many open files
WSAENETDOWN (10050) Network is down
WSAENETRESET (10052) Network dropped connection
WSAENOBUFS (10055) No buffer space available
WSAENETUNREACH (10051) Network is unreachable
WSAETIMEDOUT (10060) Connection timed out
WSAHOST_NOT_FOUND (11001) Host not found
WSASYSNOTREADY (10091) Network sub-system is unavailable
WSANOTINITIALISED (10093) WSAStartup() not performed
WSANO_DATA (11004) Valid name, no data of that type
WSANO_RECOVERY (11003) Non-recoverable query error
WSATRY_AGAIN (11002) Non-authoritative host found
WSAVERNOTSUPPORTED (10092) Wrong WinSock DLL version
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Common SOCKET error return code (transfer)
WSAEINTR (10004) Interrupted system call.
When a blocking WinSock function is interrupted by WSACancelBlockingCall(), the blocking function will get the error WSAEINTR message. Readers should note that when your program uses WSACancelBlockingCall to interrupt a blocking function, you must write code for the blocking function to handle the WSAEINTR error message, otherwise your program may have some unexpected errors.
In principle, this error may occur in all functions that can be performed in blocking mode.
WSAEBADF (10009) Wrong file code
In the Berkeley socket interface, the file descriptor and the socket descriptor are connected. Opening a socket can be thought of as opening a file. The meaning of WSAEBADF in the Berkeley socket interface refers to the wrong socket descriptor. The wrong socket descriptor may be an unopened socket or a closed socket.
There is a common error code WSAENOTSOCK in WinSock, which is used to specify the socket descriptor of the error. For details, please refer to the WSAENOTSOCK section.
WSAEACCES (10013) No such permission
For Berkeley socket interface functions, the reason for this error is usually to open a file or socket that does not have the permission to open. For example, sock error error = 10058, on UNIX, ordinary users cannot open SOCK_RAW sockets, usually super users have this permission. If a normal user attempts to open the socket of SOCK_RAW, they will get this error message.
For the WinSock API function interface, there are two functions that cause this error: send() and sendto(). When sending data using send() or sendto(), set the destination address to the broadcast address, but does not call setsockopt() to set the SO_BROADCAST option, a WSAEACCES error will occur.
WSAEFAULT (10014) Wrong memory address The
system has detected the use of the wrong memory address. When calling the WinSock function, parameters are sock error error = 10058 passed in as indicators. This indicator may point to a structure, such as a sockaddr_in structure, or point to a data buffer. The WSAEFAULT error occurs when the program accidentally passes in a pointer that is not pointed to by the wrong memory. In addition, this error can also occur when the memory block pointed to by the indicator is too small.
WSAEINVAL (10022) Parameter error
If incorrect parameters are passed to the WinSock function, it will cause the error WSAEINVAL. If the parameter is a structured indicator, filling the structure with incorrect values ​​will also cause this error. For example, the how() parameter of the shutdown() function can only be 0, 1, or 2. If it is set to other values, this error will occur.
In the design of network programs, there is usually a certain sequence of calls between functions and functions. If this sequence is not followed, this error will also occur. Below is a detailed description of each related function, sock error error = 10058.
Function
Timing of the error when
accept()
calls accept() before calling listen() successfully
bind()
has successfully called bind() function and specified the name of the
getstockname()
did not call bind() function specifies the socket name
listen()
already connected or the socket does not call bind() function to specify the socket name
recv() and recvfrom()
For datagram sockets, the socket does not call bind() function to specify the IP address, port, protocol, sock error error = 10058, etc.; Stream socket, the connection has not been established
send() and sendto()
For datagram socket, the socket does not call bind() function to specify the IP address, port, protocol, sock error error = 10058, etc.; for stream socket, the connection has not been established. In
principle, all functions have parameters If the value that can be set has a certain range, or has some specific values, these functions may cause this error.
WSAEMFILE (10024) Too many open files
The explanation of the Berkeley socket interface is to open too many files, exceeding the limit on the number of open files. In Berkeley socket, the file and socket opening are described by file descriptor. WinSock is different from files for sockets. The meaning of WSAEMFILE in WinSock is to open too many sockets.
This program usually occurs when too many network programs are executed on the same machine, so that too many sockets are opened. Another error that can be avoided is that the application does not properly close unused sockets, causing the socket resources to run out.
WSAEWOULDBLOCK (10035) Blocking
function function This error occurs when the function hp, system error 86 01 is performed in a non-blocking mode, and the function function is not completed when the function function returns sock error error = 10058 the moment. For example, suppose send() sends a piece of data to the remote host in a non-blocking manner, and suppose the function returns with the error WSAEWOULDBLOCK, which means that this piece of data cannot be sent in this send() function call.
For the connect() function, this error indicates that the remote host has not been successfully connected, and the connection request is in progress. If your program uses the setsockopt() function to set the time limit with SO_LINGER, this error may occur when calling closesocket().
For the asynchronous network data function (WSAAsyncGetXXXXByYYYY()), a WSAEWOULDBLOCK error is obtained, indicating that the network data to be queried is currently unavailable. This is usually a temporary error, and the application may succeed in calling the same function later.
WSAEINPROGRESS (10036) has a blocking function being executed.
For each sock error error = 10058 or thread, WinSock only allows "one" blocking function to be executed. If a blocking function is being executed and the WinSock function is called, the function will return a WSAEINPROGRESS error.
This error can also occur in functions that require a long execution time, sock error error = 10058, such as connect(). There is a situation like this: When the "non-blocking" connect() function is executed twice, because it is a non-blocking connect(), the first call returns the WSAEWOULDBLOCK error code. At this time, the connection request has not been completed, and the second connect() call will get a WSAEINPROGRESS error.
Our suggestion is to add WSAIsBlocking() before the function call where this error may occur to determine whether there is a blocking function being executed. If so, we may need to cancel the ongoing blocking function, or cancel what we currently want to do.
WSAEALREADY (10037) Function has been completed
The meaning of this error is very different in the interpretation of the Berkeley socket interface and the WinSock function. The explanation of the Berkeley socket interface is that the function has been completed; in WinSock, WSAEALREADY means: "The asynchronous event you want to cancel has been cancelled!", that is, when you call WSACancelAsyncRequest() to try to cancel An asynchronous event, and the event has been cancelled.
WSAENOTSOCK (10038) Illegal sockets
are usually passed in as a parameter to the WinSock function with a socket descriptor. If the socket represented by the socket descriptor is not opened correctly or is not opened at all, the function will get a WSAENOTSOCK error. In principle, as long as the function passed in as a parameter with the socket descriptor, there is a possibility of a WSAENOSOCK error.
WSAEDESTADDRREQ (10039) requires the address of the other party.
When you want to send data to a remote machine, you must specify the address (and port, etc.) of the other sock error error = 10058 to deliver it correctly. Check to see if your application correctly fills in the other party’s sockaddr structure when calling connect() or sendto().
WSAEMSGSIZE (10040) The message is too long and the buffer cannot be accommodated.
This error occurs because the message data is too large and the buffer cannot be accommodated. The buffer here may be specified by the user or used internally by the system. There are four functions that can cause this error: The timing of the
function
error occurs when
recv(), recvform()
uses datagram socket to receive data, if the buffer length specified by recv(), recvform() is less than the received datagram, then Too long datagram will be discarded and tell the function WSAEMSGSIZE this error
send(), sendto() When
using datagram socket to send data, if the sent data buffer is larger than the maximum length of datagram that WinSock can transmit, then send() and sendto () Return the WSAEMSGSIZ error message
WSAEPROTOTYPE (10041) Wrong protocol type
The reason for the error is that a protocol not supported by WinSock is specified in the socket() function call. For example, you cannot set the steam socket (SOCK_STREAM) to use UDP protocol for transmission (IPPRO_UDP). Stream socket does not support UDP protocol. If you really want to test, the program deliberately calls socket() like this: hSock=socket(AF_INET, SOCK_STREAM, IPPROTO_UDP); you will find that such a socket() function call will get a WSAEPROTONOSUPPORT error. This is obviously wrong, it should be WSAEPROTOTYPE error. The error WSAEPROTOTYPE indicates that the wrong protocol is specified, sock error error = 10058, and the specified protocol is supported by the address family (protocol family), but does not apply to the socket type. In the above example, the UDP protocol belongs to the AF_INET address family, but it cannot be used on the stream socket (SOCK_STREAM socket). The error of WSAEPROTONOSUPPORT indicates that the specified protocol is not supported by the protocol family, which is a bit different from WSAEPROTOTYPE in meaning.
In fact, the difference between WSAEPROTOTYPE and WSAEPROTONOSUPPORT is minimal. When developing network programs, sock error error = 10058, both of these errors represent the same situation-protocol specification errors.
In short, you will never be able to try this error WSAEPROTOTYPE, sock error error = 10058.
WSAENOPROTOOPT (10042) Wrong protocol option (option)
This error is mainly for the getsockopt() and setsockopt() functions. These two functions can have different functions by setting different options with parameters. There are more or less restrictions on each option. For example, sock error error = 10058, some options can only be used in stream sockets, and some can only be used in datagram sockets. If these restrictions are violated, sock error error = 10058, this error will occur. Please see the table below:
SO_DONTLINGER
SO_KEEPALIVE
SO_LINGER
SO_OOBINLINE
TCP_NODELAY
Datagram socket (SOCK_DGRAM) These options are not supported
SO_DEBUG
SO_DONTROUTE
SO_RCVBUF
SO_SNDBUF
TCP_NODELAY
core of some vendor WinSock TCP/IP protocol does not support these options
SO_ACCEPTCONN
SO_ERROR
SO_TYPE
these options apply only to getsockopt () function, can not act on the setsockopt () Function
WSAEPROTONOSUPPORT (10043) Unsupported protocol
WinSock protocol core does not support the specified communication protocol. For example, when you use the socket() function, the second parameter is specified as SOCK_STREAM, and the third parameter is specified as IPPROTO_ICMP, so the socket() call will get the error WSAEPROTONOSUPPORT. WinSock version 1. 1 does not support the ICMP protocol, sock error error = 10058, so if you call socket() to specify the ICMP protocol, an error will occur. In fact, there is more to the WSAEPROTONPSUPPORT error. See WSAEPROTOTYPE for details.
Socket type not supported by WSAESOCKTNOSUPPORT (10044)
The current WinSock version does not support the socket type specified by the function. For example, the WinSock protocol core developed completely based on the WinSock version 1.1 specification does not support the socket type SOCK_RAW. When calling the socket() function, sock error error = 10058, the address family selects AF_INET (PF_INET) and the socket type selects SOCK_RAW, this error will occur.
The core of the WinSock protocol developed by some manufacturers provides many different functions in addition to supporting the specifications of the WinSock version 1.1 specification. We recommend that you use these additional functions when developing your program, and please consider the compatibility with other environments.
The WSAEOPNOTSUPP (10045) function does not support this type of socket
function does not support the current socket type. For example, the accept() and listen() functions can only work on connection-oriented sockets (stream sockets), that is, stream sockets. For recv(), recvform(), send() and sendto() functions, MSG_OOB can only be used for connection-oriented sockets.
WSAEPFNOSUPPORT (10046) Unsupported protocol family The
current WinSock protocol core does not support the specified protocol family. This error is very similar to WSAEAFNOSUPPORT. Currently, this error has been replaced by WSAEAFNOSUPPORT. Readers can refer to the description of WSAEAFNOSUPPORT.
WSAEAFNOSUPPORT (10047) Unsupported address family The license does
not support the specified address family. For the socket() function, the reason for the error is that the function transfers the wrong parameter. For functions that take the sockaddr structure as a parameter, the reason for the error is often that the network protocol does not support the address family specified in the sockaddr structure (sin_family member).
WSAEADDRINUSE (10048) address has been assigned
The specified "address" is in use. The address here refers to the name of the socket, which consists of three parts: protocol, port and IP address. This error usually occurs because the port is already occupied by other applications when the application tries to use the bind() function to specify the port. This happens when two server programs of the same nature (specify the same socket name) are executed on the same host. The second program will get this error message because the first program occupies a port first.
Another common situation is to use bind() to specify the port of the socket when writing a client program. This error often occurs. It's not that you can't use bind() to specify the socket port, but you can't determine whether the specified port is being used by other programs when the program is running. Usually the bind() function is rarely called in the client program, and the general client program is to let the system help you choose an appropriate port.
In addition, applications can use the SO_REUSEADDR option of setsockopt() to allow the port to be reused, sock error error = 10058, but we do not encourage this. This may cause problems for the TCP/IP core in judging applications.
WSAEADDRNOTAVAIL (10049) Unable to specify the address
The cause of the error is usually that the machine should not have an address, sock error error = 10058. The address here consists of three parts: network protocol, port and IP address.
In the Berkeley socket interface, when calling bind(), if the specified IP address is not the address that the local machine should have, this error will occur. When calling connect() or sendto() function, if sin_port in the sockaddr_in structure is filled with "0", this will also cause this error (EADDRNOTAVAIL error on UNXI).
For the WinSock function, the timing of the error is similar to that of the Berkeley socket function. Both bind() and connect() will cause such errors.
For the WinSock function, the timing of the error is similar to that of the Berkeley socket function. Both bind() and connect() will cause such errors. The WinSock version 1.1 specification does not mention that the bind() function will cause a WSAEADDRNOTAVAIL error, but according to our test results, bind() can also cause such an error.
WSAENETDOWN (10050) Network error The
lower network system has a problem, and the WinSock function cannot be executed. This is a very serious problem, which will cause almost all WinSock function calls to fail. If there is an error in your WinSock function, sock error error = 10058, then please check your network card, network card driver and your WinSock protocol core.
WSAENETUNREACH (10051) Cannot connect to the specified network.
In the Berkeley socket interface, sock error error = 10058, this error means that the network system of the other party cannot be contacted. In the WinSock 1.1 specification, WSAENETUNREACH is connected to ETHOSTUNREACH in the Berkeley socket interface.
WSAENETRESET (10052) The network has been reset. The
other party's host has an error and rebooted. You will get this error when calling functions related to sending data on the local host. For the setsockopt() function, the reason for this error is an attempt to set SO_KEEPALIVE on a timeout connection, sock error error = 10058.
WSAECONNABORTED (10053) Connection interruption
After the connection is established, when there is some reason that the TCP/IP protocol core continuously resends data, and the resend fails, the TCP/IP protocol interrupts the connection. At this point, the application will receive the error WSACONNABORTED.
WSAECONNRESET (10054) The connection has been reset
by the other party. The connection has been forcibly interrupted by the other party's system. If the TCP/IP protocol core detects a connection problem with the stream socket, it will send a message indicating that the connection is reset (reset) to the other party. At this time, the other program will get the error message of WSAECONNRESET.
WSAENOBUFS (10055) The buffer is too small.
WinSock core cannot allocate enough buffer to execute the program. The occurrence of this error is related to the entire Windows system resources. If the resources available for the entire Windows itself are few, there are few programs that can be executed simultaneously. It is also possible that "bad" applications have been executed, and system resources (such as memory) are not used and returned normally. Or the abnormal shutdown of some applications will also occupy system resources.
WSAEISCONN (10056) socket is already connected.
Network functions usually have a certain calling sequence, and sock error error = 10058 functions cannot be called after they are successfully called, otherwise an error will occur. When the connection is established, the client program calls () successfully, and the server program calls accept() successfully. At this time, if the client program calls the connect() function again, it will get the error WSAEISCONN, which means that the socket is already connected. This error will also occur if the client program calls the listen() function, indicating that this function should not be called at this time. For the server program, if the socket is already connected and the program calls the connect() function, it will also get the error WSAEISCONN.
The above error occurs on the stream socket, because the stream socket will establish a connection. For datagram sockets, multiple successful connect() function calls are allowed (for datdgram sockets, the purpose of calling the connect() function is not to establish a connection). The reason for this error in the datagram socket is that in the sendto() function, when the sendto() is called to send the datagram, if the address of the other party is filled with INADDR_ANY("0.0.0.0") and the port is filled with 0 (in the sockaddr_in structure)It will cause the error WSAEISCONN, sock error error = 10058.
WSAENOTCONN (10057) socket has not been connected.
Network functions usually have a certain calling sequence. Some functions must be called successfully before a certain function can be called. The reason for the WSAENOTCONN error is obvious, that is, before the connection is established, sock error error = 10058, if you try to get data from the other party or send data to the other party, the error WSAENETCONN will occur.
For example, for a stream socket, if you call send() to try to send data before the connection is established, or call recv() to try to get data, this error will occur, telling you that the socket has not yet established a connection. If you call the getpeername() function to try to get the socket connected to the other party, of course this error will occur. For the function setsockopt(), if SO_KEEPALIVE is set, but the connection has been interrupted, the error WSAENETCONN will also occur.
Beginners may not check whether the function call is wrong after calling the connect() function, so that they do not know whether the connection has been established correctly.
WSAESHUTDOWN (10058) socket has been closed
This error code means that no more data can be sent because the socket has been closed by the shutdown() function. When you close the socket with shutdown(), the TCP/IP protocol core of WinSock will close the socket's transmission or reception function. One thing to note is that this error will only appear in stream sockets.
WSAETOOMANYREFS (10059) Too many references, resource exhaustion
The explanation in the UNIX operating system means that the core resources of the system are exhausted. However, there is no function in the WinSock 1.1 specification that will cause this error.
WSAETIMEDOUT (10060) Connection timeout (timeout)
When the program tries to use connect() to connect to a remote host, the host has never responded. After a period of time, the TCP/IP protocol core will return a connect() letter Type WSAETIMEDOUT this error message. The reason for this error may be a problem with the system of the remote host that the program is connecting to, or there is no such host at all. There is also a possible cause that there is a problem with the local machine's network system, causing the local host to fail to communicate with the remote host. Check the settings of your network system to see if there are any improperities, such as the settings of the gateway, the comparison between the host name and the network address in the host name table (hosts), sock error error = 10058, etc.
WSAECONNREFUSED (10061) Connection refused The
connection request was rejected by the other party's machine, and the connection could not be established with the other party. This error is not because of a problem with the network system, but because the server program of the other machine refused the connection request of the client program, or the server program does not exist at all. When the TCP/IP core receives a connection request, it will check to see if there is a port monitored by a server program in the system that is the port that the connection request needs to connect to. If there is no such server program, the TCP/IP core will reject a WSAECONNREFUSED Give the other program.
There are usually several reasons for this error. The user may connect to the wrong remote host or the wrong port, or the remote host and port are correct, but the server program is not executed. Check to see if the sockaddr_in structure in the program is filled in incorrectly? Is the IP address and port in sockaddr_in arranged in network byte order?
WSAELOOP (10062) Too many levels of symbolic links (Symbolic links)
In the UNIX operating system, this error means that the path refers to too many symbolic links (symbolic links).
WSAENAMETOOLONG (10063) The file name is too long.
In the UNIX operating system, this error means that the path name (including the file name) of the file to be opened is too long.
WSAEHOSTDOWN (10064) The opposite host is shut down.
In the explanation of Berkeley socket interface, the reason for this error is when the remote host shuts down or the system has a problem.
WSAEHOSTUNREACH (10065) Unable to contact the opposite host.
In the Berkeley socket interface, this error means that the opposite host cannot be contacted. In WinSock, there are similar error codes. Readers can refer to the description of the error in WSAENETUNREACH.
WSAEPROCLIM (10067) Too many processes.
A Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously. WSAStartup() may fail with this error if the limit has been reached.
WSASYSNOTREADY (10091) The host network system is not yet ready. The
local host network system is not yet functioning normally. If this error occurs, readers may want to check if there is a file named WINSOCK.DLL (or the 32-bit version of WSOCK32.DLL)? Is this file stored in the correct path?
WSAVERNOTSUPPORTED (10092) Unsupported WinSock.DLL version error occurs The reason is that the WinSock version specified when calling the WSAStartup() function is not supported by the existing WinSock version. If this error occurs, the reader must determine the version of WinSock in the local Windows system and the supported version of the version, sock error error = 10058, etc. Usually the newer version can support both the old and new versions of WinSock. It is recommended that readers use the newer WinSock version.
WSANOTINITIALISED (10093) WSAStartup() was not executed The
application did not call WSAStartup() or the call to WSAStartup() failed. The application must successfully call WSAStartup() to use WinSock.DLL, sock error error = 10058, otherwise this error message will appear.
WSAEDISCON (10101) Graceful shutdown in progress.
Returned by WSARecv(), WSARecvFrom() to indicate the remote party has initiated a graceful shutdown sequence.
WSATYPE_NOT_FOUND (10109) Class type not found
The specified class was not found.
WSAHOST_NOT_FOUND (11001) It has been confirmed that
the host cannot be found. This error occurs when you use the network data function to find the host's data and the host does not exist. The method to find network host data is usually to find the network name table (host file) of the local host first. If it can't find it, sock error error = 10058, then find it through DNS. If it can't find it anymore, it usually returns to the function like this error.
When such an error occurs, check to see if there is any problem with the host name interpretation setting of the local host. It is the DNS setting that is more likely to have a problem. Make sure whether it is the wrong DNS server. If the DNS server is correct, make sure that the DNS server is running. You can use the ping program to see if the DNS server is running. If there is no ping program, you can try to explain a certain host and see if the DNS server is operating normally.
WSATRY_AGAIN (11002) Cannot find the network data, but it has not been confirmed.
This pioneer deh 4000ub error-15 a temporary error. It tells you that the network data you are looking for cannot be found. You can try again.
WSANO_RECOVERY (11003) Unrecoverable error
For querying the host name, the reason for this error is caused by an error in the Domain Name System (DNS). These errors include DNS errors such as FORMERR, REFUSED, and NOTIMP. For details, please refer to the RFC1035 document on the domain sock error error = 10058 system.
For querying service and protocol data, the reason for this error is that the database for storing network data cannot be found. This database is usually a file on the local host, such as SERVICES and PROTOCOL.
WSANO_DATA (11004) The name is legal, but there is no such data
The query format is correct, but no such information exists. This is usually a temporary error. This data may be found on a different network data server, sock error error = 10058.
WSAPROVIDERFAILEDINIT (OS dependent) Unable to initialize a service provider.
Either a service provider's DLL could not be loaded (LoadLibrary() failed) or the provider's WSPStartup/NSPStartup function failed.
WSASYSCALLFAILURE (OS dependent) System call failure.
Returned when a system call that should never fail does. For example, if a call to WaitForMultipleObjects() fails or one of the registry APIs fails trying to manipulate the
protocol/namespace catalogs.
WSA_INVALID_HANDLE (OS dependent) Specified event object handle is invalid.
An application attempts to use an event object, but the specified handle is not valid.
WSA_INVALID_PARAMETER (OS dependent) One or more parameters are invalid.
An application used a WinSock function which directly maps to a Win32 function. The Win32 function is indicating a problem with one or more parameters.
WSAINVALIDPROCTABLE (OS dependent) Invalid procedure table from service provider.
A service provider returned a bogus proc table to WS2_32.DLL. (Usually caused by one or more of the function pointers being NULL.)
WSAINVALIDPROVIDER (OS dependent) Invalid service provider version number.
A service provider returned a sock error error = 10058 number other than 2.2.
WSA_IO_INCOMPLETE (OS dependent) Overlapped I/O event object not in signaled state.
The application has tried to determine the status of an overlapped operation which is not yet completed. Applications that use WSAGetOverlappedResult() (with the fWait flag set to false) in a polling mode to determine when an overlapped operation has completed will get this error code until the operation is complete.
WSA_IO_PENDING (OS dependent) Overlapped operations will complete later.
The application has initiated an overlapped operation which cannot be completed immediately. A completion indication will be given at a later time when the operation has been completed.
WSA_NOT_ENOUGH_MEMORY (OS dependent) Insufficient memory available.
An application used a WinSock function which directly maps to a Win32 function. The Win32 function is indicating a lack of required memory resources.7

Windows Sockets Error Codes

WSA_INVALID_HANDLE
6
Specified event object handle is invalid.
An application attempts to use an event object, but the specified handle is not valid.
WSA_NOT_ENOUGH_MEMORY
8
Insufficient memory available.
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.
WSA_INVALID_PARAMETER
87
One or more parameters are invalid.
An application used a Windows Sockets function which directly maps to a Windows function. The Windows function is indicating a problem with one or more parameters.
WSA_OPERATION_ABORTED
995
Overlapped operation aborted.
An overlapped operation was canceled due to the closure of the socket, or the execution of the SIO_FLUSH command in WSAIoctl.
WSA_IO_INCOMPLETE
996
Overlapped I/O event sock error error = 10058 not in signaled state.
The application has tried to determine the status of an overlapped operation which is not yet completed. Applications that use WSAGetOverlappedResult (with the fWait flag set to FALSE) in a polling mode to determine when an overlapped operation has completed, get this error code until the operation is complete.
WSA_IO_PENDING
997
Overlapped operations will complete later.
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.
WSAEINTR
10004
Interrupted function call.
A blocking operation was interrupted by a call to WSACancelBlockingCall.
WSAEBADF
10009
File handle is not valid.
The file handle supplied is not valid.
WSAEACCES
10013
Permission denied.
An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST).
Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4.0 with SP4 and later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4.0 with SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option.
WSAEFAULT
10014
Bad address.
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).
WSAEINVAL
10022
Invalid argument.
Some invalid argument was supplied (for example, sock error error = 10058, specifying an invalid level to the setsockopt function). In some instances, it also refers to the current state of the socket—for instance, calling accept on a socket that is not listening.
WSAEMFILE
10024
Too many open files.
Too many open sockets. Each implementation may have a maximum number of socket handles available, either globally, per process, or per thread.
WSAEWOULDBLOCK
10035
Resource temporarily unavailable.
This error is returned from operations on nonblocking sockets that cannot too many errors, reiniting completed immediately, for example recv when no data is queued to be read from the socket. It is a nonfatal error, and the operation should be retried later, sock error error = 10058. 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.
WSAEINPROGRESS
10036
Operation now in progress.
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.
WSAEALREADY
10037
Operation already in progress.
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.
WSAENOTSOCK
10038
Socket operation on nonsocket.
An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, sock error error = 10058, or for select, a member of an fd_set was not valid.
WSAEDESTADDRREQ
10039
Destination address required.
A required address was omitted from an operation on a socket. For example, this error is returned if sendto is called with the remote address of ADDR_ANY.
WSAEMSGSIZE
10040
Message too long.
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.
WSAEPROTOTYPE
10041
Protocol wrong type for socket.
A protocol was specified in the socket function call that does not support the semantics of the socket type requested. For example, the ARPA Internet UDP protocol cannot be specified with a socket type of SOCK_STREAM.
WSAENOPROTOOPT
10042
Bad protocol option.
An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call.
WSAEPROTONOSUPPORT
10043
Protocol not supported.
The requested protocol has not been configured into the system, or no implementation for it exists. For example, a socket call requests a SOCK_DGRAM socket, but specifies a stream protocol.
WSAESOCKTNOSUPPORT
10044
Socket type not supported.
The support for the specified socket type does not exist in this address family. For example, the optional type SOCK_RAW might be selected in a socket call, and the implementation does not support SOCK_RAW sockets at all.
WSAEOPNOTSUPP
10045
Operation not supported.
The attempted operation is not supported for the type of object referenced. Usually this occurs when a socket descriptor to a socket that cannot support this operation is trying to accept a connection on a datagram socket.
WSAEPFNOSUPPORT
10046
Protocol family not supported.
The protocol family has not been configured into the system or no implementation for it exists. This message has a slightly different meaning from WSAEAFNOSUPPORT. However, it is interchangeable in most cases, and all Windows Sockets functions that return one of these messages also specify WSAEAFNOSUPPORT.
WSAEAFNOSUPPORT
10047
Address family not supported by protocol family.
An address incompatible with the requested protocol was used. All sockets are created with an associated address family (that is, AF_INET for Internet Protocols) and a generic protocol type (that is, SOCK_STREAM). This error is returned if an incorrect protocol is explicitly requested in the socket call, or if an address of the wrong family is used for a socket, for example, in sendto.
WSAEADDRINUSE
10048
Address already in use.
Typically, sock error error = 10058, only one usage of each socket address (protocol/IP address/port) is permitted, sock error error = 10058. This error occurs if an application attempts to bind a socket to an IP address/port that has already been used for an existing socket, or a socket that was not closed properly, or one that is still in the process of closing. For server applications that need to bind multiple sockets to the same port number, consider using setsockopt (SO_REUSEADDR). Client applications usually need not call bind at all—connect chooses an unused port automatically. When bind is called with a wildcard address (involving ADDR_ANY), a WSAEADDRINUSE error could be delayed until the specific address is committed. This could happen with a call to another function later, including connect, listen, WSAConnect, or WSAJoinLeaf.
WSAEADDRNOTAVAIL
10049
Cannot assign requested address.
The 3d rpg editor runtime error 429 address is not valid in its context. This normally results from an attempt to bind to an address sock error error = 10058 is not valid for the local computer. This can also result from connect, sock error error = 10058, sendto, WSAConnect, WSAJoinLeaf, or WSASendTo when the remote address or port is not valid for a remote computer (for example, address or port 0).
WSAENETDOWN
10050
Network is down.
A socket operation encountered a dead network. This could indicate a serious failure of the network system (that is, the protocol stack that the Windows Sockets DLL runs over), the network interface, or the local network itself.
WSAENETUNREACH
10051
Network is unreachable.
A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host.
WSAENETRESET
10052
Network dropped connection on reset.
The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. It can also be returned by setsockopt if an attempt is made to set SO_KEEPALIVE on a connection that has already failed.
WSAECONNABORTED
10053
Software caused connection abort.
An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error.
WSAECONNRESET
10054
Connection reset by peer.
An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.
WSAENOBUFS
10055
No buffer space available.
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
WSAEISCONN
10056
Socket is already connected.
A connect request was made on an already-connected socket. Some implementations also return this error if sendto is called on a connected SOCK_DGRAM socket (for SOCK_STREAM sockets, the to parameter in sendto is ignored) although other implementations treat this as a legal occurrence.
WSAENOTCONN
10057
Socket is not connected.
A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using sendto) no address was supplied. Any other type of operation might also return this error—for example, setsockopt setting SO_KEEPALIVE if the connection has been reset.
WSAESHUTDOWN
10058
Cannot send after socket shutdown.
A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. By calling shutdown a partial close of a socket is requested, which is a signal that sending or receiving, or both have been discontinued.
WSAETOOMANYREFS
10059
Too many references.
Too many references to some kernel object.
WSAETIMEDOUT
10060
Connection timed out.
A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.
WSAECONNREFUSED
10061
Connection refused.
No connection could be made because the target computer actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server sock error error = 10058 running.
WSAELOOP
10062
Cannot translate name.
Cannot translate a name.
WSAENAMETOOLONG
10063
Name too long.
A name component or a name was too long.
WSAEHOSTDOWN
10064
Host is down.
A socket operation failed because the destination host is down. A socket operation encountered a dead host. Networking activity on the local host has not been initiated. These conditions are more likely to be indicated by the error WSAETIMEDOUT.
WSAEHOSTUNREACH
10065
No route sock error error = 10058 host.
A socket operation was attempted to an unreachable host. See WSAENETUNREACH.
WSAENOTEMPTY
10066
Directory not empty.
Cannot remove a directory that is not empty.
WSAEPROCLIM
10067
Too many processes.
A Windows Sockets implementation may have a limit on the number of applications that can use it simultaneously. WSAStartup may fail with this error if the limit has been reached.
WSAEUSERS
10068
User quota exceeded.
Ran out of user quota.
WSAEDQUOT
10069
Disk quota exceeded.
Ran out of disk quota.
WSAESTALE
10070
Stale file handle reference.
The file handle reference is no longer available.
WSAEREMOTE
10071
Item is remote.
The item is not available locally.
WSASYSNOTREADY
10091
Network subsystem is unavailable.
This error is returned by WSAStartup if the Windows Sockets implementation cannot function at this time because the underlying system it uses to provide network services is currently unavailable. Users should check:
  • That the appropriate Windows Sockets DLL file is in the current path.
  • That they are not trying to use more than one Windows Sockets implementation simultaneously. If there is more than one Winsock DLL on your system, sock error error = 10058, be sure the first one in the path is appropriate for the network subsystem currently loaded.
  • The Windows Sockets implementation documentation to be sure all necessary components are currently installed and configured correctly.
WSAVERNOTSUPPORTED
10092
Winsock.dll version out of range.
The current Windows Sockets implementation does not support the Windows Sockets specification version requested by the application. Check that no old Windows Sockets DLL files are being accessed.
WSANOTINITIALISED
10093
Successful WSAStartup not yet performed.
Either the application has not called WSAStartup or WSAStartup failed. The application may be accessing a socket that the current active task does not own (that is, trying to share a socket between tasks), or WSACleanup has been called too many times.
WSAEDISCON
10101
Graceful shutdown in progress.
Returned by WSARecv and WSARecvFrom to indicate that the remote party has initiated a graceful shutdown sequence.
WSAENOMORE
10102
No more results.
No more results can be returned by the WSALookupServiceNext function.
WSAECANCELLED
10103
Call has sock error error = 10058 canceled.
A call to the WSALookupServiceEnd function was made while this call was still processing. The call has been canceled.
WSAEINVALIDPROCTABLE
10104
Procedure call table is invalid.
The service provider procedure call table is invalid. A service provider returned a bogus procedure table to Ws2_32.dll. This is usually caused by one or more of the function pointers being NULL.
WSAEINVALIDPROVIDER
10105
Service provider is invalid.
The requested service provider is invalid, sock error error = 10058. This error is returned by the WSCGetProviderInfo and WSCGetProviderInfo32 functions if the protocol entry specified could not be found. This error is also returned if the service provider returned a version number other than 2.0.
WSAEPROVIDERFAILEDINIT
10106
Service provider failed to initialize.
The requested service provider could not be loaded or initialized. This error is returned if either a service provider's DLL could not be loaded (LoadLibrary failed) or the provider's WSPStartup or NSPStartup function failed.
WSASYSCALLFAILURE
10107
System call failure.
A system call that should never fail has failed. This is a generic error code, returned under various conditions, sock error error = 10058.
Returned when a system call that should never fail does fail. For example, if a call to WaitForMultipleEvents fails or one of the registry functions fails trying to manipulate the protocol/namespace catalogs.
Returned when a provider does not return SUCCESS and sock error error = 10058 not provide an extended error code. Can indicate a service provider implementation error.
WSASERVICE_NOT_FOUND
10108
Service not found.
No such service is known. The service cannot be found in the specified name space.
WSATYPE_NOT_FOUND
10109
Class type not found.
The specified class was not found.
WSA_E_NO_MORE
10110
No more sock error error = 10058 No more results can be returned by the WSALookupServiceNext function.
WSA_E_CANCELLED
10111
Call was canceled.
A call to the WSALookupServiceEnd function was made while this call was still processing. The call has been canceled.
WSAEREFUSED
10112
Database query was refused.
A database query failed because it was actively refused.
WSAHOST_NOT_FOUND
11001
Host sock error error = 10058 found.
No such host is known. The name is not an official host name or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means that the specified name could not be found in the relevant database.
WSATRY_AGAIN
11002
Nonauthoritative host not found.
This is usually a temporary error during host name resolution and means that the local server did not receive a response from an authoritative server. A retry at some time later may be successful.
WSANO_RECOVERY
11003
This is a nonrecoverable error.
This indicates that some sort of nonrecoverable error occurred during a database lookup. This may be because the database files (for example, BSD-compatible HOSTS, SERVICES, or PROTOCOLS files) could not be found, or a DNS request was returned by the server with a severe error.
WSANO_DATA
11004
Valid name, no data record of requested type.
The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a host name-to-address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server). An MX record is returned but no A record—indicating the host itself exists, but is not directly reachable.
WSA_QOS_RECEIVERS
11005
QoS receivers.
At least one QoS reserve has arrived.
WSA_QOS_SENDERS
11006
QoS senders.
At least one QoS send path has arrived.
WSA_QOS_NO_SENDERS
11007
No QoS senders.
There are no QoS senders.
WSA_QOS_NO_RECEIVERS
11008
QoS no receivers.
There are no QoS receivers.
WSA_QOS_REQUEST_CONFIRMED
11009
QoS request confirmed.
The QoS reserve request has been confirmed.
WSA_QOS_ADMISSION_FAILURE
11010
QoS admission error.
A QoS error occurred due to lack of resources.
WSA_QOS_POLICY_FAILURE
11011
QoS policy failure.
The QoS request was rejected because the policy system couldn't allocate the requested resource within the existing policy.
WSA_QOS_BAD_STYLE
11012
QoS bad style.
An unknown or conflicting QoS style was encountered.
WSA_QOS_BAD_OBJECT
11013
QoS bad object.
A problem was encountered with some part of the filterspec or the provider-specific buffer in general.
WSA_QOS_TRAFFIC_CTRL_ERROR
11014
QoS traffic control error.
An error with the underlying traffic control (TC) API as the generic QoS request was converted for local enforcement by the TC API. This could be due to sock error error = 10058 out of memory error or to an internal QoS provider error.
WSA_QOS_GENERIC_ERROR
11015
QoS generic error.
A general QoS error.
WSA_QOS_ESERVICETYPE
11016
QoS service type error.
An invalid or unrecognized service type was found in the QoS flowspec.
WSA_QOS_EFLOWSPEC
11017
QoS flowspec error.
An invalid or inconsistent flowspec was found in the QOS structure.
WSA_QOS_EPROVSPECBUF
11018
Invalid QoS provider buffer.
Sock error error = 10058 invalid QoS provider-specific buffer.
WSA_QOS_EFILTERSTYLE
11019
Invalid QoS filter style.
An invalid QoS filter style was used.
WSA_QOS_EFILTERTYPE
11020
Invalid QoS filter type.
An invalid QoS filter type was used.
WSA_QOS_EFILTERCOUNT
11021
Incorrect QoS filter count.
An incorrect number of QoS FILTERSPECs were specified in the FLOWDESCRIPTOR.
WSA_QOS_EOBJLENGTH
11022
Invalid QoS object length.
An object with an invalid ObjectLength field was specified in the QoS provider-specific buffer.
WSA_QOS_EFLOWCOUNT
11023
Incorrect QoS flow count.
An incorrect number of flow descriptors was specified in the QoS structure.
WSA_QOS_EUNKOWNPSOBJ
11024
Unrecognized QoS object.
An unrecognized object was found in the QoS provider-specific buffer.
WSA_QOS_EPOLICYOBJ
11025
Invalid QoS policy object.
An invalid policy object was found in the QoS provider-specific buffer.
WSA_QOS_EFLOWDESC
11026
Invalid QoS flow descriptor.
An invalid QoS flow descriptor was found in the flow descriptor list.
WSA_QOS_EPSFLOWSPEC
11027
Invalid QoS provider-specific flowspec.
An invalid or inconsistent flowspec was found in the QoS provider-specific buffer.
WSA_QOS_EPSFILTERSPEC
11028
Invalid QoS provider-specific filterspec.
An invalid Canon mp160 e27 error code was found in the QoS provider-specific buffer.
WSA_QOS_ESDMODEOBJ
11029
Invalid QoS shape discard mode object.
An invalid shape discard mode object was found in the QoS provider-specific buffer.
WSA_QOS_ESHAPERATEOBJ
11030
Invalid QoS shaping rate object.
An invalid shaping rate object was found in the QoS provider-specific buffer.
WSA_QOS_RESERVED_PETYPE
11031
Reserved policy QoS element type.
A reserved policy element was found in the QoS provider-specific buffer.

SFTP or SSH network connection errors


Contents




Failed to establish SFTP connection error code 103. - The semaphore cannot be set again

Our customers often write us that establishing remote connection to ESX server via SFTP results in following error:

Failed to establish SFTP connection error code 103. - The semaphore cannot be set again

We have investigated this issue and discovered that this problem may appear at the ESX 4.x versions that don't have SFTP support. This is a network error message, and normally it appears when a number of connections from one client exceed the predefined limit at the server, however ESX 4.x doesn't have proper SFTP support which is required to gain direct disk access via a network. If you see such error, you have following options:

  • close other programs that may have already established connections to ESX such as Putty or other SFTP client. Try to reconnect when resources are free.

  • upgrade your ESX to 5.0+ version to access it via SSH,

  • access VMFS disk(s) or drive images directly using some dedicated, stand alone, physical Windows PC.

Actually we recommend everyone to use the last option, it could require more effort, however, you will reduce recovery time a lot.

Please note: accessing VMFS via network protocols like SSH or SFTP severely reduce performance. Our test configuration achieves a scan speed of approx 340Gb per hour for local disk access for a single HDD. Compare it with 0.75Gb per hour via SFTP/SSH on a 1Gbit LAN connection.


Connection lost due to error 10053. Try again read?

The server has closed the connection(a timeout is a common reason) without properly notifying the client. Reconnect to the SSH server in order to restore the operation.


FTP failed (Error: Connection lost due to error 10058)

10058 SSH <b>sock error error = 10058</b> error

The issue was caused by outdated SSH library that allowed authentication by password only. Since May 25 2021 the SSH library was updated starting from the version of VMFS Recovery v4.9.3.5

In general, an error code 10058 occurs as the result of a socket previously shut down or partially closed. Once the socket is in this state, then it will not allow further data transmissions across the connection.

If you encountered this issue, please either create ANSI compatible credentials or use an alternative method to access VMFS datastore. I remind you, that SSH is still the slowest of them all.

If you would like to obtain more information about this problem you may be interested to check the following links: MS TechNet description, MSDN error codes, similar problem explained with VmWare Virtual Desktop Manager.


Connection failed (Error code: 96260)

This error happens when SSH fails to resolve domain name. Please use IP address instead.




Return to contents

DominoPDF uses HTTP to process a URL and convert the resulting HTML output to PDF. In some cases the underlying HTTP protocol may return an error (not the fault of DominoPDF) and this error will be flagged in the DominoPDF log file (if enabled).

Below we have provided a list of common Socket errors which will help in establishing the cause of the issue and decide resolution.

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 sock error error = 10058 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

0 Comments

Leave a Comment