lw Troubleshoot

</table>
Symptoms:
  • A specific label printer is not printing.
  • All else is good.
Resolution:
Option 1. Change timeout to 60 seconds.
  • Loftware Design32 program > Devices (F6) > Connection Settings.
  • Close Design32.
  • Check LPS Client to confirm labels have resumed printing.
  • Note: Default timeout is 8 seconds.
  • Note: If timeout is already 60 seconds, change it to 59 seconds.
Option 2. Temporarily change IP address to a dummy IP address.
  • Loftware Design32 program > Devices (F6) > Connection Settings.
  • Change label printer IP address in Loftware Design32.
  • Close Design32.
  • Wait 30 seconds.
  • Reopen Design32.
  • Change IP address back to correct IP address.
  • Close Design32.
  • Check LPS Client to confirm labels have resumed printing.
Option 3. Reload factory settings.
Context:
  • Loftware Print Server (LPS)
    • </td></tr>
Symptoms:
  • Label printer is not printing.
  • Print jobs end up in the "Critical Failure" queue.
  • Label printer IP address ping is successful.
  • Browse to label printer's web interface is successful.
  • Newly deployed printer.
Tried and didn't work:
  • Temporary change to dummy IP address and back.
Resolution:
  • Restart label printer via its web interface.
Context:
  • Label Printer
  • Loftware Print Server (LPS)
Symptoms:
  • Label printer IP address ping is successful.
  • Browse to label printer's web interface fails.
  • LPS Status Client shows these errors:
    • M1557 Connection refused.
    • M2231 Error opening port.
  • Device offline/error state/busy.
  • Telnet connection attempt returns "Could not open connection to the host on port 9100: Connect failed".
  • Note: Other printers on the same Loftware Print Server are working normally with no issues.
Tried and didn't work:
  • Restart printer.
  • Temporary change to dummy IP address and back.
Cause:
  • Printer's NIC card is bad.
Resolution:
  • Replace printer's NIC card.
Context:
  • Label Printer
  • Loftware Print Server (LPS)
Symptom:
  • Cannot connect printer to Wi-Fi using Wi-Fi Wizard.
Cause:
  • Wi-Fi Wizard is broken.
Resolution:
  • Enter Wi-Fi settings manually.
Context:
  • Label Printer
  • Wifi
Symptom:
  • Printing in the middle of two (2) labels.
Resolution:
  • Configure start and stop adjust to:
    • Start = -100 dots
    • Stop = 0 dots
Context:
  • Label Printer
Symptoms:
  • Users for multiple printers report labels are not printing.
  • Few, if any, print jobs are being processed by the affected Loftware Print Server.
  • TranPrint Print Queue table (FD3N920):
    • There are many more jobs than normal.
    • Most records are for one label printer number.
Cause:
  • DSI app or JD Edwards (JDE) NER or program is in infinite loop inserting records into the TranPrint Print Queue table.
Resolution:
  1. Stop DSI Printing Agent.
  2. Stop Loftware Print Server service on the affected Loftware server.
  3. Ask your JD Edwards CNC person to determine if a JD Edwards NER or program is causing this issue.
  4. If appropriate, kill the JD Edwards NER job.
  5. Delete jobs in the label printer queue via LPS Status Client.
  6. Rename the OLEBP folder(s) ...For example, by appending ".save".
  7. Create new OLEBP folder(s).
  8. Delete all files in the PRINTED folder in order to allow the Loftware Print Server service to start faster.
  9. Delete the TranPrint table records for the affected label printer number.
  10. Start Loftware Print Server service.
  11. Start DSI Printing Agent.
Context:
  • Loftware Print Server (LPS)
  • TranPrint Print Queue
Symptoms:
  • Labels are not printing correctly.
  • Labels print, but they are not printing correctly or they are not the correct label.
  • User complaints might be...
    • "Labels are not correct."
    • "Labels are not printing."
    • "Format is not correct."
Cause:
  • Probably caching.
  • The format in the printer's cache got corrupted.
Resolution:
  1. Loftware Design32 > Devices (F6) > Connection settings:
    • Change label printer's IP address to dummy IP address.
    • Change label printer's IP address back to the correct IP address.
  2. Loftware Design32:
    • Send test label format to the printer.
  3. Restart the label printer.
Context:
  • Loftware Print Server (LPS)
Symptoms:
  • Labels not printing.
  • No labels in print queue.
Cause:
  • User printed to the wrong printer (or default "dummy" printer).
Resolution:
  • Ask user to enter the correct label printer number.
Context:
  • Label Printer
  • Loftware Print Server (LPS)
Symptoms:
  • Labels not printing.
  • No labels in print queue.
Cause:
  • Possibly a corrupted file in the WDDROP folder (where print job files are written to).
Resolution:
Option 1. If issue is occurring for many label printers on the same Loftware server:
  • Stop Loftware Print Server service.
  • Rename WDDROP folder.
  • Start Loftware Print Server service.
Option 2. If just one label printer has the issue (and you don't want to interrupt the other label printers):
  • Add the label printer that is having the issue as a new printer on a different (or the same) Loftware server.
Context:
  • Loftware Print Server (LPS)
Symptoms:
  • IP address *can* be pinged.
  • Cannot browse to printer browser interface.
  • LPS Status Client shows these errors:
    • M2231 Error Opening Port
    • M1557 Connection refused
  • Device offline/error state/busy.
  • Telnet connection attempt returns "Could not open connection to the host, on port 9100: Connect failed".
  • Other printers on the same Loftware server are working normally with no issues.
Cause:
  • Printer's NIC card is bad.
Resolution:
  • Replace printer's NIC card.
Symptoms:
  • Label does not print correctly.
Cause:
  • Printer cache for label is corrupted.
Resolution:
  • Print test label from Loftware Design32 program.
Symptoms:
  • Some jobs in the "Jobs Processed" folder do not actually print.
Resolution:
  • Update printer firmware.
Symptoms:
  • Print job is stuck in Pending queue in Loftware Status Client.
  • Can still ping IP address successfully after printer is turned off.
Cause:
  • Duplicate IP address on network.
Resolution:
  • Change printer IP address.