Sierra 5391-01 Wsaeisconn, Wsaemfile, Wsaemsgsize, Wsaenetdown, Wsaenobufs, Wsaenoprotoopt

Page 49

T12017-Sentry_LANServer_Users_Manual

 

 

 

 

 

 

Page 49 of 59

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Macro

Code

Message

 

Description

 

 

 

 

 

 

 

 

 

 

 

A connect request was made on an

 

 

 

 

 

 

already

connected

socket. Some

 

 

 

 

 

 

implementations

also return

this

 

 

 

 

Socket

is

error if sendto is called on a

 

 

WSAEISCONN

10056

already

 

connected SOCK_DGRAM socket

 

 

 

 

connected

 

(For SOCK_STREAM sockets, the

 

 

 

 

 

 

to parameter in sendto is ignored),

 

 

 

 

 

 

although

other

implementations

 

 

 

 

 

 

treat this as a legal occurrence.

 

 

 

 

 

 

 

Too many open sockets. Each

 

 

 

 

Too many open

implementation

 

may

have

a

 

 

WSAEMFILE

10024

maximum

number

of

socket

 

 

 

 

files

 

handles available, either

globally,

 

 

 

 

 

 

 

 

 

 

 

 

per process or per thread.

 

 

 

 

 

 

 

 

A message sent on a datagram

 

 

 

 

 

 

socket was larger than the internal

 

 

WSAEMSGSIZE

10040

Message

too

message

buffer

or

some other

 

 

long

 

network limit, or the buffer used to

 

 

 

 

 

 

 

 

 

 

 

receive a datagram into was

 

 

 

 

 

 

smaller than the datagram itself.

 

 

 

 

 

 

A socket operation encountered a

 

 

 

 

 

 

dead network. This could indicate a

 

 

WSAENETDOWN

10050

Network

is

serious failure of the network

 

 

down

 

system (i.e. the protocol stack that

 

 

 

 

 

the WinSock DLL runs over), the

 

 

 

 

 

 

 

 

 

 

 

 

network interface, or the local

 

 

 

 

 

 

network itself.

 

 

 

 

 

 

 

 

 

 

 

The connection has been broken

 

 

 

 

 

 

due to "keep-alive"

activity

 

 

 

 

Network

 

detecting a failure while the

 

 

WSAENETRESET

10052

dropped

 

operation

was

in

progress. It

can

 

 

connection

on

also be returned by setsockopt if

 

 

 

 

 

 

 

 

reset

 

an attempt

is

made

to

set

 

 

 

 

 

 

SO_KEEPALIVE on a connection

 

 

 

 

 

 

that has already failed.

 

 

 

 

 

 

 

 

A socket operation was attempted

 

 

WSAENETUNREACH

10051

Network

is

to an unreachable network. This

 

 

unreachable

 

usually

means

the

local

software

 

 

 

 

 

knows no route to reach the remote

 

 

 

 

 

 

 

 

 

 

 

 

host.

 

 

 

 

 

 

 

 

 

 

 

 

 

An operation on a socket could not

 

 

WSAENOBUFS

10055

No buffer space

be performed because the system

 

 

available

 

lacked sufficient buffer space or

 

 

 

 

 

 

 

 

 

 

 

because a queue was full.

 

 

 

 

 

 

 

 

An

unknown,

 

invalid

or

 

 

WSAENOPROTOOPT

10042

Bad protocol

unsupported option

or level

was

 

 

option

 

specified in a getsockopt or

 

 

 

 

 

 

 

 

 

 

 

setsockopt call.

 

 

 

 

 

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 49
Contents Applicability & Effectivity Sentry LANServerTable of Contents LED1 Product Description General FeaturesOperation Connections Sentry Firmware VersionModel 5391-01 LANServer with 2-4 Sentry Controllers Page Quick Start Quick Start LANServer TerminologySetting Browser Security Settings for ActiveX controls Browser Security SettingsActiveX Controls and Security T12017-SentryLANServerUsersManual Customize the settings Cookies and Browser Security Setting the Browser Privacy Settings for CookiesSpecify 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 Acknowledging Alarms Understanding the Alarm Table ColorsClick Retry to clear the dialog Event Report Types Interpreting Sentry EventsPage Understanding the Events What happens if Event Logging is disabled?Events Page and the Date / Time Space Problems Potential Problems with Event Logging File ProblemsEvent File Maintenance Limited number of event recordsManaging Sentry Events Uploading How Event Time Stamps are reported Manual upload Potential Problems with an 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 How the Control Operates DescriptionProblems with Calibration Backup Control Backup File ContentsInterpreting Analog, Text and LED controls Text Controls Analog ControlsLED Controls Using the LANServer to allow customers to upload files Appendix 1.2. Objects report ‘Not Found’ Appendix 1.3. Page login.htm not foundAppendix 1.7. Cookie Length Appendix 1.6. Buttons Display in White40159,8 40977,8 40985,8 Appendix 1.9. LANServer Configuration LEDFYI Appendix 2. LANServer Error MessagesWEB#13 Err Not enough Space for alarm WEB#15 FYI ASO Max Limited to %d Web#68 FYI. Http Appendix 3. WinSock Error Messages Wsaenetreset WsaeconnresetWsaeafnosupport WsaealreadyWsaedestaddrreq WsaefaultWsaehostdown WsaehostunreachWsaemfile WsaeisconnWsaemsgsize WsaenetdownWsaenotsock WsaenotconnWsaeopnotsupp WsaepfnosupportWsaesocktnosupport WsaeshutdownSockraw WsaetimedoutWsainvalidproctable WsainvalidparameterWsainvalidprovider WsaioincompleteWsanodata WsanotinitialisedHosts WsanorecoveryWsaproviderfailedinit WsasyscallfailureWsavernotsupported WINSOCK.DLLWsaediscon 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