
ID# Loftware Notification Agent Message
414
There are no configured recipients, please configure Loftware Notification Agent before
starting!
415
This version of the Loftware Notification Agent has not been successfully installed! Please
rerun setup.
418 Failed to initialize socket libraries!
424
Loftware has detected that Hotmail is the default mail client.User interaction is required with
Hotmail which will cause the Notification Agent to lock up. Email Notifications have been
disabled for this session.
Avoid using Hotmail as a mail client with the LNA.
425
Loftware has detected that Eudora is the default mail client. Eudora cannot be reliably run from
the Loftware Notification Agent Service. Email Notifications have been disabled for this
session.
Avoid using Eudora as a mail client with the LNA.
Other common messages shown in the LPS Status Client or written to log files include:
LPS Status Client or Log
File Messages
Explanation
Label not designed for selected
device <devicenumber>
Labels designed for one printer may not work for a printer from a
different family or is a different model number within the same
printer family. See Knowledge Base Article 2009021.
Error opening port
There are many possible causes for this error, but the most common
cause is that a driver is already using the same port that Loftware is
trying to use.
Failed to open specified Label
Format <format>
Reasons could be that the label format does not exist in the
specified path, that one of the files needed for the LPS to print a
label is missing, that the LPS user does not have access to the
directory specified under Options | File Locations. See Knowledge
Base Articles 2009229 and 2009230.
Selected Device Not Configured
This may occur when LPS tries to send a job to a printer that has
not been set up in the LLM Device Configuration.It may also recur if
the LPS does not have permission to use.See Knowledge Base
Article 2009053.
Device Down <device>
No servers were found on the
network
This usually occurs when attempting to run the On-Demand Print
Client without having first starting the Loftware Print Server.See
Knowledge Base Article 2009244.
Printer is busy
If you are receiving this error when your printer is clearly not busy,
it is most likely due to a connection problem.
Loftware LabelManager Version 10.1.1 User's Guide
531
Comentários a estes Manuais