Sierra 5391-02, 5391-01 user manual Appendix 3. WinSock Error Messages

Page 46

T12017-Sentry_LANServer_Users_Manual

Page 46 of 59

Appendix 3. WinSock Error Messages

The following is a list of possible error codes returned by the WSAGetLastError call, along with their extended explanations. Errors are listed in alphabetical order of error macro. Error codes defined in WINSOCK2.H not returned from any function have not been listed here.

Macro

Code

Message

Description

 

 

 

 

 

 

 

An attempt was made to access a

 

 

 

socket in a way forbidden by its

 

 

Permission

access permissions. An example is

WSAEACCES

10013

using

a

broadcast

address for

denied.

 

 

sendto

 

without

broadcast

 

 

 

 

 

 

 

permission

being

set

using

 

 

 

setsockopt (SO_BROADCAST).

 

 

 

Only one usage of each socket

 

 

 

address

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

 

 

 

For server applications that need to

 

 

 

bind multiple sockets to the same

 

 

Address

port

number,

consider

using

WSAEADDRINUSE

10048

setsockopt

(SO_REUSEADDR).

already in use

 

 

Client applications usually need not

 

 

 

 

 

 

call bind at all - connect will

 

 

 

choose

an

unused

port

 

 

 

automatically. When bind is called

 

 

 

with a wild-card address (involving

 

 

 

ADDR_ANY),

 

 

a

 

 

 

WSAEADDRINUSE error could be

 

 

 

delayed until the specific address is

 

 

 

"committed."

This could

happen

 

 

 

with a call to other functions later,

 

 

 

including

 

connect,

listen,

 

 

 

WSAConnect or WSAJoinLeaf.

 

 

 

The requested address is not valid

 

 

 

in its context. Normally results from

 

 

 

an attempt to bind to an address

 

 

Cannot assign

that is not valid for the local

WSAEADDRNOTAVAIL

10049

machine. This can also result from

requested

connect, sendto, WSAConnect,

 

 

address

 

 

WSAJoinLeaf,

or

WSASendTo

 

 

 

 

 

 

when the remote address or port is

 

 

 

not valid for a remote machine (e.g.

 

 

 

address or port 0).

 

 

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

Page 45 Page 47
Image 46
Page 45 Page 47
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 Event File Maintenance Potential Problems with Event Logging File ProblemsSpace Problems 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 Wsaeafnosupport WsaeconnresetWsaenetreset WsaealreadyWsaehostdown WsaefaultWsaedestaddrreq WsaehostunreachWsaemsgsize WsaeisconnWsaemfile WsaenetdownWsaeopnotsupp WsaenotconnWsaenotsock WsaepfnosupportSockraw WsaeshutdownWsaesocktnosupport WsaetimedoutWsainvalidprovider WsainvalidparameterWsainvalidproctable WsaioincompleteWsanotinitialised WsanodataWsaproviderfailedinit WsanorecoveryHosts WsasyscallfailureWsaediscon WINSOCK.DLLWsavernotsupported 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
Top Page Image Contents