MailSite services log various Network I/O errors
Internet congestion causes connection timeouts and it is common for Internet hosts to have trouble connecting to other hosts.
MailSite will automatically retry delivery attempts for outgoing mail.
Remote hosts will automatically retry delivery attempts for incoming mail. If
users are not receiving notices about undeliverable messages then you do not need to take
Winsock Error Codes
All MailSite Network I/O errors report a number that is a standard Winsock error code.
Following is a comprehensive list of Winsock error codes in numerical order with a
technical description for each:
10004 - WSAEINTR - Interrupted function call.
A blocking operation was interrupted by a call to WSACancelBlockingCall.
10013 - WSAEACCES - 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
10014 - WSAEFAULT - 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
struct sockaddr is smaller than sizeof(struct sockaddr).
10022 - WSAEINVAL - Invalid argument.
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
- for instance, calling accept on a socket
that is not listening.
10024 - WSAEMFILE - 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.
10035 - WSAEWOULDBLOCK - Resource temporarily unavailable.
This error is returned from operations on non-blocking sockets that cannot be completed
immediately, for example recv when no data is queued to be read from the socket. It is a
non-fatal error, and the operation should be retried later. It is normal for
WSAEWOULDBLOCK to be reported as the result from calling connect on a non-blocking
SOCK_STREAM socket, since some time must elapse for the connection to be established.
10036 - WSAEINPROGRESS - Operation now in progress.
A blocking operation is currently executing. Windows Sockets only allows a single
blocking operation to be outstanding per task (or thread), 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.
10037 - WSAEALREADY - Operation already in progress.
An operation was attempted on a non-blocking socket that already had an operation in
progress - i.e. calling connect a second time on a non-blocking socket that is already
connecting, or canceling an asynchronous request (WSAAsyncGetXbyY) that has already been
canceled or completed.
10038 - WSAENOTSOCK - Socket operation on non-socket.
An operation was attempted on something that is not a socket. Either the socket handle
parameter did not reference a valid socket, or for select, a member of an fd_set was not
10039 - WSAEDESTADDRREQ - Destination address required.
A required address was omitted from an operation on a socket. For example, this error
will be returned if sendto is called with the remote address of ADDR_ANY.
10040 - WSAEMSGSIZE - 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 into was smaller than the
10041 - WSAEPROTOTYPE 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.
10042 - WSAENOPROTOOPT - Bad protocol option.
An unknown, invalid or unsupported option or level was specified in a getsockopt or
10043 - WSAEPROTONOSUPPORT - 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
10044 - WSAESOCKTNOSUPPORT 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.
10045 - WSAEOPNOTSUPP - 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, for
example, trying to accept a connection on a datagram socket.
10046 - WSAEPFNOSUPPORT - Protocol family not supported.
The protocol family has not been configured into the system or no implementation for it
exists. Has a slightly different meaning to WSAEAFNOSUPPORT, but is interchangeable in
most cases, and all Windows Sockets functions that return one of these specify
10047 - WSAEAFNOSUPPORT - 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" (i.e. AF_INET for Internet Protocols) and a
generic protocol type (i.e. SOCK_STREAM). This error will be 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, e.g. in sendto.
10048 - WSAEADDRINUSE - Address already in use.
Only one usage of each socket address (protocol/IP address/port) is normally permitted.
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 wasn't 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 will choose an unused port
10049 - WSAEADDRNOTAVAIL - Cannot assign requested address.
The requested address is not valid in its context. Normally results from an attempt to
bind to an address that is not valid for the local machine, or connect/sendto an address
or port that is not valid for a remote machine (e.g. port 0).
10050 - WSAENETDOWN - Network is down.
A socket operation encountered a dead network. This could indicate a serious failure of
the network system (i.e. the protocol stack that the WinSock DLL runs over), the network
interface, or the local network itself.
10051 - WSAENETUNREACH - 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.
10052 - WSAENETRESET - Network dropped connection on reset.
The host you were connected to crashed and rebooted. May also be returned by setsockopt
if an attempt is made to set SO_KEEPALIVE on a connection that has already failed.
10053 - WSAECONNABORTED - Software caused connection abort.
An established connection was aborted by the software in your host machine, possibly
due to a data transmission timeout or protocol error.
10054 - WSAECONNRESET - Connection reset by peer.
A 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, or the
remote host used a "hard close" (see setsockopt for more information on the
SO_LINGER option on the remote socket.)
10055 - WSAENOBUFS - 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.
10056 - WSAEISCONN - 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.
10057 - WSAENOTCONN - 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.
10058 - WSAESHUTDOWN - 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 has
10060 - WSAETIMEDOUT - Connection timed out.
A connection attempt failed because the connected party did not properly respond after
a period of time, or established connection failed because connected host has failed to
10061 - WSAECONNREFUSED - Connection refused.
No connection could be made because the target machine actively refused it. This
usually results from trying to connect to a service that is inactive on the foreign host -
i.e. one with no server application running.
10064 - WSAEHOSTDOWN - Host is down.
A socket operation failed because the destination host was 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.
10065 - WSAEHOSTUNREACH - No route to host.
A socket operation was attempted to an unreachable host. See WSAENETUNREACH
10067 - WSAEPROCLIM - 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.
10091 - WSASYSNOTREADY - 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, be sure the first one in the path is appropriate for the
network subsystem currently loaded. Refer to the Windows Sockets implementation
documentation to be sure all necessary components are currently installed and configured
10092 - WSAVERNOTSUPPORTED - 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.
10093 - WSANOTINITIALISED - Successful WSAStartup not yet
Either the application hasn't called WSAStartup or WSAStartup failed.
The application may be accessing a socket which the current active task does not own (i.e.
trying to share a socket between tasks), or WSACleanup has been called too many times.
10094 - WSAEDISCON - Graceful shutdown in progress.
Returned by recv, WSARecv to indicate the remote party has initiated a
graceful shutdown sequence.
11001 - WSAHOST_NOT_FOUND - Host not found.
No such host is known. The name is not an official hostname 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 the specified name could not be found in the
11002 - WSATRY_AGAIN - Non-authoritative host not found.
This is usually a temporary error during hostname 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.
11003 - WSANO_RECOVERY - This is a non-recoverable error.
This indicates some sort of non-recoverable error occurred during a
database lookup. This may be because the database files (e.g. BSD-compatible HOSTS,
SERVICES or PROTOCOLS files) could not be found, or a DNS request was returned by the
server with a severe error.
11004 - WSANO_DATA - Valid name, no data record of requested
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
hostname - address translation attempt (using gethostbyname or WSAAsyncGetHostByName)
which uses the DNS (Domain Name Server), and an MX record is returned but no A record -
indicating the host itself exists, but is not directly reachable.
See these other knowledge base documents:
Last revised 2006-9-29