Sierra 5391-02 Wsainvalidparameter, Wsainvalidproctable, Wsainvalidprovider, Wsaioincomplete

Page 52

T12017-Sentry_LANServer_Users_Manual

 

 

 

 

 

 

 

 

Page 52 of 59

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Macro

Code

Message

 

 

Description

 

 

 

 

 

 

 

 

 

 

 

 

 

 

An application used a Windows

 

 

 

 

One

or

more

Sockets

function

 

which

directly

 

 

WSA_INVALID_PARAMETER

OS

maps to a Win32 function. The

 

 

dependent

parameters

are

Win32

function

 

is

indicating

a

 

 

 

 

invalid

 

 

 

problem with one or more

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

parameters.

 

 

 

 

 

 

 

 

 

 

Invalid

 

 

 

A service provider returned a

 

 

WSAINVALIDPROCTABLE

OS

procedure table

bogus proc table to WS2_32.DLL.

 

 

dependent

from

service

(Usually caused by one or more of

 

 

 

 

 

 

 

provider

 

 

the function pointers being NULL.)

 

 

 

OS

Invalid

service

A service provider returned a

 

 

WSAINVALIDPROVIDER

provider version

 

 

 

dependent

number

 

 

version number other than 2.0.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The application has tried to

 

 

 

 

 

 

 

 

determine the status of an

 

 

 

 

 

 

 

 

overlapped operation which is not

 

 

 

 

Overlapped

I/O

yet

completed.

Applications

that

 

 

WSA_IO_INCOMPLETE

OS

event object not

use

WSAGetOverlappedResult

 

 

dependent

in

signaled

(with the fWait flag set to false) in a

 

 

 

 

 

 

 

state

 

 

 

polling mode to determine when an

 

 

 

 

 

 

 

 

overlapped

operation

 

has

 

 

 

 

 

 

 

 

completed will get this error code

 

 

 

 

 

 

 

 

until the operation is complete.

 

 

 

 

 

 

 

 

 

 

The application has initiated an

 

 

 

 

Overlapped

 

overlapped operation which cannot

 

 

 

OS

 

be

completed

 

immediately.

 

A

 

 

WSA_IO_PENDING

operations

 

will

 

 

 

 

dependent

 

completion indication will be given

 

 

 

 

complete later

at a later time when the operation

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

has been completed.

 

 

 

 

 

 

 

 

 

 

 

An application used a Windows

 

 

 

OS

Insufficient

 

Sockets

function

 

which

directly

 

 

WSA_NOT_ENOUGH_MEMORY

memory

 

 

maps to a Win32 function. The

 

 

dependent

 

 

 

 

 

 

available

 

 

Win32 function is indicating a lack

 

 

 

 

 

 

 

 

of required memory resources.

 

 

 

 

 

 

 

 

 

 

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

 

 

WSAHOST_NOT_FOUND

11001

Host not found

error may also be returned for

 

 

 

 

 

 

 

 

protocol and service queries, and

 

 

 

 

 

 

 

 

means the specified name could

 

 

 

 

 

 

 

 

not be found in the relevant

 

 

 

 

 

 

 

 

database.

 

 

 

 

 

 

 

 

 

OS

Specified

event

An application attempts to use an

 

 

WSA_INVALID_HANDLE

object handle is

event object, but the specified

 

 

dependent

 

 

 

 

invalid

 

 

 

handle is not valid.

 

 

 

 

 

 

 

 

 

 

 

 

An application used a Windows

 

 

 

OS

One

or

more

Sockets

function

 

which

directly

 

 

WSA_INVALID_PARAMETER

parameters

are

maps to a Win32 function. The

 

 

 

dependent

invalid

 

 

 

Win32

function

 

is

indicating

a

 

 

 

 

 

 

 

problem with one or more

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

parameters.

 

 

 

 

 

 

 

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: support@fieldserver.com

Image 52
Contents Sentry LANServer Applicability & EffectivityTable of Contents LED1 Product Description General FeaturesOperation Sentry Firmware Version ConnectionsModel 5391-01 LANServer with 2-4 Sentry Controllers Page Quick Start LANServer Terminology Quick StartSetting Browser Security Settings for ActiveX controls Browser Security SettingsActiveX Controls and Security T12017-SentryLANServerUsersManual Customize the settings Setting the Browser Privacy Settings for Cookies Cookies and Browser SecuritySpecify the WebServer IP address and then click Allow T12017-SentryLANServerUsersManual Interpreting Zone Buttons T12017-SentryLANServerUsersManual Interpreting Sentry-Sensor Controls Interpreting Sentry -Combo Controls Interpreting Sentry Alarms Understanding the Alarm Table Colors Acknowledging AlarmsClick Retry to clear the dialog Interpreting Sentry Events Event Report TypesPage Understanding the Events What happens if Event Logging is disabled?Events Page and the Date / Time Potential Problems with Event Logging File Problems Space ProblemsEvent File Maintenance Limited number of event recordsManaging Sentry Events Uploading Potential Problems with an Upload How Event Time Stamps are reported Manual uploadInterpreting the Sentry Face Plate LED Current sensor number Gas Concentration for current sensor Sensor One User at a Time ActiveX Not InstalledLANServer Driver Ver .05f Required Description How the Control OperatesBackup File Contents Problems with Calibration Backup ControlInterpreting Analog, Text and LED controls Analog Controls Text ControlsLED Controls Using the LANServer to allow customers to upload files Appendix 1.3. Page login.htm not found Appendix 1.2. Objects report ‘Not Found’Appendix 1.6. Buttons Display in White Appendix 1.7. Cookie LengthAppendix 1.9. LANServer Configuration LED 40159,8 40977,8 40985,8Appendix 2. LANServer Error Messages FYIWEB#13 Err Not enough Space for alarm WEB#15 FYI ASO Max Limited to %d Web#68 FYI. Http Appendix 3. WinSock Error Messages Wsaeconnreset WsaenetresetWsaeafnosupport WsaealreadyWsaefault WsaedestaddrreqWsaehostdown Wsaehostunreach Wsaeisconn Wsaemfile Wsaemsgsize WsaenetdownWsaenotconn WsaenotsockWsaeopnotsupp WsaepfnosupportWsaeshutdown WsaesocktnosupportSockraw WsaetimedoutWsainvalidparameter WsainvalidproctableWsainvalidprovider WsaioincompleteWsanotinitialised WsanodataWsanorecovery HostsWsaproviderfailedinit WsasyscallfailureWINSOCK.DLL WsavernotsupportedWsaediscon WsaoperationabortedAppendix 4.2. LED1 Appendix 4. FieldServer ActiveX Controls Appendix 4.1. Ana1Appendix 4.3. Char1 Appendix 4.4. Limitations and Supported Environments Appendix 5. General Appendix 5.1 .1 Browser Caching This page Intentionally Left Blank