Troubleshooting Inventory

Inventory Installation

Inventory is installed as a result of the agent installation and includes and/or uses the following files:

Installation files

LDIScn32.exe
ldapwhoami.exe
AMTScanner.exe
ClientRollingLog.dll
ClientRollingLog.log4net
elogapi.dll
GatherProducts.exe
GPMM.exe
HPScanner.exe
Lclxclnt.dll
ldaccount.dll
ldapinfo.dll
ldappl3.ini
ldapwhoami.exe
ldavhlpr.dll
LDISCN32.exe
LDServerRoles.exe
LDMBBApi.dll
LDProfile.exe
libhttp.dll
loc32vc0.dll
LocalPrtInfo.exe
log4net.dll
ltapi.dll
processrunner.dll
psapi.dll
ServerScanner.exe
ThinClientScanner.exe
vulscan.dll
WMIRulesScan.exe

Possible Installation issues

If the following option is checked within the agent configuration when the agent is deployed, you could possibly see a delay in the installation completing and the first inventory scan being sent:

To start: How to use 10 simple checks to Troubleshoot Inventory - Devices not updating, Duplicated or Missing Scans

In order to effectively troubleshoot Inventory a general understanding of the Inventory workflow is necessary.

Inventory Service Settings

Settings for the inventory service can be found on the core server by opening the 'Ivanti Configure Services' (SvcCfg.exe) application from the Start Menu, from the \Program Files\LANDesk\ManagementSuite\ directory, or by navigating to Configure > Services > Inventory.

For additional information on these settings as well as the Advanced Settings please click here.

Inventory Client Settings

Client inventory settings can be found within the agent configuration or agent settings options within the 'Configuration' menu in EPM.

For additional information on the client settings please click here.

General Inventory workflow

Initiating an Inventory Scan

Inventory Scans are initiated on the client by calling LDISCN32.exe.

LDISCN32.EXE is located in the LDCLIENT directory on the client.

Typically if there is an issue related to the scanner you will be asked to gather a debug output file.

From the run line on client computer run the following command:
"C:\Program Files\LANDesk\LDClient\LDISCN32.EXE" /F /O=c:\ioutput.txt

This will create an output debug file with additional troubleshooting information.

Client Initiated

Inventory scan launched through the Local Scheduler on the client
Inventory Scanner is run from the Ivanti Management Program group on the core server using the following syntax:
"C:\Program Files (x86)\LANDesk\LDClient\LDICN32.EXE" /V

A Managed Script is Scheduled and run the client computer through Scheduled Tasks. This is accessed by going to the Distribution tool group, and then the Manage Scripts tool. Within that tool there is an "inventoryscanner" script that contains the following commands:

Core Initiated

Right-clicking a computer or computers and selecting Hardware Scan, Hardware and Software Scan, or Full Sync Scan
Using the Manage Scripts tool. Go to the Distribution tool set and select "Manage Scripts". Within there is an "inventoryscanner" script. Right click this script and schedule it.

Scanning for additional data such as registry keys, additional file types, etc

Scanning for additional data and other additional Inventory settings can be found in the Manage Software tool.

For additional information:https://help.ivanti.com/docs/help/en_US/LDMS/10.0/Windows/inv-c-settings.htm?Highlight=manage software

Communication with the Core Server

Inventory Scanner connects to the Core Server to get Scan Instructions using the Syntax below

GET /ScanInstructions/InventoryService/PING/{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} (Where xxx .. is the Computers Device ID)
After the Inventory Scanner completes running it posts the information to the Core "PostingData" web service using the following syntax taken from the IIS log:

POST /postingData/scan.upload prefix=ldscan\decomp&suffix=.SCN

data-mce-style="padding-left: 30px;" style="padding-left:30px"

TMP = This is a temporary file used when a client communicates to the core server.
SCN = This is a regular scan file waiting for the Inventory Server to process.

By default, the server has a limit in scan file size of 10000000 (or 10 meg) for scan files. This number can be modified in Configure Services -> Inventory -> Advanced Settings -> Max Scan File Size. If the number exceeds the set amount, scans will be moved to the ERRORBIGSCAN folder If the scan files in the LDSCAN folder exceed this number you can change this number to a more suitable one.

Inventory Server Service

Inventory Server Service file location

"C:\Program Files\LANDesk\ManagementSuite\LDInv32.exe"

Inventory Server Service Log Files

The service log file is located here: C:\ProgramData\LANDesk\LDINV32.LOGThe Event Viewer is an excellent way to view activity for the Inventory Server Service. Useful events will be listed in the Windows Logs - Application section.You can filter by Event Levels "Critical", "Warning", and "Error" and then filter the Sources to show "LANDesk Inventory Server" to show only events relating to the Inventory Server Service.

From the Event Viewer - Windows Logs - Application log, click on the "Filter Current log" in the right-hand pane.
Select "Critical", "Warning", and "Error" in the "Event Level" section.

There are three different types of messages to look for:

Out of sync scans: By default, the Inventory Server will "flag" a machine as out of sync if it hasn't heard from the machine in more than 24 hours. This basically means that the next time the device sends in an inventory scan it will be a full scan. When experiencing problems and backups with inventory a large number of these log entries are normal as the inventory catches up over the next 1-2 days.
Errors: There are many possible errors that the Inventory Server can log so without going into detail it would be best to search the community for the error in question. There is usually a document or discussion that explains the error in more detail and how to correct it.
Blocked Inventory Items: The Inventory Server will flag unknown or unexpected information in a scan file and block the scan from being inserted into the database. That information is recorded on the core under Configure - Services - Inventory Server - Unknown Items. Most of these entries are normal and should be left as blocked as they may contain corrupt information that doesn't need to be in the database, however, when using Custom Data, for example, the information may need to be allowed.

Possible Issues

Issue: Unable to start LANDESK Inventory Server Service and settings missing from Configure Services

Issue: Core Will Not Process Inventory Scan Due To Large File Size

Error: "The Inventory Server Did Not respond" when running Inventory Scan

Error: Committing on Table...Increased column size might be necessary (Event ID 4100)

Reinstalling the service

At times it may be necessary to remove and re-install the LANDesk Inventory Server service.

"C:\Program files\LANDesk\ManagementSuite\LDInv32.exe" /Remove"

"C:\Program files\LANDesk\ManagementSuite\LDInv32.exe" /install"

Managed Planet Core Scan Processor Service

If the "Enable Real-time Processing" option is turned on in Data Analytics the Inventory Scanner service will ask the core for Scan Instructions and normal scan instructions plus additional instructions are sent with Data Analytics data. This includes active rules that are set in Data Analytics.

The service watches the LDSCAN folder for the .MP or .MINIMP files. The Managed Planet Core Scan Processor service must be running in order to process scan files as they come in.

When the "Enable Real-time" processing function is turned on in Data Analytics the Intermediate File Extension in Configure Services -> Inventory -> Advanced settings is set to ".MP' as depicted below.

If the Managed Planet Core Scan Process Service is not consuming the Data Analytics scan process and they are piling up in the MP_TEMP folder, check the account that the Managed Planet service runs with. This account must have rights to access the LDSCAN folder.

Basic Troubleshooting Guide - Data Translation Services - Real-Time Processing

Enable Core Scan Debugging and Data Analytics Logging

Communication with the Core Server

The Communication process with the Web Service is the same as the regular process, but the files have a .MP or .MINIMP suffix and instead of the regular Inventory Server service processing the file the file is processed by the Management Planet Core Scan processor service and then modifies the scan file to ready it for LANDesk Inventory Server service and is moved to the regular LDSCAN folder.

Service file location

"C:\Program Files\LANDesk\ManagementSuite\MPCore.exe"

Log Files

C:\Program Files\LANDesk\ManagementSuite\log\MPCore.Exe.Log

Possible Issues

Issue: MP files are collecting in the LDSCAN folder

Thousands of .MP files are stacking up in the LDSCAN folder

The following rules should not be made active due to performance impact:

Web Import

B2B Connectors

Import Data

Calculate Data

Tasks

Inventory is run based upon the criteria inventory settings criteria within the agent configuration. You can view the scheduler tasks through the local scheduler on the device by following the documentation below:

How To: View Local Scheduler Tasks on a Client

When running a task from the core server you may encounter various Status messages as the scan progresses,

Directories

Location	Description
\Program Files (x86)\LANDesk\LDClient\Data	Client - Inventory Data Files
\Program Files (x86)\LANDesk\LDClient\	Client - Inventory installation files/exes
\Program Files\LANDesk\ManagementSuite\ldlogon	Server - Inventory Data Files

Registry Keys

Key name	Description
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Intel\LANDesk\LDWM	Core Server Communication
HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\Common Api	Device ID (x32)
HKEY_LOCAL_MACHINE\SOFTWARE\Intel\LANDesk\Common Api	Device ID (x32)
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LANDesk\Common Api	Device ID (x64)
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intel\LANDesk\Common Api	Device ID (x64)

Database Tables and Inventory Information

Quick SQL Script to find all of your Inventory Attributes in your LANDesk Database

How to determine the table size of a Microsoft SQL Server database

How to find out Database information for Inventory Items by the Object or Attribute name

Gathering logging information for Ivanti support

About Inventory Scanner Switches

How to generate an inventory output file from a client for LANDESK support to do further troubleshooting?

How To: Enable XTrace Diagnostic Logging for the LANDESK Core and Clients

Standard Log Files

Windows Application Event Viewer - Most LANDesk Inventory Server errors or exceptions are logged to the Application Log

Gatherproducts.log - \Program Files (x86)\LANDesk\LDClient\Data

ldiscn32.log - \ProgramData\LANDesk\Log

LDInv32.exe.log - \Program Files\LANDesk\ManagementSuite\log\

Trace Log Files

ldapwhoamixtrace logging - ldapwhoami.log - \ProgramData\LANDesk\Log

Note: This log file will only be created if xtrace in enabled.

Debug Logging

Debug Scanner log - ldiscn32.log - \Program Files (x86)\LANDesk\LDClient\Data
Inventory Server Service log - ldinv32.exexxxxx_xxxxx.log - \Program Files\LANDesk\ManagementSuite\log\LDInv32.exexxxxx_xxxxx.log

Note: This is the rolling log and must be manually enabled in Configure | Services | Inventory | Advanced Settings | Use Rolling Log = 1 on the core server.

Performance Issues

Performance issues are typically manifested by scans not processing or scan processing too slowly. Further information on making sure this process goes smoothly can be found here in How to keep inventory up to date and flowing correctly.