Product

Symptoms

• Lotem Xpose does not launch
• Production Manager does not launch

Cause

Production Manager data base may be corrupt.

Solution

In Xpose version 1.0:

1. Exit Lotem Xpose, and then exit Lotem Controller.
2. Reset TSP.
3. Log off of Windows NT press alt+ctrl+delete, and then click Log Off... to abort any processes that are stuck. In most cases there is no need to reboot.
4. Start Lotem Controller, and then start Lotem Xpose.

If the problem persists, the Xpose Production Manager database may be damaged. Check if the database is damaged, as follows.

1. Select Start>Run>cmd.
2. In the command line, type testSQL and press Enter. 

If the values in the status printouts on screen do not equal 0, replace the database with an empty database, as follows.

1. Exit the Lotem Xpose application, and log off of Windows NT.
2. Copy the empty database below to C:\LotemExpose\version\DBQ TEQueue.mdb
3. Reboot the system.

In Xpose version 1.1.47 with update 5 or 6.1:

1. In Lotem Xpose, click the Preferences icon.
   
2. In the Preferences dialog box, in the Plate Expose tab, in the How many jobs will be left area, decrease the following parameter values as follows:
   • Completed queue—50
   • Failed queue—30
   
3. Restart Xpose.

Notes:

• The first time that the application starts, it takes a long time. Any following restarts are much faster.
• The bug related to the slowness of the application after a few weeks of work is solved in Xpo version 3.0.68.

Technical contact(s)

Mario Amir

Submitted by

Mario Amir

Date submitted

22 Oct 2001