Scan problems

Edit online

The most common problems with software scans are reported on the Software Scan Health widget. Refer to this topic to learn how to solve problems that are reported on the widget as well as for solutions to other scan-related problems.

Software Scan Health widget

For information about troubleshooting statuses that are displayed on the Software Scan Health widget, see: Statuses on the Software Scan Health widget

Other scan problems

In the Software Scan Status analysis, the status of a software scan is Failed and the value in the Is archive file size exceeded column is True.
The problem occurs when the scan file is larger than the maximum archive file size that can be sent by the BigFix® client. To solve the problem, perform the following steps:
  1. Check the BigFix client log for information about the size of the file that exceeded the limit. By default, the log is in the following location.
    • Linux /var/opt/BESClient/__BESData/__Global/Logs
    • Windows C:\Program Files (x86)\BigFix Enterprise\BESClient\__BESData\__Global \Logs
  2. Log in to the BigFix console.
  3. In the left navigation, click Computers, right-click the computer on which the scan failed, and then click Edit Computer Settings.
  4. Increase the value of the _BESClient_ArchiveManager_MaxArchiveSize parameter.
The software scan cannot be run on an LPAR because the Initiate Software Scan is not relevant on that computer
When a WPAR exists on an LPAR, all WPAR processes are visible on the level of the LPAR. When the software scan is running on the WPAR, the process is visible on the level of the LPAR and thus the Initiate Software Scan fixlet is not relevant on the LPAR. To run the software scan on the LPAR, wait for the scan to finish on the WPAR. Alternatively, perform the following steps:
  1. Log in to the BigFix console.
  2. Select the Initiate Software Scan fixlet and click Take Action.
  3. On the Target tab, select Dynamically target by property.
  4. Expand By Retrieved Properties and then expand By Computer Name.
  5. Select the LPAR computer on which you want to run the software scan and click OK.
Upgrade of the scanner fails on a WPAR.
When a WPAR exists on an LPAR, you must first upgrade the scanner on the LPAR, and then on the WPAR.

Software scans are failing. Computers where the scans are failing have the Low Disk Space status on the Deployment Health widget.
The problem might be caused by insufficient disk space for the scanner cache. To solve the problem, move the scanner cache folder to a different location or optimize the cache. For more information, see: Optimizing scanner cache configuration (BigFix scenario).

Software components that are installed in the /usr/lpp directory on AIX are not discovered.
The problem occurs because the /usr/lpp directory is by default excluded from software scans. Starting from scanner version 2.8.0.5000, the directory is included in software scans, and components installed in this directory are discovered. Thus, to solve the problem, update the scanner to version 2.8.0.5000 or later, and wait for the next scheduled software scan. Alternatively, you can manually include the /usr/lpp directory in software scans. For more information, see: Including the excluded directories back in scans (BigFix scenario).

After the update of the scanner, the number of software components discovered on AIX increased and some duplicates appeared.
Previously, the /usr/lpp directory was excluded from software scans. However, components whose signatures existed only in this directory were not discovered. Thus, starting from scanner version 2.8.0.5000, the /usr/lpp directory was included in software scans. It caused that more components are discovered and displayed on the reports. However, components installed in the /usr/lpp might also be discovered in other directories. In such case, duplicate components appear on the reports. To solve the problem, suppress the duplicates. For more information, see: Excluding and suppressing software instances. You can also create a custom rule that suppresses components that are discovered in /usr/lpp and other directories. For more information, see: Creating and managing custom rules for software.
How to check the results of the Software Scan Status analysis?
To check the status of the software scan, view the results of the Software Scan Status analysis.
  1. Log in to the BigFix console.
  2. In the navigation tree, go to Sites > External Sites > IBM License Reporting (ILMT) > Analyses.
  3. Select the Software Scan Status analysis.
  4. In the lower pane, open the Results tab.
    Tip: Scroll right to view all the relevant data.
    Results of the Software Scan Status analysis.