UBQ000192: SMTP \ WSA error codes

UBQ ID Number: UBQ000192
Last Modified: 2000-06-06

Summary:

SMTP \ WSA error codes

Details:

WSA Errors

--------------------------------------------------------------------------------

WSAHOSTNOTFOUND

Error Number: 10001

The specified host cannot be found.

--------------------------------------------------------------------------------

WSAEINTR

Error Number: 10004

Interrupted function call. 

A blocking operation was interrupted by a call to 
WSACancelBlockingCall. 

--------------------------------------------------------------------------------

WSAEACCES

Error Number: 10013

Permission denied. 

An attempt was made to access a socket in a way forbidden by its access 
permissions. 

-------------------------------------------------------------------------------
WSAEFAULT

Error Number: 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. 

--------------------------------------------------------------------------------

WSAEINPROGRESS

Error Number: 10036

Operation now in progress. 

A blocking operation is currently executing. Windows Sockets only 
allows a single blocking operation.

--------------------------------------------------------------------------------

WSAEALREADY

Error Number: 10037

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 Error:WSAAsyncGetXbyY that 
has already been canceled or completed. 

 

--------------------------------------------------------------------------------

WSAEDESTADDRREQ

Error Number: 10039

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. 

--------------------------------------------------------------------------------

WSAEAFNOSUPPORT

Error Number: 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" 
Error: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. 

--------------------------------------------------------------------------------

WSAEADDRINUSE

Error Number: 10048

Address already in use. 

Only one usage of each socket address Error: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. Client applications usually need not call 
bind at all - connect will choose an unused port automatically.

--------------------------------------------------------------------------------
WSAEADDRNOTAVAIL

Error Number: 10049

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. 

--------------------------------------------------------------------------------
WSAECONNABORTED

Error Number: 10053

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. 

--------------------------------------------------------------------------------
WSAECONNRESET

Error Number: 10054

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" .

--------------------------------------------------------------------------------
WSAECONNREFUSED

Error Number: 10061

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. 

--------------------------------------------------------------------------------
WSAEHOSTDOWN

Error Number: 10064

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. 

--------------------------------------------------------------------------------
WSAEHOSTUNREACH

Error Number: 10065

No route to host. 

A socket operation was attempted to an unreachable host.

--------------------------------------------------------------------------------
WSAEINVAL

Error Number: 10022

Invalid argument. 

Some invalid argument was supplied Error: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. 

--------------------------------------------------------------------------------
WSAEISCONN

Error Number: 10056

Socket is already connected. 

A connect request was made on an already connected socket. 

--------------------------------------------------------------------------------
WSAEMFILE

Error Number: 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. 

--------------------------------------------------------------------------------
WSAENOTSOCK

Error Number: 10038

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 valid. 

--------------------------------------------------------------------------------

WSAEMSGSIZE

Error Number: 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 into was smaller than 
the datagram itself. 

--------------------------------------------------------------------------------
WSAENOPROTOOPT

Error Number: 10042

Bad protocol option. 

An unknown, invalid or unsupported option or level was specified in a 
getsockopt or setsockopt call. 

--------------------------------------------------------------------------------

WSAEPROTONOSUPPORT

Error Number: 10043

Protocol not supported. 

The requested protocol has not been configured into the system, 
or no implementation for it exists.

 

--------------------------------------------------------------------------------

WSAEOPNOTSUPP

Error Number: 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, for example, trying 
to accept a connection on a datagram socket. 

--------------------------------------------------------------------------------
WSAEPFNOSUPPORT

Error Number: 10046

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 WSAEAFNOSUPPORT. 

--------------------------------------------------------------------------------

WSAENETDOWN

Error Number: 10050

Network is down. 

A socket operation encountered a dead network. This could 
indicate a serious failure of the network system.

--------------------------------------------------------------------------------

WSAENETUNREACH

Error Number: 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

Error Number: 10052

Network dropped connection on reset. 

The host you were connected to crashed and rebooted.

--------------------------------------------------------------------------------
WSAENOBUFS

Error Number: 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. 

--------------------------------------------------------------------------------
WSAENOTCONN

Error Number: 10057

Socket is not connected. 

A request to send or receive data was disallowed because the socket 
is not connected. 

 

--------------------------------------------------------------------------------

WSATIMEOUT

Error Number: 10060

SMTP timeout error.

The connection may be timing out due to a slow link. Increase the retransmission 
timeout value of the following registry key to 10 or even 20.

See UBQ: UBQ000162 Non-UltraBac Specific Registry Key: TcpMaxDataRetransmissions

 

--------------------------------------------------------------------------------
WSAEPROCLIM

Error Number: 10067

Too many processes.

A Windows Sockets implementation may have a limit on the number 
of applications that may use it simultaneously.

--------------------------------------------------------------------------------

 

More Information:

See UBQ000162: Non-UltraBac Specific Registry Key: TcpMaxDataRetransmissions

Version: UltraBac v8.x
Copyright UltraBac Software 2005