Documentation logo

Lab 50 Troubleshooting and FAQs

If you should encounter an error while using Lab 50, there are many resources available for troubleshooting the problem via internal logging tools.

Reporting Issues to Support

If you should encounter an error while using Lab 50, there are many resources available for troubleshooting the problem via internal logging tools. Information you should include when contacting support via phone or email includes the following:

  • The full software version as shown on the Home tab of Lab 50
  • Any error messages that appear on both the General and Details tabs
  • The event in progress at time of the error. ie. Were you trying to print an order? Mark it complete? Burn a DVD? etc.
  • Any log files found in C:\Program Files\Lucidiom Lab 50 7.0 or the path of your Lab 50 installation
  • Any information that may be relevant to the error. ie. You are getting an error while printing, but the same order printed fine yesterday. One order will not print, but the others all print fine. etc.

Providing this information upfront will help to speed up the progress of determining the problem in the software.

How to Access Log Information

Locate and read Lab 50's log files when diagnosing an issue.

Corrupted State.xml Issue

Identify and resolve a corrupted state.xml file.

Lab 50 Invoice Customizations and Macros

Customize invoice templates and macros in Lab 50.

Reimporting Lab 50 Orders from the Local Backup

Restore orders from the local backup when needed.

Resetting the Local Database

Steps to reset Lab 50's local database.

Color Space: sRGB vs. Adobe RGB

Understand color space differences and their effect on prints.