Thick Client Applications

Symptom HTTP 500 Internal Server Error when logging into browser-based applications Resolution An HTTP 500 error may be caused by an incorrect configuration of the ASP.net version.   ASP.net version should be set to 4.0 or higher, the e...

How to remove the machine name "FAILOVER" on a system that is no longer clustered Procedure Steps If a server was once part of an NEC Cluster, the LS Communication Server may still be referenced as FAILOVER. You can check this by launching...

 Symptom This error message indicates that the OnGuard license file does not have the Open Access "OnGuard WATCH" feature set to true . Resolution Request an updated OnGuard license file. ...

 Symptom There are two possible causes that can create this error message to appear when trying to access the OnGuard WATCH web page: The port number ( 8080 ) is missing in the URL The LS Web Service (nginx) is not...

 Symptom This issue occurs if the LS Web Service (nginx) is not running. Resolution Start or restart the LS Web Service.   In the Task Manager list of processes, two nginx processes (with the g...

 Symptom There are three possible causes that can create this error message when trying to access the OnGuard WATCH web page: The LS Web Proxy Service is not running The LS Open Access Service is not running The...

 Symptom There are two possible symptoms that may cause this error message to appear: Bad response after GetDirectoryList () call, or Login Driver is not running Resolution To resolve...

 Symptom There are two possible symptoms that may cause the "Server Error in '/watch' Application" error message to appear: Bad response after GetDirectoryList () call, or Login Driver is not running ...