Skip to end of metadata
Go to start of metadata

Description

When you attempt to start the Loftware Print server service, the Windows Services Console displays a warning dialog box containing the following message:

The Loftware Print Server service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.

Explanation

As the error message indicates, the Windows Services console made an attempt to start the Loftware Print Server service but was unsuccessful.  Due to a lack of information as to the cause, the Services console issues a fairly generic warning message.  Because of the lack detail, a bit more troubleshooting will be needed to determine the cause. 

Solution

Solution steps
  1. When a service fails to start, checking the Windows Event Logs is a great place to start your search for a cause.  One of the most common causes of this warning is a key failure which is clearly shown in the Windows Application Event Log entry shown below.  In this case, the log entry provides a link to information on enabling Emergency Mode for the license.

  2. Additional useful information may also be found in the Loftware.log.  This log file can be found by clicking on Start | All Programs | Loftware Labeling | System Folders | Logs.  (Note: On newer Windows operating systems like Server 2012, Windows 8, and Windows 10, you may need to locate the Loftware.log using a method for that particular operating system, such as  Using the Charms Bar, Start screen, and/or Tiles.) 
    Once Loftware.log is located, open this file using Notepad or your favorite editor and scroll to the bottom of the file for any additional clues that may be present.  For example, the following log entries show the software license in use was created for an LPS running in a VMware environment, however this particular LPS was NOT running on a VMware platform.

* 03-16-2016 (18:31:07) ->PW-LicenseRead failed, VMWare license is not running in VMWare

* 03-16-2016 (18:31:07) ->PW-ReadAndSetPWOptions, last error = 0

* 03-16-2016 (18:31:07) ->PW-OpenKey, Password Invalid, last error = 0

By checking the Windows Event Logs and the Loftware.log, you should have enough information to determine a course of action.  In the example above, a new license that is not designated for a VMware environment will be needed.

 

 

 

Article Number

2016021

Versions

Loftware Print Server versions 9.5 and higher.

Environment

All supported LPS environments.