NOTE: This documentation relates to an earlier version of the APM / Lab 50 software.

Visit the current documentation home.

Q: I'm getting an error that my import folder cannot be accessed\cannot be found at this time. What causes this error?
A: If you normally turn your kiosks off each night and leave the Lab 50 machine turned on, or if you turn all of the machines off but turn the Lab 50 machine on first, the software will not be able to find the other machines until they have been turned on and established a network connection. In these instances, the error may be ignored.

If all machines have been turned on and one machine is returning this error, you'll need to check the network cables to confirm everything is plugged in properly. Additionally, you may want to try restarting your router or switch. If these do not resolve the problem, try swapping the network cable between a machine that is connecting correctly and the machine that is not. If the machine previously not connected will now connect, you need to replace the network cable.

Q: My orders are failing to print. What might be causing this issue?
A: If an order is failing to print and you have recently added new products to your kiosk offerings, you may need to do some additional configuration in the Setup Wizard of Lab 50 in order for the product to print. Please reference the appropriate Printer Interface Guide for your setup and follow the steps to confirm your new products are completely configured.

If you have not added new products or have confirmed that everything is already configured, double-check your network or USB connection(s) as applicable for your printer type.

Q: My orders are grayed out, and I cannot print any of them. Additionally, no new orders are showing up. What do I do?
A: If all previous orders appear gray, and no new orders will appear on the orders screen though they are on the Lab 50 machine, you may have a corrupted state.xml file in your Lab 50 installation. Contact support for further assistance.

Q: My user credentials are not being saved even though the option to save them was selected. How do I fix this?
A: If your credentials are not being saved, they may have been entered incorrectly when the box was checked, and the software will therefore clear the fields. If the information previously did save and now will not save, you may have a corrupted state.xml file in your Lab 50 installation. Contact support for further assistance.

Q: I'm getting a table 5 index error in Lab 50. What does this error mean?
A: This error indicates a temporary problem updating the local database file on the machine where Lab 50 is installed. This is a non-critical error, and it may be cleared by closing and re-opening Lab 50.

Q: I'm receiving a communication error in Lab 50 when I try to burn CDs/DVDs. What does this error mean?
A: This error usually indicates there is a problem with Back Lab Burner accessing your CD/DVD drive to burn the order. You'll want to review the configuration settings in Back Lab Burner via Settings > Options as well as in Lab 50 via Settings > Fulfillment > Back Lab Burner.

Q: I'm receiving a MSG Need Activation Error when trying to burn cd/dvds. What does this message mean?
A: This message usually indicates a problem with your Back Lab Burner licensing. Open Back Lab Burner via c:\BackLabBurner\BackLabBurner.exe and note the APM ID, error code 1 and 2, and the history ID given in the error message, then contact support and provide this information.

Q: I'm receiving a Concurrency Error similar to the following:

  1. Concurrency violation: the UpdateCommand affected 0 of the expected 1
    records. [ System.Data.DBConcurrencyException ]
  2. Adapter at index 0 failed during an update. Concurrency violation: the
    UpdateCommand affected 0 of the expected 1 records.
    [ System.Data.DataException ]
  3. Table 'Order' has errors.
    Concurrency violation: the UpdateCommand affected 0 of the expected 1
    records.

What does this mean, and how do I fix it?
A: This error indicates a temporary problem updating the local database file on the machine where Lab 50 is installed. This is a non-critical error, and it may be cleared by closing and re-opening Lab 50.

  • No labels