Error Messages

For Tenable Security Center API status codes, see the Tenable Security Center API Guide.

Note: Some errors are dependent on internal processes. If the error code you received is not listed, it may not indicate a specific Tenable Security Center error.

Scanning

For more information about creating, modifying, and launching scans, see Configure Scans.

For more information about statuses, see Tenable Nessus Scanner Statuses, Scan Result Statuses, and View Your Scan Zones.

Code	Message	Recommended Action
14	Progress handler has died.	Your system processes may be overloaded during the scan. Confirm your available system resources and re-run the scan.
14	Error creating Email notifying User '<username'> of Scan launch.	Do any of the following: Confirm the alert specifies one or more valid email addresses. For more information, see Email. Confirm the job queue database is not locked.
14	Error creating Email notifying User '<username>' of Scan completion.	Do any of the following: Confirm the alert specifies one or more valid email addresses. For more information, see Email. Confirm the job queue database is not locked.
60	Available Zones do not cover any accessible Scan IPs for Scan job #<jobIDorPID> ('<scanDefinitionName>' - #<scanDefinitionID>).	For troubleshooting assistance, see the knowledge base article.
62	No scanners ready to scan	The scan may be using incorrect or insufficient credentials, or another issue is blocking the scan. For troubleshooting assistance, see the knowledge base article.
64	Scan #<scanDefinitionID> is disabled.	You may have insufficient permissions to run the scan. For troubleshooting assistance, see the knowledge base article.
64	Scan Policy #<scanPolicyID> in Scan #<scanDefinitionID> is disabled.	You may have insufficient permissions to run the scan. For troubleshooting assistance, see the knowledge base article.
70	Unable to launch Scan progress process	Tenable Security Center is unable to fork the running scan process. You may need to raise the stack size for the tns user. Contact your system administrator for assistance.
102	Could not open '<nessusFile>' for writing.	Tenable Security Center may have insufficient disk space. Free up disk space in Tenable Security Center, as described in the knowledge base article.
106	Error getting contents of AuditFile '<auditFileName>' for Scan job #<scanJobID>.	Tenable Security Center cannot access the audit file definition. Do any of the following: Verify the specified audit file is valid. Create a new audit file to use with the scan. For more information, see Audit Files.
106	Error creating temp SCAP directory '<scapDir>'.	Tenable Security Center may have insufficient disk space. Free up disk space in Tenable Security Center, as described in the knowledge base article.
106	Error creating temp OVAL directory '<ovalDir>'.	Tenable Security Center may have insufficient disk space. Free up disk space in Tenable Security Center, as described in the knowledge base article.
106	Error creating temp directory '<tempDir>'.	Tenable Security Center may have insufficient disk space. Free up disk space in Tenable Security Center, as described in the knowledge base article.
106	Error untaring SCAP results file '<file>' (rc = $rc).	Tenable Security Center may have insufficient disk space. Free up disk space in Tenable Security Center, as described in the knowledge base article.
106	Error moving <type> result file '<curFile>' to '<newFile>'.	Tenable Security Center may have insufficient disk space. Free up disk space in Tenable Security Center, as described in the knowledge base article.
106	Unable to get current working directory.	Tenable Security Center may have insufficient disk space. Free up disk space in Tenable Security Center, as described in the knowledge base article.
106	Failed to change to the SCAP directory for zipping.	Tenable Security Center may have insufficient disk space. Free up disk space in Tenable Security Center, as described in the knowledge base article.
106	Error building SCAP results file '<scapFile>' (rc = <zipReturnCode>).	Tenable Security Center may have insufficient disk space. Free up disk space in Tenable Security Center, as described in the knowledge base article.
106	Failed to change back to originating directory.	Tenable Security Center may have insufficient disk space. Free up disk space in Tenable Security Center, as described in the knowledge base article.
106	Unable to get current working directory.	Tenable Security Center may have insufficient disk space. Free up disk space in Tenable Security Center, as described in the knowledge base article.
106	Failed to change to the OVAL directory for zipping.	Tenable Security Center may have insufficient disk space. Free up disk space in Tenable Security Center, as described in the knowledge base article.
106	Error building OVAL results file '$ovalFile' (rc = $rc).	Tenable Security Center may have insufficient disk space. Free up disk space in Tenable Security Center, as described in the knowledge base article.
106	Failed to change back to originating directory.	Tenable Security Center may have insufficient disk space. Free up disk space in Tenable Security Center, as described in the knowledge base article.
106	No results file found for Scan job #<jobIDorPID> ('<scanDefinitionName>' - #<scanDefinitionID>).	Tenable Security Center cannot locate /opt/sc/data/scans/#jobID/results.xml. Verify the following: /opt/sc/data/scans/#jobID/results.xml is in the correct directory. The tns user can access the file and directory.
106	Error creating new VDB directory for Scan job #<jobIDorPID> ('<scanDefinitionName>' - #<scanDefinitionID>).	Verify the tns user can access the following directory: /opt/sc/orgs/#orgID/VDB/#dateOfScan/.
106	Error moving results for Scan job #<jobIDorPID> ('<scanDefinitionName>' - #<scanDefinitionID>).	Verify the tns user can access the following directory: /opt/sc/orgs/#orgID/VDB/#dateOfScan/.
145	Error reading AuditFile '' for Scan job #<scanJobID>. Unable to retrieve AuditFile #<auditFileID>"	Add an audit file to the scan policy, then re-run the scan. For more information, see Audit Files and Scan Policies.
146	Unable to find template maps for Policy template #<policyTemplateID>.	Check for any errors with the last plugin update. If needed perform another plugin update. For more information, see Offline Plugin and Feed Updates for Tenable Security Center.
146	Diagnostic target is outside IPs of original Scan.	The scan target is not included in the scan configuration. If you want to include the target in the scan, update the scan settings and then re-run the scan.
146	Diagnostic target is not a single host.	The target of the diagnostic scan must be a single IP or FQDN. Update the scan configuration, then re-run the scan.
146	Zone Selection is locked but no Zone is specified.	You may have insufficient permissions to run the scan, or you may need to adjust your scan configuration. For troubleshooting assistance, see the knowledge base article.
146	Zone Selection is selectable but no Zone is specified.	You may have insufficient permissions to run the scan, or you may need to adjust your scan configuration. For troubleshooting assistance, see the knowledge base article.
146	Entered IPs and Assets are empty.	One or more scan targets do not exist in the selected import repository. For troubleshooting assistance, see the knowledge base article.
146	Scan IPs are restricted.	You may have insufficient permissions to run the scan, or you may need to adjust your scan configuration. For troubleshooting assistance, see the knowledge base article.
146	Scan IPs are not within your accessible range.	You may have insufficient permissions to run the scan, or you may need to adjust your scan configuration. For troubleshooting assistance, see the knowledge base article.
146	The number of Scan IPs is too large (more than 2^24 unique IPs).	Reduce the number of scan targets and re-run the scan.
147	Job #<scanJobID> not found.	Confirm the job queue database is not locked, then re-run the scan.
201	Error Setting up Scan database. <details>	Do any of the following, then re-run the scan: Confirm you have adequate disk space Confirm the tns user can access /opt/sc/data/scans/#jobID/
201	Error creating Scan database tables. <details>	Do any of the following, then re-run the scan: Confirm you have adequate disk space Confirm the tns user can access /opt/sc/data/scans/#jobID/ Confirm there are no corrupted databases
202	Error message varies.	Your system processes may be overloaded during the scan. Confirm your available system resources and re-run the scan. If the error persists, contact your Tenable representative.
400	Scan job #<scanJobID> stopped due to scanner inactivity.	Your system processes may be overloaded during the scan. Confirm your available system resources and re-run the scan.
65536	Failed to resolve <numFailed> scan target hostnames in Scan #job #<jobIDorPID> ('<scanDefinitionName>' - #<scanDefinitionID>)."	Tenable Security Center cannot resolve the specified scan target hostnames. For troubleshooting assistance, see the knowledge base article.
65536	Unable to scan <numRestrictedTargets> Restricted target<plural> in Scan job #<jobIDorPID> ('<scanDefinitionName>' - #<scanDefinitionID>).	You may have insufficient permissions to run the scan, or you may need to adjust your scan configuration. For troubleshooting assistance, see the knowledge base article.
65536	Unable to scan <numInaccessibleTargets> target(s) outside your accessible ranges in Scan #job #<jobIDorPID> ('<scanDefinitionName>' - #<scanDefinitionID>).	You may have insufficient permissions to run the scan, or you may need to adjust your scan configuration. For troubleshooting assistance, see the knowledge base article.
65536	Usable Zones fail to cover <unscannableCount> accessible Scan IP<plural> for Scan job #<jobIDorPID> ('<scanDefinitionName>' - #<scanDefinitionID>).	You may have insufficient permissions to run the scan, or you may need to adjust your scan configuration. For troubleshooting assistance, see the knowledge base article.
65536	Available Zones do not cover accessible Scan IPs for Scan job #<jobIDorPID> ('<scanDefinitionName>' - #<scanDefinitionID>).	You may have insufficient permissions to run the scan, or you may need to adjust your scan configuration. For troubleshooting assistance, see the knowledge base article.