What you will see
When running any Reports and/or Historical data on Lexmark Fleet Tracker ( LFT) version 3.0, the data doesnot generate.
Issue verification
Possible error on the logs:
- To check the logs, navigate to C:\Program Files\Lexmark\Fleet Tracker\server\logs.
- Open the latest lexmarkfleettracker-stderr log and look for error:
Caused by: oracle.net.ns.NetException: Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
Recommended solution
Navigate to C:\Program Files\Lexmark\Fleet Tracker\server\webapps\ROOT\WEB-INF\Classes, open the LFM-config.properties file, and then verify the following:
- Check whether the LFM-config properties are in this format:
dataSource_dwh.driverClassName= oracle.jdbc.OracleDriver dataSource_dwh.url: jdbc:oracle:thin:@//ip_addressdataSource_dwh.username= Admindwh dataSource_dwh..password= manager366
- Change to the correct format.
- Make sure the dataSource_dwh.url, username and password are correct.
- Make sure the URL has the 1521 port number; i.e., jdbc:oracle:thin:@// ip_address:1521/xe.
For instance:
dataSource_dwh.driverClassName= oracle.jdbc.OracleDriver dataSource_dwh.url: jdbc:oracle:thin:@//ip_address:1521/xe dataSource_dwh.username= Admindwh dataSource_dwh..password= manager366
IMPORTANT! After modifying the properties file, restart Lexmark Fleet Manager ( LFM), wait for a roll up, and then wait for approximately 30 minutes before running any report and/or historical data.
Still need help?
If you require additional assistance, please close this window and locate
Get In Touch with Lexmark! for contact information.
NOTE: When calling for support, you will need your printer model/ machine type and serial number ( SN). Please be near the products described in this article to expedite the support process and reduce callbacks.
LEGACY ID: SO7676