Home
Troubleshooting and support
Learn about solutions to common problems that might arise when you use BigFix Inventory BigFix Inventory and how to find logs and trace files that help you troubleshoot those problems.
Interrupting software scan
BigFix Inventory scans run in the background. Fixlets, such as Initiate Software Scan and Initiate Software Scan on Shared Disks trigger the scan to run in the background.

Troubleshooting and support
Learn about solutions to common problems that might arise when you use BigFix Inventory BigFix Inventory and how to find logs and trace files that help you troubleshoot those problems.
- Troubleshooting a problem
  Troubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is to determine why something does not work as expected and explain how to resolve the problem.
- Duplicate UUIDs problem
  BigFix Inventory requires unique virtual machine UUID (Universally Unique Identifier) numbers to calculate the capacity for all virtual machines and to detect virtualization hierarchy. If there are computers with duplicated UUIDs, a message is displayed in the To Do list. The import log also shows a warning about duplicate UUIDs.
- Interrupting software scan
  BigFix Inventory scans run in the background. Fixlets, such as Initiate Software Scan and Initiate Software Scan on Shared Disks trigger the scan to run in the background.
- Troubleshooting software discovery
  Problems with software discovery usually fall into one of three categories. The most common category is when the software is discovered but the components are assigned to an incorrect product. In this case, it is enough to reassign the component. The remaining categories include false-positive discovery, or no discovery due to the lack of the signature on the computer.

Interrupting software scan

BigFix Inventory scans run in the background. Fixlets, such as Initiate Software Scan and Initiate Software Scan on Shared Disks trigger the scan to run in the background.

With version 10.0.6, a fixlet '114 Interrupt BigFix Inventory Software Scans' is provided in the troubleshooting category to kill the running processes:

wscansw, wscanfs
runcit_sw.bat/sh
start_scan.sh (shared disk scan)

After executing the fixlet, Software Scan Status for Catalog, File, ISO tag and SLM Tag scan is set to 2:Interrupted. Each execution is tracked in LMT/CIT/end_scanner.log.

Steps to interrupt the scan in progress

To stop all running scans, perform the below recommended steps:

Stop any instance of the Initiate Software Scan and Initiate Software Scan on Share Disks.
Target the fixlet '114 Interrupt BigFix Inventory Software Scans' on the machines which are in scope.
Set the desired time range of operation. Use the UTC time and ensure that the time is in future.
1. The start of action BigFix Client depends on multiple factors, such as evaluation cycle. So, do not end action too soon.
2. Action is relevant only when processes, wscansw/wscanfs/runcit_sw/start_scan.sh are found.
It is possible to completely remove the relevance and let the action be executed.