Software scan return codes
If the software scan fails, an error code that indicates why the scan failed is returned. Check what is the possible cause of scan failure that is indicated by each code and how to solve the problem.
Locating the return codes
- On computers with the BigFix® client.
Return codes are available in the results of the Software Scan Status analysis.
- On computers with the disconnected scanner.Return codes are available in the scanner_status.yml file that is located in the following directory. It is also added to every scan results package.
<disconnected_scanner_install_dir>/work
<disconnected_scanner_install_dir>\work
Software scan return codes
| Return code | Possible cause and solutions |
|---|---|
| 0 | No errors. |
| 1 | Scan data was not gathered. To verify what is the cause of the problem, go to the computer
where the problem occurred, open the command prompt and run the following
command.
|
| 2 | The scanner configuration file is corrupted. Reinstall or upgrade the scanner. For more information, see the following links. |
| 3 | A signature file could not be parsed. Reinstall or upgrade the scanner to redeploy the software catalog on computers where the problem occurred. For more information, see the following links. |
| 4 | Scan output file could not be saved to the output directory. Ensure that the
scan output directory is writable. By default, the directory is in the following location.
|
| 5 | The user that runs the scan does not have read permission to the scanner
configuration file. Ensure that the user has the read and write permissions to the following
directory.
|
| 6 | Scanner catalog does not exist on the endpoint. Reinstall or upgrade the scanner to redeploy the software catalog on computers where the problem occurred. For more information, see the following links. |
| 8 | Scanner internal error occurred. Gather scanner logs and
contact IBM Support. By default, the log files are in the following directory.
|
| 9 | The scanner timed out. Perform the following tasks.
|
| 10 | The scanner is being upgraded. Wait until the upgrade finishes. |
| 11 | Scan output file or directory is read only. Ensure that the scan output file
or directory is writable. By default, the directory is in the following location.
|
| 12 | The cit.ini file was not found. Install the scanner. By
default, the cit.ini file is located in the following directory.
|
| 13 | The scanner configuration file was not found. Reinstall or upgrade the scanner. For more information, see the following links. |
| 14 | The scanner trace file was not found. Reinstall or upgrade the scanner. For more information, see the following links. |
| 18 | One of the scanner files could not be open. Ensure that the administrator or
root of the computer on which the problem occurred has the read and write permissions to the
following files. Scanner configuration file CitHWConfig.xml,
scanner properties file Cit.properties, and scanner trace file
CitTrace.properties, which by default are in the following directory.
|
| 19 | One of the scanner files could not be renamed. Ensure that the administrator
or root of the computer on which the problem occurred has the read and write permissions to the
following files. Scanner configuration file CitHWConfig.xml,
scanner properties file Cit.properties, and scanner trace file
CitTrace.properties, which by default are in the following directory.
|
| 20 | One of the scanner files could not be deleted. Ensure that the administrator
or root of the computer on which the problem occurred has the read and write permissions to the
following files. Scanner configuration file CitHWConfig.xml,
scanner properties file Cit.properties, and scanner trace file
CitTrace.properties, which by default are in the following directory.
|
| 21 | The scanner configuration file is corrupted. Reinstall or upgrade the scanner. For more information, see the following links. |
| 22 | The scanner trace file is corrupted. Reinstall or upgrade the scanner. For more information, see the following links. |
| 28 | A required shared library file is not available. Reinstall or upgrade the scanner. For more information, see the following links. |
| 29 | The scanner timed out. Perform the following tasks.
|
| 30 | The scanner query failed. Gather scanner logs and
contact IBM Support. By default, the log files are in the following directory.
|
| 31 | The scan process was interrupted. On computers with the BigFix client, stop the running scan action and start the scans again. On computers with the disconnected scanner., rerun the scan. |
| 37 | Scanner internal error occurred. Gather scanner logs and
contact IBM Support. By default, the log files are in the following directory.
|
| 40 | An error occurred while creating the warning file during the software scan.
Ensure that the administrator or root of the computer on which the problem occurred has the read and
write permissions to the following directory.
|
| 41 | Scanner process initialization failed. Gather scanner logs and
contact IBM Support. By default, the log files are in the following directory.
|
| 42 | The signature catalog schema cannot be found. Reinstall or update the scanner.
For more information, see the following links.
If it does not help, gather scanner logs and contact IBM Support. By default, the log files are
in the following directory.
|
| 49 | The user that runs the scan does not have the read permission to the scanner
properties file cit.properties. Ensure that the administrator or root of the
computer on which the problem occurred has the read permissions to this file. By default, the file
is in the following directory.
|
| 51 | The scanner configuration file was not found. Reinstall or upgrade the scanner. For more information, see the following links. |
| 52 | Scanner internal error occurred. Gather scanner logs and
contact IBM Support. By default, the log files are in the following directory.
|
| 54 | The scan file cannot be compressed. Ensure that the administrator or root of
the computer on which the problem occurred has the read and write permissions to the following
directory.
|
| 56 | The scan output signature file cannot be created. Ensure that the
administrator or root of the computer on which the problem occurred has the read and write
permissions to the following directory.
|
| 57 | One of the following
environment variables is not set.
|
 123 |
The return code is applicable only to computers with the disconnected scanner.
It is not applicable to computers with the BigFix
client. The scan was interrupted because another software scan is in progress. Go to the computer
where the problem occurred and verify if any of the following processes is running:
|
| 125 | Memory allocation failed. Gather scanner logs and
contact IBM Support. By default, the log files are in the following directory.
|
| 255 | The return code is applicable only to computers with the disconnected scanner.
It is not applicable to computers with the BigFix
client. Scanner internal error occurred. Gather scanner logs and contact IBM Support. By default,
the log files are in the following directory.
|
Return codes greater than 128 or 256
Some return codes are triggered by problems that are signaled by the operating system.
These are the return codes greater than 128 in case of bash and 256 in case of ksh. To check what is
the system signal, use the following calculations: - For bash: return code - 128 = operating system signal
- For ksh: return code - 256 = operating system signal
The following table presents the list of the most common return
codes, their possible cause and solution.
| Return code | Signal | Possible cause and solution |
|---|---|---|
| 134 | 6 - SIGABRT | There might not be enough memory available for the process to work. Increase the memory limit
for this process by changing ulimit for data seg size: ulimit -d.
If the problem persists, contact IBM Support. |
| 138 | 10 - SIGBUS | There is not enough disk space on the computer. Free some disk space. If the problem persists, ensure that you use the latest version of the scanner. |
| 139 | 11 - SIGSEGV | There might not be enough memory available for the process to work. Increase the memory limit
for this process by changing ulimit for data seg size: ulimit -d.
If the problem persists, contact IBM Support. |