Thank you for your feedback

Information Required to Escalate Lexmark Fleet Manager (LFM) Issues

Document ID:FA926
01/22/14 Properties  


Escalation checklist; LFT2.0; LFT3.0; Lexmark Fleet Tracker; LSM; Services Monitor; Embedded; eLSM; LLT; Local Tracker; LPMA; Print Monitor Agent;


Lexmark Fleet Manager



Collect or capture all information below before opening an escalation item.

IMPORTANT! You should utilize all available technical support resources before electing to escalate issues.


Before you begin

Verify Lexmark Fleet Tracker product activation. Click here for additional information if necessary.


Step 1: Gather mandatory information below for ALL escalations.

  • Customer Information
    • Account Name
    • Account Address
    • Customer Name
    • Phone Number
    • Email Address
  • Lexmark Device Machine Type/Model

IMPORTANT! Please utilize this escalation template:

[PROBLEM DESCRIPTION] – Include details in Step 2.

  • Problem frequency
  • Readily repeatable or random issue

[SETUP or ENVIRONMENT] to include:

  • Number of affected devices (include Lexmark and/or non-Lexmark printers)
  • New roll out or new installation



Step 2: Problem Description

Provide a detailed problem description: 

  1. For data roll-up issues, include all LFM collectors involved: 
  • Lexmark Fleet Tracker (LFT 2.0 only)
  • Lexmark Services monitor (LSM)
  • embedded Lexmark Services Monitor (eLSM)
  • Lexmark Local Tracker (LLT)
  • Lexmark Print Monitor Agent (LPMA)
  1. Include code levels of affected LFM products.
  2. Details should include information about environment, architecture, installation, frequency (persistent and repeatable vs. random anomaly), functionality, etc.


Step 3: Capture Escalation Requirements

Collect the data points defined below for any or all solutions that are running in the environment.

a. LFT Data Points



How to Obtain (LFT 2.0)

LFT3.0 Locations

LFT log files

Required for debugging LFT services

1. Log on to the server that is hosting the LFT 2.0 Application.

2. Open file explorer and navigate to the default path C:\Lexmark\Lexmark_LFT\Logs.

3. Copy all log files into a .zip file and attach to escalation.

C:\Program Files\Lexmark\Fleet Tracker\server\logs

Screen capture of problematic behavior (i.e., error message, incorrect reading on webpage)

Provides a good overview of the problem especially if it’s a system error message

Use the ALT + Print Screen feature in windows or any screen capture utility available.

Same as LFT 2.0.

Check Oracle version installed on the hosting server.


1. Open LFT 2.0 webpage.

2. In left-hand frame under the Administration section, select LFT Status.

3. In the bottom-right frame you will see the Version.

Click Image to Enlarge

1. Open LFT 3.0.

2. Click on System Configuration.

Installation path of LFT and Oracle installations

Installation path may vary depending on which version of Oracle is used.

The default path for LFT is C:\Lexmark\Lexmark_LFT.

The default path for Oracle XE is C:\oraclexe.


b. LSM Data Points

Requirement Relevance How to Obtain
LSM log file Useful for understanding problematic behavior

1. Log on to the server that is hosting LSM Application.

2. Open file explorer and navigate to C:\Program Files\Lexmark\LSM \rXpress.log.

3. Copy the rXpress.log file and attach to escalation.

Screen Capture Provides overview of problematic behavior

Use the ALT + Print Screen feature in windows or any screen capture utility available.

Confirm rXpress service is running Required service for LSM

1. Open Windows Task Manager > select Processes tab.

2. Confirm rXpress.exe and rXpressStart.exe are running.

Installation path of LSM


The default path for LSM is C:\Program Files\Lexmark\LSM.

Note: LSM is self-contained and does not rely on Oracle for data storage on the LSM collector.

IMPORTANT: The LSM installer writes into a flat file system which shows up as rXpress.rx in the installation directory.

Deleting this file and restarting the LSM will remove all print data from the LSM collector. Configuration settings will remain, however, as they are stored in the registry.

 c. Management Information Base (MIB) Data

This is required for device support issues. Collect MIB data using the iReasoning MIB Browser Free Personal Edition.

NOTE: Exported data should be in XML format.

Step Action

Go to the MIB browser website.

At the bottom of the screen, click “I Accept”.

Select either setup.exe (for Windows) or (for all other platforms).

Click Image to Enlarge

4 Install the MIB Browser.

Note: Please follow the on-screen instructions during installation.
5 Launch the  icon.

Enter the printer’s IP address in the Address field.

Click Image to Enlarge

Click Operations, select Walk then click .

Click Image to Enlarge

After the data has loaded in the Result Table, click the  icon to begin the XML data export.

Click Image to Enlarge

Go under File and Save Session.

Click Image to Enlarge

d. Additional Oracle Database (DB) Information

For capacity issues, check Oracle version vs. size of users.dbf file to determine if database (DB) has gone over it's storage capacity.

Step Action

Determine Oracle Version to determine size capacity.

Note: To check the Oracle version, click Start All Programs View Oracle Version. Oracle 10g XE = 4 GB; Oracle 11g XE = 11 GB.


Locate users.dbf file and check size.

Note: This file determines size of DB. Default Oracle install directory: C:\oraclexe\app\oracle\oradata\xe\users.dbf


Check the size of users.dbf vs. the overall size capacity of the Oracle version being used.

Important! Issues will result if user.dbf is larger in size than Oracle version. Escalate DB issues right away.


Additional information

If you have any questions or encounter problems when collecting the data required above, please contact your next level of support or Lexmark Technical Support for any additional suggestions.

Additional information may be requested by the support agent.


Please enter the email address you would like to send a copy of this page to.