beautypg.com

Sierra 5391-02 User Manual

Page 53

background image

T12017-Sentry_LANServer_Users_Manual

Page 53 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

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
version number other than 2.0.

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 Windows
Sockets function which directly
maps to a Win32 function. The
Win32 function is indicating a lack
of required memory resources.

WSANOTINITIALISED

10093

Successful
WSAStartup
not

yet

performed

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.

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

This manual is related to the following products: