Some users may have issues creating a community account. For more information, please click here.

How to enable FlexNet Manager Suite diagnostic tracing

How to enable FlexNet Manager Suite diagnostic tracing

Summary

This KB article will cover the configuration and collection of trace files within FlexNet Manager Suite. 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.

Synopsis

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.

Trace configuration 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.

Component

File Name

Windows File Location

Unix File Location

Full Agent

etcp.trace

C:\Program Files (x86)\ManageSoft

/opt/managesoft

Lite Agent (remote execution)

ndtrack.trace

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

root /etc 

Beacon

etdp.trace

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

N/A

Inventory or batch server

etap.trace

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

N/A

How to configure tracing

  1. Take a backup copy of the configuration .trace file for the component you wish to trace.
  2. Open the relevant .trace file in a text editor.
  3. Find the "filename=..." and specify a valid full path to a file to hold generated tracing. Create the specified directory if it does not already exist exist.
  4. Remove the "#" (comment character) from the start of appropriate lines in the .trace file to specify what classes of tracing information should be generated. Usually a Flexera technical support team member will inform you of what classes to enable here.
  5. Save the updates to the .trace file.
  6. If you are seeking to generate tracing from a long-running process, you may need to stop and restart the process to pick up changes in the .trace file. As an example, if you are tracing beacon processes you may need to restart the Flexera Beacon Engine Windows service.
  7. Perform the problematic action again to cause tracing to be generated.
  8. Inspect the generated tracing details in the file specified by the "filename=" setting.
  9. Once done, revert the configuration changes that were made to the .trace file to avoid generating further tracing output.

Note: Generated trace files can grow quickly, and be very large. Consider compressing trace files before sending them on to anybody else.

Related articles and resources

 

Was this article helpful? Yes No
100% helpful (2/2)
Comments

@mcavanagh 

Very useful for FNMS .. This helps a lot to me..specially step wise and graphical representation of FlexNet Manager 

Regards

David

canada post tracking

Version history
Revision #:
8 of 8
Last update:
‎Sep 17, 2021 02:10 AM
Updated by: