FlexNet Manager Suite 2022 R2's configuration files have been updated from Log4Net to NLog format to utilize NLog's logging technology. An issue can occur when upgrading to version 2022 R2 if configuration files are not changed automatically to NLog format. During the upgrade process, some or all configuration files may remain in Log4Net format, causing logs not to be generated. The cause of the configuration files not updating formats during the upgrade process is still under investigation as a potential bug with our engineering resources.

If this issue occurs, when looking at any logging locations, you will only see logs that were present before the upgrade to version 2022 R2. To locate your current logs, the default location is: ProgramData\Flexera Software\Compliance\Logging. Logs are then nested into the subfolders of the specific component, for example, WebUI, BatchProcessScheduler, or BatchProcessTask.

Resolution

1. Navigate to ProgramData\Flexera Software\Compliance\Logging\ on the current system.
2. Compare the existing configuration files with those in the zip file attached to this article. Note any logs that do not contain NLog, as these will need to be replaced.
3. Replace the configuration files still utilizing Log4Net with the updated NLog configuration files.

Once you've replaced these files, FlexNet Manager Suite will start generating logs as normal.

To better understand the layout of NLog, below are examples of WebUI configuration files in Log4net and NLog format.

WebUI.config in Log4Net

WebUI.config in NLog