Troubleshoot Devices
For information about managing device connections, see Managing Devices. For information about managing access to device connections, see Controlling Access in Loftware Enterprise SP.
Important! Whenever you add a new device, data service, integration, or facility, you must ensure that the service is activated on all Loftware Application Servers on which it should be available to run and started on at least one. In an environment with only one Loftware Application Server, these types of services are automatically activated and started when they are created. For more information,
Important! In an environment with distributed services, to permit a user to perform administrative tasks related to services you must assign Read and Write permissions for Servers. These permissions must be assigned for each server in Access Control
Symptom | Resolution |
---|---|
Problems are encountered when configuring a remote spooler (LPR) connection by using a TCP/IP device connection with LPR protocol. |
|
Problems are encountered when configuring a TCP/IP device connection with Standard protocol. |
|
Problems are encountered when configuring or using Loftware Remote Print. |
|
Problems are encountered when a configured USB device connected to a Linux operating system is moved to a different USB port. |
Go to Devices |
A thermal printer is exhibiting unexpected behavior. |
For thermal printers, always set the resolution to what is reported by the device. |
A QuickLabel device's status changes to Errored when a print job is sent to it. |
If a QuickLabel device is in sleep mode when Loftware Enterprise SP sends a print job to it, the device's status may change to Errored. To resolve this issue, restart the QuickLabel device. |
A QuickLabel device is exhibiting unexpected behavior. |
For QuickLabel devices, always set the label template size to match the stock size. |
A QuickLabel device is producing low print quality symbols even when set to Best print quality. |
QuickLabel devices generate all symbols at print time. Low print quality and verification grades may occur in small symbols due to the high resolution of the printers (600 dpi and 1200 dpi). To avoid low print quality, increase the Line X-Dim value of the symbol. |
Print jobs are not printing from a NeuraLabel device, even though the status in Loftware Enterprise SP is Completed. |
If the configuration of a NeuraLabel device in Loftware Enterprise SP does not match the media in the device, an error may occur at the device resulting in failed print jobs. Because the error occurs at the device, Loftware Enterprise SP reports the status as Completed. To resolve, check that your configuration matches the media in the device. For more information, see NeuraLabel Device Driver. |
When printing to an Epson device, a native field prints behind an imaged field when it should print on top of the imaged field. |
If you are printing to an Epson device and your label template contains a combination of native and imaged fields, you can enforce the stacking order of native and imaged fields when printing to match the order displayed in Label Design |
Font recall is not performing as expected. |
For Zebra devices, x.14 or later firmware is required to support font commands. For font recall If the font installed in Loftware Enterprise SP and the font loaded into device memory are not the same, you may have unexpected results. If a field includes any of the following characteristics, then the font alone cannot be used to format the text and Loftware Enterprise SP must generate an image of the formatted text for that field. When this approach is necessary, font recall cannot be applied for the field.
For more information about font recall, see Fonts for Zebra Devices. |
Label Specific Options are not having the intended effect. |