Adopted: Troubleshooting Inventory

FlexNet Manager Suite 2021 R1 (On-Premises)

Inventory gathering and upload is a sophisticated chain from target inventory device through inventory beacon to central application server. For general trouble-shooting over the whole process, see the online help for FlexNet Manager Suite under Inventory Beacons > Inventory Beacon Reference > Troubleshooting: Inventory Not Uploading. This topic focuses entirely on inventory collection on the target inventory device.

The regular log file for the ndtrack executable is identified in [Registry]\ManageSoft\Tracker\CurrentVersion\LogFile (see LogFile (inventory component)). In the Adopted case, the default paths are:
  • On Windows platforms, $(TempDirectory)\ManageSoft\tracker.log
  • On UNIX-like platforms, /var/opt/managesoft/log/tracker.log (when the ndtrack executable runs as root).

For advanced trouble-shooting, you may require more advanced tracing and logging. You may also be asked to submit a trace file to assist the Support team at Flexera to solve difficult problems in your environment.

To configure advanced tracing for the installed FlexNet inventory agent:

  1. In a flat text editor, open the etcp.trace file.
    In the Adopted case, this file is co-located with the installed ndtrack executable on the target inventory device:
    • On Windows, the default is C:\Program Files (x86)\ManageSoft\etcp.trace
    • On UNIX-like platforms, the default is /opt/managesoft/etcp.trace.
  2. Configure the name and location of the trace/log file that will be generated on the inventory device.
    The hash or pound character (#) identifies a comment. To "uncomment" a line in the .trace configuration file means to delete (only) the leading hash character. Choose one of the following lines, uncomment it, and optionally modify it to your requirements. On Windows:
    #filename=C:\ManageSoft%p_%d_%t_%u.log	# filename pattern with everything!
    On UNIX-like platforms:
    #filename=/tmp/log/ManageSoft%p_%d_%t_%u.log # filename pattern with everything!
    See the notes within the file header for the use of the supported variables within the file name.
    Tip: It is best practice to use a pattern that includes (at least) either a date stamp (%d) or a sequential number (%u). Without these, the fixed file name means tracing information is appended to the same file with every inventory collection. This can quickly produce a trace file too large for text editors to read, and too hard to manage in terms of disk space. Variables in the file name trigger creation of a new file each time the associated variable is changed (or, for %u, at every invocation of ndtrack).
    Important: The log file path:
    • Must be on the same drive as the ndtrack executable (on Windows devices)
    • Must exist and be writable before the ndtrack executable is next invoked (tracing does not create any directories, and does not function if any directory in the specified path is missing or unwritable).
  3. Uncomment the lines for which you want to enable tracing (ensuring that the uncommented line now starts with a plus sign).
    The tracing controls are arranged hierarchically. For example, uncommenting the one line for +Inventory/Tracker enables tracing for all child controls, as in this example:
    This setting enables (almost) all tracing related to the tracker component (ndtrack). You can also create an exemption to the general setting by making the appropriate line starts with a minus sign. For example, this one-line change within the above:
    turns off tracing for everything related to gathering inventory from the Windows registry (that is, the disable setting is also inherited by the Inventory/Tracker/Registry/Keys and /Values controls).

    One control that may affect the tracker component is outside this set. Because the tracker attempts an upload to the inventory beacon as soon as inventory gathering is complete, its tracing is affected by the +Communication/Network setting (along with the ndupload and ndlaunch components). This enables tracing of all network communications, including server certificate checking and the like.

    Some common choices for tracing the inventory gathering process are listed in the table below.

  4. To turn off tracing for an individual line that has previously been enabled, either comment out the line again, or switch the plus sign to a minus sign at the start of the line. A quick way to turn off tracing but keep all the settings for future use is to comment out only the filename setting that specifies the log file.
Some of the more commonly used tracing options for the tracker include the following:
Category Option Notes
Networking +Communication/Network

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 executable.



Shows active preferences, whether set in the registry (on Windows platforms) or in the config.ini file (on UNIX-like platforms), or inbuilt default values.

Hardware inventory


Traces all hardware inventory classes visible in the <Hardware> node in the .ndi inventory file, including CPU information and virtualization.

Software inventory


Traces the inventory operations that populate the <Package> nodes in the .ndi inventory file.

Software inventory


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 archive.


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.

FlexNet Manager Suite (On-Premises)

2021 R1