As LOWIS is a complex software system there is the potential for the occasional error to occur. When this happens on the server, a LOWIS process may fail. The LOWIS host will usually try to restart and re-run the last command, a default of five times, before letting a process stop completely due to an error.
If a process has failed that is set to run automatically, the status indicator in LOWIS Admin will show in red and the Processes count will show a lower value than the total expected number of running processes.
The first thing you should try to do is restart the process. After failing, any previously queued commands are lost. If the process aborted due to a particular command, then you may be able to restart the process by simply right clicking on it and selecting restart.
Even if the process restarts successfully, you should report the issue for further investigation. If you look at the Messages section of LOWIS Admin there should be a log of any process errors that occurred. Please include a screen shot of any errors that are noted during the time frame when the process failed.
Finally, if you have turned on the Process Dump On Abort option in the LOWIS Admin configuration a memory dump should be generated whenever a process fails. They may often be too large to directly attach to a ticket submission, but if the support staff feel that it is needed please work with them to transfer over this file to help diagnose the issue that occurred. If you do have this option enabled, you may also occasionally wish to check the directory where the memory dumps are set to be generated and delete older memory dumps that are no longer needed.
If the entire LOWIS service has stopped, you should try restarting it from Windows Services. The main LOWIS service is the LOWIS Host Service (pictured below). If it fails to restart, and it is not running under the Local System, first make sure that the password for the user selected as the Log On As user has not changed since the service was configured.
If the service still will not restart, you can attempt to run it from a command prompt window to potentially get more information about why it is failing. Two of the more common reasons for the service failing to start are the SQL database used by LOWIS is not running, as pictured below, or third party security software preventing the application from launching. If you receive a pop-up security message asking for permission to launch the application, look for a box to check that says to not ask again when running this software. This should allow LOWIS to be run as a service. You may also wish to check the activity logs from any security software to verify there are no instances of it blocking the service from starting.
If the service starts, but no processes launch and users are unable to connect it may be due to the license having expired. Looking at the server status in LOWIS Admin should show this as an alarm on the main Servers screen. If this is the case, please contact support.