How to Enable Trace level logging

How to Enable Trace level logging


This KB article will cover the configuration and collection of trace files within FNMS. For additional logging of what is being collected during the inventory, It will cover the different types of trace files including details on lite agents.



Trace level logging can be performed on the batch, application, beacon, and agent and is used primarily when the normal logging solutions do not provide enough information, even with debug settings enabled.

By generating a trace log you can track much more activity although tracking everything can result in very large files so be warned to only use this when necessary and do not forget to turn it off when you're done.


Trace file location per component

The location of the trace files is dependent on what you are looking to trace. Each component has a different location, see the below table for reference


File Name

Windows File Location

Linux File Location

Full Agent


C:\Program Files (x86)\ManageSoft


Lite Agent (remote execution)


Wherever the ndtrack.exe is located (i.e. C:\Temp\)

root /etc 



C:\Program Files (x86)\Flexera Software\Inventory Beacon




C:\Program Files (x86)\Flexera Software\FlexNet Manager Platform


Note: that the Lite Agent (remote execution) trace file should be called ndtrack.trace


How to run the trace files

  1. Go to the component that you want to run a trace on (see Trace file location per component)
  2. Navigate to the directory (see Trace File location per component)
  3. Take a backup copy if you require to revert back to the original
  4. Open the relevant Trace file (be aware you may need to first disable the relevant Flexera service via services.msc before this file can be opened or saved)
  5. Once opened find the following line and define a valid file-path (Please note the location must exist otherwise the trace will not work)


  1. Usually, the technical support member will inform you of what you will need to uncomment, to do so remove the ‘#’ from the beginning of the line


  1. Once done, save the document and attempt to perform the problem action again,


  • Agents run the following commands
    • For Windows Agents and Lite Agents: ndtrack.exe -t Machine -o LogFile=C:\Temp\tracker.log -o Upload=false -o MachineInventoryDirectory=C:\Temp
    • For non-Windows Agents: ./ndtrack -t Machine -o LogFile=/tmp/log/managesoft/tracker.log -o Upload=false -o MachineInventoryDirectory=/tmp/log/managesoft
    • For non-Windows Lite Agents: ./ -t Machine -o LogFile=/tmp/log/managesoft/tracker.log -o Upload=false -o MachineInventoryDirectory=/tmp/log/managesoft
  • Beacons execute a discovery rule or scheduled task etc.
  • Batch execute a license or full reconcile, one-off import, etc.

Note: It might be quite large prior to compressing, and might take a while to generate the relevant files

  1. Navigate to the location set within the trace.log file
  2. The directory should include Managesoft_#_Date.log (if kept default file name)
  3. Compress the files and attach to the case if needed

Note: remember to repeat steps 1 - 6 and to comment the code out using '#' or to restore to your backed-up copy.



  • Options Definitions (ETCP)

For the full guide see “Adopted: Troubleshooting Inventory” within the GatheringFlexnetInventory.pdf






Traces all low-level upload and download actions

(whether HTTP or HTTPS). It includes HTTPS certificate

checking and related areas. Covers actions by the

ndtrack, ndupload, and ndlaunch components.

All inventory


Traces all inventory operations, which on large inventory

tasks, could result in a sizable trace file.

All tracker


This traces almost all operations of the ndtrack





Shows active preferences, whether set in the registry (on

Windows platforms) or in the config.ini file (on UNIXlike

platforms), or inbuilt default values.




Traces all hardware inventory classes visible in the

<Hardware> node in the .ndi inventory file, including

CPU information and virtualization.




Traces the inventory operations that populate the

<Package> nodes in the .ndi inventory file.




Tracing mainly for file inventory gathering (such as the

<Content> and MD5 nodes of the .ndi file).

Oracle inventory


When the inventory device hosts Oracle Database, this is

the tracing for local Oracle inventory.



Traces the preparation of the .ndi inventory file(s),

keeping in mind that on an Oracle Database server, there

may be multiple files generated.



Traces the compression of the .ndi file into a .gz




Traces the upload of the .ndi.gz archive to an

inventory beacon by the tracker.

Tip: If the immediate upload by the tracker fails for

some temporary reason, the upload is attempted

again later by the ndupload component. While this

component does not provide this same level of

operations tracing as the tracker does, you can

enable +Communication/ Network for low-level

tracing of each step in the upload interaction.



Was this article helpful? Yes No
100% helpful (2/2)
Version history
Revision #:
4 of 4
Last update:
‎Aug 11, 2020 04:55 AM
Updated by: