Sierra 5391-02 Appendix 1.2. Objects report ‘Not Found’, Appendix 1.3. Page login.htm not found

Page 38

T12017-Sentry_LANServer_Users_Manual

Page 38 of 59

Appendix 1. Troubleshooting

Appendix 1.1. Objects Report ‘Offline’

Click Refresh or change to another page and return to the screen and see if the problem persists. If it does then check the state of the LANServer by checking the error screen and the overview screen using Ruinet. Check the network connection.

Appendix 1.2. Objects report ‘Not Found’

If this problem persists after a refresh then report to Technical Support as it may indicate that the version LANServer software and the version of the software used to prepare the project for downloading are not compatible.

Appendix 1.3. Page login.htm not found

If access control is enabled and a user has not been logged in then the LANServer will change the web page to a page called ‘login.htm’. In the event that access control is activated without the system-builder having built a page called ‘login.htm’ then the browser will display a HTTP 404 error.

Appendix 1.4. User ids and passwords are not available for validation. Try again.

The access control system uses cookies to transfer data between the browser and the LANServer. If one of the cookies hasn’t been delivered to the browser yet, this message is displayed. Use the Back button on the browser to go back to one of the project screens and try again.

Appendix 1.5. Alarm Page doesn’t auto refresh when there is a new alarm.

This problem can be corrected by adjusting the browser settings. The browser’s cache system is telling the browser used use the cached copy of a page instead of reading a refreshed copy from the LANServer.

In the browser ‘Tools’ menu, select the ‘Internet Options’

Adjust cache settings here.

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 38
Contents Sentry LANServer Applicability & EffectivityTable of Contents LED1 Operation FeaturesProduct Description General Sentry Firmware Version ConnectionsModel 5391-01 LANServer with 2-4 Sentry Controllers Page Quick Start LANServer Terminology Quick StartActiveX Controls and Security Browser Security SettingsSetting Browser Security Settings for ActiveX controls 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 Events Page and the Date / Time What happens if Event Logging is disabled?Understanding the Events 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 LANServer Driver Ver .05f Required ActiveX Not InstalledOne User at a Time 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.3. Char1 Appendix 4. FieldServer ActiveX Controls Appendix 4.1. Ana1Appendix 4.2. LED1 Appendix 4.4. Limitations and Supported Environments Appendix 5. General Appendix 5.1 .1 Browser Caching This page Intentionally Left Blank