The following sections describe the various messages that the LPS posts to the Application Event Log.  There are three categories of messages: Information, Warnings, and Errors.  Knowing what these messages mean could prove to be vital in troubleshooting potentially difficult problems.  Be advised that many of these messages are only visible if enabled in the ‘Logging’ section of the LPS Configuration Applet.

Event Log Informational Messages

Message 105: The service was started.
Date and time of service start.

Message 108: The service was stopped.
Date and time of service stop.

Message 109: Found and processed command file: <name>

Message 111: Passed pass file: <name> to Batch Print
If “Log Jobs” has been enabled in the Event Logging section under the Logging tab of the LPS Configuration Applet, the above entries are added after successfully locating and processing/passing the named files.  Be aware that enabling “Log Jobs” could unnecessarily ‘flood’ the system log with informational messages.  Once your system is up and running, you might consider turning this setting off.

Message 112: Batch Print has issued Job Number: <number>
The Loftware Batch Print sub-system assigns job numbers to each job (file) passed to it.  Enable the “Job Numbers” option in the Event Logging tab of the LPS configuration utility for this data.

Message 113: User <name> has modified configuration settings for LPS service.
This message is logged when a user modifies the settings in the LPS configuration utility.

Event Log Warning Messages

Message 121: Cannot rename/move file <name>, file does not exist.
This is an internal error caused most likely by passing an invalid batch filename in a command file, or by a user/process deleting a pass file after dropping but before processing.

Message 124: File <name> does not exist
This is an internal error commonly caused by dropping a command file before dropping the batch file (.bch).  In this case, the command file is renamed to *.cme.

Message 125: Warning, Loftware Print Server is configured to run in demo mode.
There is no hardware key present.  If data on your label is scrambled, the Loftware sub-system is configured to run in demo mode (normal during evaluation periods).

Event Log Errors

Message 103: The control handler could not be installed.
An internal error during service startup, possible causes: low resources.

Message 104: The initialization process failed.
Something failed during the service initialization process (startup) follows one of the more verbose messages.

Message 114: Failed to create scan thread due to low memory resources.
The system could not allocate the requested resources to create a thread.  Check resources, correct, reboot, and retry.

Message 115: Failed to create scan thread.
Internal error.  During initialization process, system has issued this error.  Reboot (power off) and retry.

Message 116: Failed to initialize OLE Libraries.
There is an error initializing the OLE libraries (dlls).  This is usually caused by a [separate] install that incorrectly overwrites one of the OLE DLLs.

Message 117: Failed to connect to Batch Print.
The Loftware Batch Print sub-system failed to initialize.  The most common reason is either incorrect Key (there is a Loftware key on the PC, but it is NOT a Loftware Print Server key) or invalid default DCOM permissions.

Message 122: Invalid directory/Cannot create for <name>, Dir <name>.
The service requires a directory ‘OLEBP’ to be created as a child to the scan directory.  On service startup, if the directory does not exist an attempt is made to create the directory.  This can fail because of invalid access rights to the path, or the scan path is incorrect to begin with (deleted after configuration).  The service needs access to Loftware sub-system files.  The llmwdn32.ini file in the Windows directory has been deleted or corrupted.

Message 126: Call to Remote Batch Print generated an exception!
Internal error.  Contact Loftware should this error occur.