The content you are looking for has been archived. View related content below.
This article describes how to configure diagnostic tracing in FlexNet Manager Suite using *.trace files.
This style of tracing can be generated by many processes that run in the application server, beacon, and agent components. It is primarily used when the normal logging solutions do not provide enough information, even with debug settings enabled.
This style of diagnostic tracing is configured using a *.trace configuration file. The name and default location of the file varies for different components as per the following table.
Component |
File Name |
Windows File Location |
Unix File Location |
Full Agent |
etcp.trace |
C:\Program Files (x86)\ManageSoft |
/opt/managesoft |
Lite Agent |
ndtrack.trace |
Wherever the ndtrack.exe is located (i.e. C:\Temp\) |
/etc |
Beacon |
etdp.trace |
C:\Program Files (x86)\Flexera Software\Inventory Beacon |
N/A |
Application server |
etap.trace |
C:\Program Files (x86)\Flexera Software\FlexNet Manager Platform |
N/A |
Note: Generated trace files can grow quickly, and be very large. Consider compressing trace files before sending them on to anybody else.
on
Aug 11, 2020
04:47 AM
- edited on
Aug 11, 2022
10:36 PM
by
ChrisG
Very useful for FNMS .. This helps a lot to me..specially step wise and graphical representation of FlexNet Manager
Regards
David