FNMS Logging Reference

FNMS Logging Reference

Introduction

The following log files and locations are used to within the FNMS product. If you see a log file that you are not expecting or are having trouble finding a log file, make sure you have considered the following key points:

  • The Presentation, Batch and Inventory Server components may be installed all on one server or split out into 2 or 3 different servers
  • It's possible to install a beacon on the batch server
  • Some components are shared between the beacon and inventory agent. Shared components are fully detailed below
  • The inventory agent may be installed on any of the servers and will always be installed on the beacon

Most of the FNMS log files are created using the log4net logging framework. Some log file locations are controlled directly in the registry whilst others are controlled by .config files. The .config files may exist in a base folder which is specified in the registry as explained below or in some cases they may be alongside the executable.

Presentation (Web) Server

FNMS Application Logs

Location

Default Base Directory

C:\ProgramData\Flexera Software\Compliance\Logging\

Common Alternative Base Directory

D:\ProgramData\Flexera Software\Compliance\Logging\

Finding Custom Paths

The logging base directory is controlled by a registry string called 'LoggingBaseDirectory' which is created under [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion] on the presentation server. If LoggingBaseDirectory is not set, it defaults to be under C:\ProgramData as above.The logging base directory contains a .config file for each logging module. The config file is an XML document which contains the actual location for the log file which by default will usually reference %property{ComplianceLoggingPath}. This property is expanded to be the LoggingBaseDirectory path.

Adjusting Logging Level

The .config files in LoggingBaseDirectory can be edited to adjust the logging level. Open the relevant .config file and scroll down to the bottom of the file to the <root> element. Adjust the <level value="INFO" /> line with the desired logging level. Typical options are ERROR, WARN, INFO, DEBUG.

WebUI Log

This log file captures events from the FNMS Web Page. This includes all views and reports under the 'Management' and 'Reports' sections in the web site. It does not capture the SAP Portal. If any error is displayed in the FNMS Web Site, there will typically be an error ID which is in the format of a GUID. The error ID is unique and changes each time the error occurs. To troubleshoot, you should typically ask the customer to reproduce the error, made a note of the error ID and then capture the WebUI log.

Location: <LoggingBaseDirectory>\WebUI\WebUI.log

SAP Portal Logs

This log file captures events from the SAP Portal UI in the FNMS web site.

Location: <LoggingBaseDirectory>\SAPPortalUI\SAPPortalUI.log

Single Sign-On Logs

This log file is used only if the customer has configured Single Sign-On with SAML or OAuth 2.0. It contains events related to requests to the identity provider and can be used in conjunction with the WebUI log for troubleshooting SSO issues.

Location: <LoggingBaseDirectory>\OAuth\sso.log

Compliance API Logs

FNMS has several APIs, this log file captures events specifically from the compliance API service at http://<FNMSUrl>/ManageSoftServices/ComplianceAPIService/ComplianceAPIService.asmx. This web service is commonly used for integrations between Flexera products and occasionally for customer created integrations.

Location: <LoggingBaseDirectory>\FNMSWebAPI\fnmswebapi.log

Baseline Import Logs

<Description>

Location: <LoggingBaseDirectory>\BaselineImport\<GUID>\BaselinePurchaseCreation.log

BatchProcessor Service Log

Not typically used for troubleshooting on presentation server

Location: <LoggingBaseDirectory>\BatchProcessScheduler\BatchProcessor.log

Other Relevant Logs

IIS Logs

IIS logs all incoming and outgoing web requests. The logs show the resource that was requested, requestor IP, HTTP status code etc. See https://msdn.microsoft.com/en-gb/magazine/dn519926.aspx for more information.

Location: %SystemDrive%\inetpub\logs\LogFiles\W3SVC1\u_ex[yymmdd].log

Custom Location: Locate by navigating to the 'Default Web Site' node in IIS Manager, then double click on 'Logging' on the right page

Windows Event Viewer

The FNMS ASP.NET applications and Windows Services can both create entries in Windows Event Viewer.

Location: Start > Run > Type 'eventvwr' > Enter

Batch Processing Server

FNMS Application Logs

Location

Default Base Directory

C:\ProgramData\Flexera Software\Compliance\Logging\

Common Alternative Base Directory

D:\ProgramData\Flexera Software\Compliance\Logging\

Finding Custom Log Paths

The logging base directory is controlled by a registry string called 'LoggingBaseDirectory' which is created under [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion] on the batch server. If LoggingBaseDirectory is not set, it defaults to be under C:\ProgramData as above. The logging base directory contains a .config file for each logging module. The config file is an XML document which contains the actual location for the log file which will by default usually reference %property{ComplianceLoggingPath}. This property is expanded to be the LoggingBaseDirectory folder.

Adjusting Logging Level

The .config files in LoggingBaseDirectory can be edited to adjust the logging level. Open the relevant .config file and scroll down to the bottom of the file to the <root> element. Adjust the <level value="INFO" /> line with the desired logging level. Typical options are ERROR, WARN, INFO, DEBUG.

Compliance Reader Logs

This log file captures the import of inventory from a data source into the FNMSCompliance database (compliance import) and the licence reconcile. On the batch server, remember that a data source can be a direct import from a database (e.g. FNMSInventory), or it can be an import of inventory from a .zip file which has been uploaded by a beacon.

Location: <LoggingBaseDirectory>\ComplianceReader\importer-[ddmmyyyy]-[pid].log

Tip: It's common to see strange log folders under the base logging folder on a batch server with a GUID for the name e.g. <LoggingBaseDirectory>\<GUID>\importer-[ddmmyyyy]-[pid].log.These log folders are supposed to temporarily exist whilst an import is running and deleted automatically when the import finishes. Sometimes the cleanup fails and the folder is left behind.If the task is finished, it's safe to go ahead and delete these folders.The logs in these folders are actually the logs that you see in the 'System Tasks' page in the UI - they're streamed into the database once the task has finished running.

Batch Process Scheduler Service Logs

This logs events from the 'FlexNet Manager Suite Batch Process Scheduler' Windows Service. The scheduler service picks up messages from the MSMQ queues which contains requests to trigger a task, and then it sends the tasks to the batch processor for processing. You will see in this log when a task is received, sent for processing and when the batch processor indicates the task has been completed. Some examples of jobs sent by the batch scheduler are Inventory imports and license reconciles (both manually triggered from the WebUI and overnight by the scheduled task), DataWarehouse Export, ARL Updates, AD Imports, database maintenance tasks. For a full list see BatchProcessType table in the compliance database.

Location: <LoggingBaseDirectory>\BatchProcessScheduler\BatchProcessScheduler.log

Batch Processor Service Logs

This logs events from the 'FlexNet Manager Suite Batch Processor' Windows Service. The batch processor service receives jobs from the scheduler, runs the job and then sends a message to indicate success back to the scheduler. You can look in this log for tasks being run by the batch processor and what command line is used to launch the task.

Location: <LoggingBaseDirectory>\BatchProcessScheduler\BatchProcessor.log

Batch Process Task Logs

Captures events from BatchProcessTask.exe in DotNet\bin\. Rarely useful but should be checked when troubleshooting batch processor issues. Logs when a task is queued with the batch processor and also logs the output when you run BatchProcessTaskConsole.exe manually to list tasks.

Location: <LoggingBaseDirectory>\BatchProcessTask\BatchProcessTask.log

Beacon Services Logs

Logs events relating to the beacons which report to this server (inventory-beacons application in IIS). This is not logging from a locally installed beacon. Some examples of information captured in this log are; generating updated discovery export files and sending that to beacons, triggering inventory imports after a 3rd party inventory package is uploaded from a beacon, trigger a business adapter import after an adapter zip file is uploaded from a beacon, generating new InventorySettings.xml files when the ARL gets updated and distributing that to beacons.

Location: <LoggingBaseDirectory>\InventoryBeacons\beacon-services.log

SAP Reader Logs

Captures information about the import of SAP inventory. On the batch server, generally a zip file containing SAP inventory is uploaded from a beacon, which is then unzipped and imported into the FNMS database. Be sure to also check SAPReader.log on the beacon.

Location: <LoggingBaseDirectory>\SAPReader\SAPReader.log

Baseline Import Logs

<Description>

Location: <LoggingBaseDirectory>\<GUID>\BaselinePurchaseProcessing.log

Business Importer Logs

Logs business adapter imports. Typically a business adapter will run on a beacon which will read information from the source and create a zip file with the data which is uploaded to the batch server. Then the batch server unzips this file and processes the information into the FNMS database. Be sure to check beacon logs too when troubleshooting business adapters.

Location: <LoggingBaseDirectory>\BatchDataImport\BusinessImport.log

Location: <LoggingBaseDirectory>\BatchDataImport\[AdapterName]-[GUID].log

Cognos Package Import Logs

Importing the cognos/analytics package is a one off task when installing cognos/analytics. Results are logged in this file. More information is in the installation documentation.

Location: <LoggingBaseDirectory>\CognosPackageImport\CognosPackageImport.log

Shadow Host Logs

Instead of the batch processor launching executables directly, it actually launches ShadowHost.exe which then takes care of launching the executable. This log file captures information from the ShadowHost. Examples of tasks captured include inventory imports, reconciles, business adapter imports with MGSBI.exe, ServiceNow exports, database maintenance tasks, SAP import, ARL import. Note that this log is mostly useful if you would like to see the command line used, or if the executable completely fails to launch and returns a non-zero exit code. If the executable launches but then fails, you will generally find the log file from that process more useful. For example if ComplianceReader is opened successfully but then fails to complete, check the Compliance Reader logs. ShadowHost logging also enables some interesting logging from both batch process services. For example you can see database queries made by these services.

Location: <LoggingBaseDirectory>\ShadowHost\

Tip: ShadowHost logging must be enabled manually by adding a new DWORD called 'ShadowHostTracingEnabled' with Value '1' under [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion]

 

Content Libraries Update Logs

2018 R2+

Logging files for all library updates (ARL, PURL, EOSL and SKU) are now handled by log4net and are logged in line with other FNMS application components.

Default Location

<LoggingBaseDirectory>\Flexera Software\Compliance\Logging\Content

Default Base Directory

C:\ProgramData\Flexera Software\Compliance\Logging\

Common Alternative Base Directory

D:\ProgramData\Flexera Software\Compliance\Logging\

Finding Custom Log Paths

The logging base directory is controlled by a registry string called 'LoggingBaseDirectory' which is created under [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion] on the presentation server. The logging base directory contains a .config file for each logging module. The config file is an XML document which contains the actual location for the log file which will by default will usually reference %property{ComplianceLoggingPath}. This property is expanded to be the BaseLoggingPath.

Adjusting Logging Level

The .config file in LoggingBaseDirectory can be edited to adjust the logging level. Open the relevant .config file and scroll down to the bottom of the file to the <root> element. Adjust the <level value="INFO" /> line with the desired logging level. Typical options are ERROR, WARN, INFO, DEBUG.

2018 R1 and earlier

Log files for all library updates (ARL, PURL, EOSL and SKU) are stored in the temp folder of the user who launched MgsImportRecognition.exe

Default Location

C:\Users\<ServiceAccount>\AppData\Local\Temp

Finding Custom Log Paths

To determine where the log will be stored, you will need to find which user account launched MgsImportRecognition.exe. If the library update has been triggered by the scheduled task on the batch server, this send the ARLDownload (and subsequently ARLImport and ARLCleanup) tasks to the batch processor. This means the account will be the same account that is being used to run the batch processor service. If MgsImportRecognition.exe is being launched manually, then the log will be in the temp folder of the user who launched the EXE.

Other Relevant Logs

IIS Logs

IIS logs all incoming and outgoing web requests. The logs show the resource that was requested, requestor IP, HTTP status code etc. See https://msdn.microsoft.com/en-gb/magazine/dn519926.aspx for more information.

Location: %SystemDrive%\inetpub\logs\LogFiles\W3SVC1\u_ex[yymmdd].log

Custom Location: Locate by navigating to the 'Default Web Site' node in IIS Manager, then double click on 'Logging' on the right page

Windows Event Viewer

The FNMS ASP.NET applications and Windows Services can both create entries in Windows Event Viewer.

Location: Start > Run > Type 'eventvwr' > Enter

 

Tip: It's possible to install a beacon on the batch server which will operate in 'direct' mode. If the customer has done this, you will also find the beacon logs on the batch server.

Inventory Server

FNMS Application Logs

Location

Default Base Directory

C:\ProgramData\Flexera Software\Compliance\Logging\

Common Alternative Base Directory

D:\ProgramData\Flexera Software\Compliance\Logging\

Finding Custom Paths

The logging base directory is controlled by a registry string called 'LoggingBaseDirectory' which is created under [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion] on the inventory server. If LoggingBaseDirectory is not set, it defaults to be under C:\ProgramData as above. The logging base directory contains a .config file for each logging module. The config file is an XML document which contains the actual location for the log file which will by default will usually reference %property{ComplianceLoggingPath}. This property is expanded to be the LoggingBaseDirectory path.

Adjusting Logging Level

The .config files in LoggingBaseDirectory can be edited to adjust the logging level. Open the relevant .config file and scroll down to the bottom of the file to the <root> element. Adjust the <level value="INFO" /> line with the desired logging level. Typical options are ERROR, WARN, INFO, DEBUG.

 Dispatcher Logs

This log captures events from the web resolvers about the import into the database of various files received from beacons. It's an important distinction that this does not include 3rd party inventory (SCCM etc) and business adapter imports. The most common types of files processed include ActionStatus, ActiveDirectory, ActivityStatus, BeaconStatus, ClientAccess, Discovery, Inventories, Logs and Usage Data.

Location: <LoggingBaseDirectory>\WebResolvers\dispatcher.log

Activity Status Logs

Similar to the dispatcher log, this log captures events from the web resolver about the import of information into the database. This log is specifically for .activity files. Activity files form a lot of the information you see on the System Tasks page in the UI. If you're troubleshooting a problem with the System Tasks page, this log can definitely be useful.

Location: <LoggingBaseDirectory>\WebResolvers\activitystatus.log

Beacon Status Logs

Similar to the dispatcher log, this log captures events from the web resolver about the import of information into the database. This log is specifically for .bstat files.

Location: <LoggingBaseDirectory>\WebResolvers\beaconstatus.log

Other Relevant Logs

IIS Logs

IIS logs all incoming and outgoing web requests. The logs show the resource that was requested, requestor IP, HTTP status code etc. See https://msdn.microsoft.com/en-gb/magazine/dn519926.aspx for more information.

Location: %SystemDrive%\inetpub\logs\LogFiles\W3SVC1\u_ex[yymmdd].log

Custom Location: Locate by navigating to the 'Default Web Site' node in IIS Manager, then double click on 'Logging' on the right page

Windows Event Viewer

The FNMS ASP.NET applications and Windows Services can both create entries in Windows Event Viewer.

Location: Start > Run > Type 'eventvwr' > Enter

Beacon Servers

Beacon Application Logs

Location

Default Base Directory

C:\ProgramData\Flexera Software\Compliance\Logging\

Common Alternative Base Directory

D:\ProgramData\Flexera Software\Compliance\Logging\

Finding Custom Paths

The logging base directory is controlled by a registry string called 'LoggingBaseDirectory' which is created under [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion] on the presentation server. If LoggingBaseDirectory is not set, it defaults to be under C:\ProgramData as above. The logging base directory contains a .config file for each logging module. The config file is an XML document which contains the actual location for the log file and the logging level

Adjusting Logging Level

The .config files in LoggingBaseDirectory can be edited to adjust the logging level. Open the relevant .config file and scroll down to the bottom of the file to the <root> element. Adjust the <level value="INFO" /> line with the desired logging level. Typical options are ERROR, WARN, INFO, DEBUG.

Active Directory Import Logs

This log captures the execution of the active directory imports which are configured on the 'Active Directory Imports' page in the Beacon UI. This log captures the LDAP connection being established with the domain controller and the import of Active Directory information. The import produces an .actdir file which is uploaded to the inventory server. Be sure to also check the Dispatcher log on the inventory server to make sure the data is successfully processed into the database.

Location: <LoggingBaseDirectory>\ActiveDirectoryImport\ADImport.log

Beacon Engine Logs

This log captures events from the Beacon Engine Service. This is one of the main log files on a beacon server and captures information about a lot of the background activities performed by a beacon. An example of some of the main events that are captured include; downloading and loading beacon policy, downloading updates to discovery & inventory rules, download discovery export file, downloading updated importer xml files.

Location: <LoggingBaseDirectory>\BeaconEngine\BeaconEngine.log

Beacon IIS Logs

Captures events from the beacons web server. The beacon web server generates and serves agent policy, settings, and upgrade files and accepts incoming files from agents.

Location: <LoggingBaseDirectory>\BeaconIIS\BeaconIIS.log

Compliance Reader Logs

Captures events from inventory imports (from 3rd party systems). To see the configured imports on a beacon you can look at the 'Inventory systems' page in the Beacon UI. It's an important distinction that this does not include inventory received from FNMS agents.

Location: <LoggingBaseDirectory>\ComplianceReader\importer-[ddmmyyyy]-[pid].log

Compliance Upload Logs

Logs events about the upload of 3rd party inventory. It's an important distinction that this does not include the upload of inventory received from FNMS agents (for this, see 'Uploader Logs' below). ComplianceUpload.exe is launched by the 'Upload third party inventory data' scheduled task.

Location: <LoggingBaseDirectory>\ComplianceUpload\upload.log

Inventory Rule Logs

Logs events from the execution of a Discovery & Inventory rule. You can see the configured rules in the Beacon UI on the 'Rules' page. Each rule execution will generate a new GUID (the task's unique SessionUID) which is used in the directory path when storing the log files.

Location: <LoggingBaseDirectory>\InventoryRule\<GUID>\

Tip: When troubleshooting, sort the InventoryRule folder by Date Modified to find the most recently created folder after triggering rule execution manually in the Beacon UI

Inventory Beacon Logs

Captures events from the BeaconUI and various other tasks performed by the local inventory beacon. The BeaconEngine.log will generally be the main log to look at when troubleshooting a beacon but it's worth checking this too.

Location: <LoggingBaseDirectory>\InventoryBeacon\inventorybeacon.log

Other Beacon Executable Logs

Uploader Logs (ndupload)

Default Directory

C:\Windows\Temp\ManageSoft

Common Alternative Directory

C:\Users\<service_account_username>\AppData\Local\Temp\ManageSoft

Finding Custom Paths

The log directory for ndupload is controlled by a registry preference. The registry preference usually includes a variable like $(TempDirectory) which is why you will see the location change depending on the user who ran the task. By default the task will run as the LocalSystem account whose $(TempDirectory) is C:\Windows\Temp. If the scheduled task is ran under a different account, or you run the executable manually then it will be the temp folder of the user who ran the task.

Uploader Logs

This log file captures the upload of all files except 3rd party inventory zips. If a file is in one of the 'Incoming' folders (default location C:\ProgramData\Flexera Software\Incoming), the upload will be logged here. This includes inventory, discovery, beacon status, activity status, client access etc. The files may be uploaded from agents which are reporting to the beacon or it may be files that were generated on the beacon itself, for example .activity files from a discovery & inventory rule execution.  - This log file is shared with agent as the agent also uses ndupload for "catch up" uploading if the initial upload fails.

Location: $(TempDirectory)\ManageSoft\uploader.log

Registry Key: [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Uploader\CurrentVersion\LogFile]

Package Retriever Logs

This log captures the download of upgrade and adoption packages.

Location: $(TempDirectory)\ManageSoft\packageretriever.log

Registry Key: [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\PackageRetriever\CurrentVersion\LogFile]

Other Relevant Logs

IIS Logs

IIS logs all incoming and outgoing web requests. The logs show the resource that was requested, requestor IP, HTTP status code etc. See https://msdn.microsoft.com/en-gb/magazine/dn519926.aspx for more information.

Location: %SystemDrive%\inetpub\logs\LogFiles\W3SVC1\u_ex[yymmdd].log

Custom Location: Locate by navigating to the 'Default Web Site' node in IIS Manager, then double click on 'Logging' on the right page

Windows Event Viewer

The FNMS ASP.NET applications and Windows Services can both create entries in Windows Event Viewer.

Location: Start > Run > Type 'eventvwr' > Enter

FlexNet Inventory Agents

Agent Application Logs

Location

Default Directory

Windows: C:\Windows\Temp\ManageSoft

Unix-based: /var/opt/managesoft/log

Common Alternative Directory

Windows: C:\Users\<username>\AppData\Local\Temp

Finding Custom Paths

The logging directories for all(except one) of the agent executables are configurable through agent preferences. On Windows all of the preferences are stored in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\. On Unix-based operating systems, the preferences are stored in a virtual registry in the /var/opt/managesoft/etc/config.ini file. On Windows, the preference usually includes a variable like $(TempDirectory) which is why you will see the location change depending on the user who ran the task. By default the agent will run most tasks as the LocalSystem account whose $(TempDirectory) is C:\Windows\Temp. If the executable is ran under a different account, or you run the executable manually then it will be the temp folder of the user who launched the executable.

Tip: When using remote desktop, watch out for temporary session folders which may contain logs, e.g. 'C:\Users\TonyM\AppData\Local\Temp\6\ManageSoft'. RDP generates a temporary session folder by default for %TEMP%. Make sure you are looking at the correct log by checking the timestamps.

Installation Logs

One of the most commonly used agent log files, this log captures events relating to the agent downloading and applying policy, client settings, schedule, failover settings and update packages. 

Windows Location: $(TempDirectory)\ManageSoft\installation.log

Unix Location: /var/opt/managesoft/nstallation.log

Registry Key / Config.ini section: [ManageSoft\Launcher\CurrentVersion\LogFile]

Tracker Logs

Captures events from inventory collection. This includes standard hardware and software inventory, Oracle inventory and client access inventory.

Windows Location: $(TempDirectory)\ManageSoft\tracker.log

Unix Location: /var/opt/managesoft/tracker.log

Registry Key / Config.ini section: [ManageSoft Corp\ManageSoft\Tracker\CurrentVersion\LogFile]

Policy Logs

Log file for the download and application of agent policy.

Windows Location: $(TempDirectory)\ManageSoft\policy.log

Unix Location: /var/opt/managesoft/policy.log

Registry Key / Config.ini section: [ManageSoft\Policy Client\CurrentVersion\LogFile]

Schedule Logs

Log file for the download and application of the agent schedule.

Windows Location: $(TempDirectory)\ManageSoft\schedule.log

Unix Location: /var/opt/managesoft/schedule.log

Registry Key / Config.ini section: [ManageSoft\Schedule Agent\CurrentVersion]

Security Service Logs

Captures events from the 'Flexera Inventory Manager security service' Windows Service. This service has two plugins, the usage agent and VDI endpoint plugin.

Windows Location: $(TempDirectory)\ManageSoft\securityservice.log

Unix Location: N/A

Registry Key / Config.ini section: Difficult to relocate. No registry preference. May be possible with .config file alongside mgssecsvc.exe

Uploader Logs

This captures events from ndupload.exe which is used to upload all types of files which can generated by the agent. However, it is only used for "catch up" uploads where the initial upload failed. For the first time upload, see the relevant log for the process that generated the file, e.g. the tracker.log for the upload of inventory and discovery files. This log file is shared with beacon.

Windows Location: $(TempDirectory)\ManageSoft\uploader.log

Unix Location: /var/opt/managesoft/uploader.log

Registry Key / Config.ini section: [ManageSoft\Uploader\CurrentVersion\LogFile]

Usage Agent Logs

Captures events from the usage agent which captures application usage information. The usage agent runs under the  'Flexera Inventory Manager security service' Windows Service.

Windows Location: $(TempDirectory)\ManageSoft\usageagent.log

Unix Location: /var/opt/managesoft/usageagent.log

Registry Key / Config.ini section: [ManageSoft\Usage Agent\CurrentVersion\LogFile]

VDI Logs

Captures events from the VDI endpoint agent. Only relevant on Citrix XenDesktop devices.

Windows Location: $(TempDirectory)\ManageSoft\vdi.log

Unix Location: N/A

Registry Key: [ManageSoft\VDI Endpoint Agent\CurrentVersion]

Other Relevant Agent Log Files

Adoption Logs

These files log the installation of an agent when a device is being adopted by a discovery & inventory rule. These will be useful when valid credentials have been provided for the beacon and it has managed to connect to the device successfully, but the installation subsequently fails.

Windows Location: $(TempDirectory)\adoption.log

Unix Location: /var/tmp/flexera/log/ndinstlr.log and ndinstlrsh.log

MSI Installation Log

This is the Windows Installer log file for the agent install. Created by default only when using the setup.exe to install the agent. 

Windows Location: %TEMP%\FlexNet Inventory Agent.msi.log

Unix Location: N/A

Tip: To generate a Windows Installer log file if you are running the MSI directly, you can use a command line like msiexec.exe /i "FlexNet Inventory Agent.msi" /l*v "%TEMP%\FlexNet Inventory Agent.msi.log". If you want to capture an MSI log for an adoption or other automated install, you can enable Windows Installer logging system wide on a device by adding the following registry string (you may need to create the key):

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
Reg_SZ: Logging
Value: voicewarmupx

Adapters, Integrations & Other

Business Adapters

Analytics

XenApp Adapter

ServiceNow Integration

ServiceNow > FNMS

<Some info about how to check exports in ServiceNow UI>

<Import into FNMS is handled by regular business adapter processes. Need to document this.>

FNMS > ServiceNow

Default Directory

Windows: C:\Temp\Log\log.log

Finding a Custom Path

The path for this log file is specified in the fnmp_servicenow_export.exe.config file which is stored in <FNMSInstallDir>\DotNet\bin\ServiceNowExport. To determine FNMSInstallDir, check the InstallDir string in the HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft key. The default InstallDir is C:\Program Files (x86)\Flexera Software\FlexNet Manager Platform\.

Information

The export from FNMS is performed by fnmp_servicenow_export.exe which is in <FNMSInstallDir>\DotNet\bin\ServiceNowExport on the batch server. You can trigger an export from the UI by navigating to System Menu > System Settings > ServiceNow.

BMC Discovery (ADDM) Adapter

App-V Server Adapter

BMC Atrium and Remedy Integration

HPE Universal Discovery (HPE-UD)

HP DDMI Adapter

Oracle Enterprise Manager (OEM) Adapter

Data Platform Integration

SVM Integration

 

 

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

Hi @dcollins ,

This really helps particularly related to FNMS>ServiceNow where there is no clue till day.

Appreciate all your efforts.

 

Regards,

Winvarma 

Please consider adding etap.trace & etcp.trace.

Hi mfranz, I am afraid it is not included in this document yet as I don't currently have a full breakdown of the options listed in trace logging, I will enhance this once I obtain the information.

That said we do have how to perform trace logging as separate KB articles for those that are interested, the trace config file itself tends to be pretty self-explanatory as to what information it gathers but I agree a document going into detail would be best

https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/How-to-enable-ETDP-Tracing/ta-p/1529...

https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/How-to-Enable-ETCP-Tracing-for-Inven...

Version history
Revision #:
4 of 4
Last update:
‎Jul 09, 2020 03:53 PM
Updated by:
 
Contributors