Sierra 5391-02 - Manual (Page 50)

T12017-Sentry_LANServer_Users_Manual Page 50 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
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.
WSAENOTSOCK 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.
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, for example, 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. 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.
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.
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.
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.