Sierra 5391-02 - Manual (Page 51)

T12017-Sentry_LANServer_Users_Manual Page 51 of 59
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: (408) 262-2299 Fax: (408) 262-2269 Toll_Free: 888-509-1970 email: [email protected]
Macro Code Message Description
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 has been
discontinued.
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.
WSAETIMEDOUT 10060
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 respond.
WSATYPE_NOT_FOUND 10109
Class type not
found
The specified class was not found.
WSAEWOULDBLOCK 10035
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.
WSAHOST_NOT_FOUND 11001 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 relevant
database.
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.