LWA And LPS Interaction When Shutting Down

Description

There are several activities that occur within Loftware Web Access when the Loftware Print Server is shut down. This articles discusses possible errors that a user may see and why each error is being generated. All results were tested with Windows 2008R2 systems for the Loftware Printer Server, database, and  Loftware Web Access - there may be some differences across operating systems.

Solutions

The following test was conducted in order to determine what happens if the Loftware Print Server (LPS) is powered down or the Loftware Web Access (LWA) losses connection to the LPS:

Scenario 1:

LPS service stopped working. Customer is receving an error message:

 (MSG 5000)  An undefined application error has occurred, please contact your system administrator.  

The customer was logged in and printing before the error occur, and does not know the service stopped.

Customer actions included:

1)  Logging into LWA with a functional application (with LPS started), and successfully printing from LWA.
2)  Stopping the Loftware Print Server service.
3)  Navigating within the LWA application with the LPS service stopped.
     A connection failure error is reported, as expected:  
    
4) Restart the Loftware Print Server service.
5) Log out and back into the LWA to successfully print.
 Note: This does not require restarting the Apache Tomcat service.

Scenario 2:

LPS server was rebooted, or shut down because of an error. Customer is receving an error message:

(msg 5000)  An undefined application error has occurred, please contact your system administrator.  

The customer was logged in and printing before the error occur, and does not know the server was rebooted.

Customer actions included:

1) Logging into LWA with a functional application (with LPS started), and successfully print from LWA.
2) Rebooting the Loftware Print Server computer.
3) Navigating within the LWA application with the LPS service not in a running state.
    A connection failure error is reported, as expected.

   

4) Restart Loftware Print Server computer (and LPS service).
5) Log out and back into the LWA to successfully print.
 Note: This does require restarting the Apache Tomcat service..

Note: In both scenarios, the LWA server was not rebooted or restarted.

Scenario 3:

All client seats for LWA are being used, then the LPS service was rebooted. The user tries to print using LWA and receives the error:

(MSG 106) An specifiec error has occured. An unexpected error has occurred on the LPS: Loftwebaccess login 
request rejected. All LoftWebAcess licenses are in use. If this problem persists, contact your Loftware Administrator. 

This occurs due to the users not being logged out, and LPS believes that all client seats are actively being used.

Solutions:

1) Login in as Administrator and navigate to User Management and release the in-use user licenses.
2) Wait for the users that are in-use to time out (default time out is set to 10 minutes).
3) Restart Apache Tomcat service which will release all licenses.
4) Restart the LWA server.