Error No Servers Were Found On The Network From On-Demand Print Client

Message

When launching the On-Demand Print Client, an error occurs stating:

Solution

This error usually occurs if you are attempting to run the On-Demand Print Client without having first started the Loftware Print Server (in earler versions, called "WatchDog-NT").  In most situations, the solution is to simply start the LPS (Loftware Print Server) and then re-launch the Client; it searches the network for the LPS and then automatically logs in once it has been located.

In some cases, such as if the client PC is located on a separate subnet from the LPS, the Client is not be able to find the LPS. If you have verified that the LPS is running and you are still receiving the 'no servers found' error, you need to create a llmwclnt.ini file that explicitly tells the On-Demand Print Client where to find the Loftware Print Server. The process for creating this file is detailed below:

1. Browse the Loftware Labeling installation directory from the Windows or Windows NT desktop, usually C:\Program Files\Loftware Labeling (or llmwin32 in earlier versions) ) and look for a file called llmwclnt.sav.
2. Rename the file llmwclnt.ini and then open it in Notepad or an equivalent ASCII text editor. If an llmwclnt.ini file already exists, simply open it in an ASCII text editor.The contents of the file vary depending on the version of the LPS you have installed.

Although the llmwclnt.ini file is initially created in the install directory on the server, it ultimately must be in the same location as On Demand Print Client executable (llmwclnt.exe) itself. By default, the executable file is also located in the install directory, and as such you shouldn't need to move the *.ini file after configuring it (see below). If however, you have manually moved the Client executable to a different folder, you will need to also move the llmwclnt.ini file to that same folder before the Client can be launched successfully.

Versions 4.2.2.7 and later

In these later versions, all information required by the Client for locating the LPS is automatically written to the file. Scroll to the bottom of the file and you should find an entry similar to the following:
 
[LPS]     Name=LPS     LabelsPath=\\LPS\LOFTWARE$\LABELS     LayoutPath=\\LPS\LOFTWARE$\LAYOUTS     ScanPath=\\LPS\LOFTWARE$\WDDROP     PrinterPath=\\LPS\LOFTWARE$     PasExt=pas     Address=555.55.5.55

Verify that this information is correct for your setup (see below for information on what each setting means), save the file as "llmwclnt.ini" ; then try relaunching the Client. As long as the Client executable and the ini file are in the same directory, you should be able to launch without error.

Versions Earlier Than 4.2.2.7

Earlier versions of the LPS create an llmwclnt.sav file that contains only sample information. This information provides guidelines for configuring the file, and leaving the sample data does not affect the Client as long as each line is proceeded by a semicolon ( ; ). For the purposes of this article however, you may find it less confusing to simply clear the sample data and start fresh. In either case, scroll to the bottom of the file and add the following information.

Note: Settings in bold are required.

[Unique section name]Name=The computer name of the serverAlias=The common name for the serverAddress=The IP address of the serverLabelsPath=UNC path to the labels directory{}LayoutPath=UNC path to the layout directory{}PrinterPath=UNC path to the install directory{}ScanPath=UNC path to the WatchDog-NT scan directory{}PasExt=Extension to be used for pass files dropped by the Client{}*

*{} If different from default 

Example:
[LPS]Name=LPSAlias=Loftware Print ServerAddress=555.55.5.55LabelsPath=\\LPS2000\LOFTWARE$\LABELSLayoutPath=\\LPS2000\LOFTWARE$\LAYOUTSPrinterPath=\\LPS2000\LOFTWARE$ScanPath=\\LPS2000\LOFTWARE$\WDDROPPasExt=xyz

Once you have entered the required information, save the file as "llmwclnt.ini" and then try relaunching the Client. As long as the Client executable and the ini file are in the same directory, you should be able to launch without an error.