Disconnected scanner return codes

Edit online

If the disconnected scanner experiences a problem, an error code that indicates the reason of failure is returned. Check what is the possible cause of the failure that is indicated by each code and how to solve the problem.

Return code is an indication of a problem encountered. To see details of the issue and try to resolve it yourself, you can check the more detailed information in the disconnected scanner log files. For more information, see: Troubleshooting discovery by disconnected scanner (disconnected scenario).

Table 1. Disconnected scanner return codes

Return code Possible cause and solutions
123
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:
  • wscansw
  • wscanfs
Gather scanner logs and contact IBM Support. By default, the log files are in the following directory.
  • UNIX <disconnected_scanner_install_dir>/logs
  • Windows <disconnected_scanner_install_dir>\logs
200 Setup of the disconnected scanner was run by a user account that does not have root or administrative privileges.
201 Incorrect parameters were passed to the disconnected scanner script. For example, you cannot use -noschedule parameter on Linux. For more information, see: Installing the disconnected scanner and gathering scan results (disconnected scenario).
202 Incorrect installation path. For example, the installation path on UNIX cannot contain white space characters. For more information, see: Downloading the disconnected scanner package (disconnected scenario).
203 The integrity check of the extracted disconnected scanner installation package failed. Manually extract the installation package and ensure the extraction was complete.
204 Incorrect values were provided for parameters in the setup_config.ini file. For more information, see: Configuration parameters of the disconnected scanner (disconnected scenario).
205 Creation of a folder or a file failed during the setup of the disconnected scanner. See the console output and log files for details.
206 Scanner installation failed. See scanner log files for more details about the reason of the failure.
207 Scanner is not installed. A disconnected scanner script was run without running the setup script first. Install the disconnected scanner by running the setup script. For more information, see: Installing the disconnected scanner and gathering scan results (disconnected scenario).
208 A 32-bit console is used on a 64-bit system.
209 Scheduling a disconnected scanner task failed. Run the setup script again. If the problem persists, contact IBM Support.
211 Error occurred during API token encryption. It is caused because the scanner version is incompatible with the installed disconnected scanner or because the endpoint_id.txt file could not be located. Re-install the disconnected scanner.
212 An error occurred during API token decryption. See scanner log files for more details about the reason of the failure. It is caused by one of the following reasons:
  • The obfuscated token value was corrupted in the setup_config.ini file. Provide the token in plain text in the following parameter in the setup_config.ini file. It will be automatically obfuscated during the next run.
    • For application update 9.2.41 and earlier: LMT_SERVER_API_TOKEN
    • For application update 9.2.42 and later: DATA_UPLOAD_TOKEN
  • Scanner version is incompatible with the installed disconnected scanner or the endpoint_id.txt file could not be located. Re-install the disconnected scanner.
213
Connection test to the License Metric Tool server or the Scans Relay failed. One of the following parameters was defined, but the other one is missing.
  • For application update 9.2.41 and earlier: LMT_SERVER_URL or LMT_SERVER_API_TOKEN
  • For application update 9.2.42 and later: DATA_UPLOAD_URL or DATA_UPLOAD_TOKEN
Both parameters should be either defined or not defined. For more information, see: Configuration parameters of the disconnected scanner (disconnected scenario).
214 Connection test to the License Metric Tool server or the Scans Relay failed. Incorrect value of the CURL_PATH parameter was provided or cURL is not installed. Correct the value or install cURL on the computer. For more information, see: Configuration parameters of the disconnected scanner (disconnected scenario).
215 Connection test to the License Metric Tool server or the Scans Relay failed. Incorrect value of the CURL_PARAMETERS parameter was provided. Correct the value. For more information, see: Configuration parameters of the disconnected scanner (disconnected scenario).
216
Connection test to the License Metric Tool server or the Scans Relay failed. Incorrect value was provided in the following parameter.
  • For application update 9.2.41 and earlier: LMT_SERVER_API_TOKEN
  • For application update 9.2.42 and later: DATA_UPLOAD_TOKEN
Correct the value. For more information, see: Configuration parameters of the disconnected scanner (disconnected scenario).
217
Connection test to the License Metric Tool server or the Scans Relay failed. The License Metric Tool user whose token was provided in the following parameter does not have the permission to upload packages with disconnected scan results.
  • For application update 9.2.41 and earlier: LMT_SERVER_API_TOKEN
  • For application update 9.2.42 and later: DATA_UPLOAD_TOKEN
Add the Manage Scan Uploads permission to the user's role or use the token of a different user.
218
Connection test to the License Metric Tool server or the Scans Relay failed. Incorrect value was provided for the following parameter.
  • For application update 9.2.41 and earlier: LMT_SERVER_URL
  • For application update 9.2.42 and later: DATA_UPLOAD_URL
Correct the value. For more information, see: Configuration parameters of the disconnected scanner (disconnected scenario).
219 Connection test to the License Metric Tool server or the Scans Relay failed. Check the disconnected scanner logs to see the details of the failure. For more information, see: Troubleshooting discovery by disconnected scanner (disconnected scenario).
220 Format of the upload file name is incorrect. Ensure that the output directory of the disconnected scanner does not contain extraneous files. For more information about disconnected scanner output directory, see: Configuration parameters of the disconnected scanner (disconnected scenario).
221 Connection test to the License Metric Tool server or the Scans Relay failed. Upload file size is too large. Contact IBM Support.
222 Connection test to the License Metric Tool server or the Scans Relay failed. An unexpected error occurred. Contact IBM Support.
224 Unable to execute the PowerShell script on Windows. Bookcase verify Windows PowerShell execution policy.
225 Hardware scan failed. For more information about the possible reasons of a failed hardware scan, see: Capacity scan return codes.
226 Catalog scan failed. For more information about the possible reasons of a failed software scan, see: Software scan return codes.
227 ISO tag scan failed. For more information about the possible reasons of a failed software scan, see: Software scan return codes.
228 SLM tag scan failed. For more information about the possible reasons of a failed software scan, see: Software scan return codes.
229 Virtualization host scan failed. See scanner log files for more details about the reason of the failure.
230 Docker scan failed. See scanner log files for more details about the reason of the failure.
231 Failed to process results of the hardware scan. See scanner log files for more details about the reason of the failure.
232 Failed to process results of the ISO tag scan. See scanner log files for more details about the reason of the failure.
233 Failed to process results of the SLM tag scan. See scanner log files for more details about the reason of the failure.
234 Scanner error. Run the scanning script again. If the problem persists, then contact IBM Support.
235 Failed to pack scan results. See scanner log files for more details about the reason of the failure.
236 Failed to check whether a new version of the disconnected scanner is available. See scanner log files for more details about the reason of the failure.
237 Failed to download the disconnected scanner package for upgrade. See scanner log files for more details about the reason of the failure.
238 Failed to determine the name of the downloaded file due to an unexpected error. Contact IBM Support.
239 Failed to rename the downloaded file from its temporary name. See scanner log files for more details about the reason of the failure.
255 Windows system error occurred during the scan. Run the scanning script again. If the problem persists, then contact IBM Support.
Table 2. Return codes from the Install Disconnected Scanner on Windows and Install Disconnected Scanner on Unix tasks

Return code Possible cause and solutions

101

 The directory provided as the installation path exists and is not empty. Change the installation path. For more information, see: Installing disconnected scanner by using a task.

102

 Creating the installation directory failed. Contact IBM Support.

103

 There is not enough free disk space to complete the disconnected scanner installation. Add more disk space or change the installation path. For more information, see: Installing disconnected scanner by using a task.

104

 Extraction of the disconnected scanner installation package failed. Contact IBM Support.