Logs for Troubleshooting

If the installation program cannot install Tenable Identity Exposure on a machine, you can forward the log file to our support (https://community.tenable.com/s/).

This log file is in your %tmp% folder, and its name always starts with “MSI” followed by random numbers, such as MSI65931.LOG.

To generate log files in another location (for example, if you placed the installer on the desktop):

1. In the command line of the local machine, type cd desktop.

2. Type .\installername.exe /LOGS "c:\<path>\logsmsi1.txt".

Tenable Identity Exposure generates log files for the various services on the individual installation.

• From the Directory Listener server — <Installation Folder>\DirectoryListener\logs

• From the Security Engine Node server — <Installation Folder>\SecurityEngineNode\logs

• From the Storage Manager server — <Installation Folder>\StorageManager\logs

• From the Directory Listener server and or Standalone Secure Relay server — <Installation Folder>\SecureRelay\logs

The default platform log files rotate when they reach a size of 100 MB each and then get compressed. These tasks automatically generate during installation in the Windows Task Scheduler. The following is an example of the tasks on the Security Engine Node node.

The Indicator of Attack (IoA) script creates a log file (example Register-TenableIOA-xxxx.log) in the same location as the script. You can review it there is any error or issue during the installation.

• Short-term retention: Keep debug logs for a short period such as 7 days after they are generated. This allows you to diagnose recent issues while minimizing storage consumption.

• Long-term archiving: Consider archiving a subset of debug logs for longer periods for compliance or troubleshooting purposes. You can store them to a safe location or compress them for efficient space utilization.