Error Messages

For Tenable Security Center API status codes, see the Tenable Security Center API Guide. If Tenable Support asks you to collect debug data to troubleshoot a scan issue, see Collect Debug Data for Tenable Support.

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
6	DNS resolution failure	Do any of the following: Log into the Tenable Security Center CLI to verify that the nameservers in the /etc/resolv.conf file are correct and reachable. Confirm DNS resolution by running nslookup plugins.nessus.org or dig plugins.nessus.org. Ensure the server has outbound internet access or access to your local update mirror. For air-gapped environments, confirm you are following the offline update process rather than an automatic synchronization. If your environment requires a proxy, verify the web proxy settings in Tenable Security Center and confirm the proxy does not have DNS resolution issues. Verify that your firewall allows traffic on port 53 (UDP/TCP) for DNS queries and port 443 (HTTPS) for plugin downloads. If you use Tenable Core, log into the management interface and confirm that the operating system applies the DNS settings correctly.
7	pluginSync; id: -1	Tenable Security Center may have insufficient disk space. Free up disk space in Tenable Security Center, as described in the knowledge base article.
7	Error on file upload	Tenable Security Center may have insufficient disk space. Free up disk space in Tenable Security Center, as described in the knowledge base article.
10	No module	The requested API module does not exist. Verify the request URL path is correct and the module name is valid for this version of Tenable Security Center.
11	No action	The requested action within the module is not recognized. Check the API endpoint and HTTP method against the Tenable Security Center API Guide.
12	Bad token	The session token is invalid or expired. Re-authenticate to obtain a new session token.
13	Bad JSON	The request body contains malformed JSON. Validate the JSON payload structure before sending. Check for unescaped characters or truncated payloads.
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.
15	Undefined error	An undefined error occurred. Check system logs at /opt/sc/admin/logs/ for more details. If the error persists, contact Tenable Support.
16	The scanner is not currently in a working state.	The application cannot write to the temporary directory. Verify that the tns user has Read/Write permissions for /opt/sc/admin/tmp and /opt/sc/data.
16	Permission Denied	The application cannot write to the temporary directory. Verify that the tns user has Read/Write permissions for /opt/sc/admin/tmp and /opt/sc/data.
20	License exceeded	The number of licensed IPs or assets has been exceeded. Review asset counts under System > License. Remove excess assets or contact Tenable to upgrade the license.
32	Broken Pipe (EPIPE) error	Confirm that the Maximum Transmission Unit (MTU) settings are consistent across your network path (for example, 1500). Review firewall logs for TCP sessions that timed out and closed during large report exports.
44	The product associated with this action does not have a valid activation code.	Navigate to System > Configuration > License and verify that the activation codes for your Tenable products are marked as Valid. If a code is invalid or missing, enter a valid activation code and click Register or Reset Activation Code.
60	Available Zones do not cover any accessible Scan IPs for Scan job #<jobIDorPID> ('<scanDefinitionName>' - #<scanDefinitionID>).	For troubleshooting assistance, see the knowledge base article.
61	Not configured	The requested resource or subsystem has not been configured. Complete the required configuration (for example, scanner setup or repository creation) before attempting this operation.
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.
63	Denied	The operation was denied, typically because it was attempted during a scan blackout window. Wait for the blackout window to end or adjust the blackout schedule under Scan Zones. For more information, see Scan Zones.
65	Expired	The license or session has expired. Renew the license under System > Configuration > License, or re-authenticate to start a new session.
66	Re-registration required	The system requires re-registration. Navigate to System > Configuration > License and re-register the activation code. This may occur after a major version upgrade or host change.
67	Connection error	Failed to establish a connection to the target service. Check network connectivity and firewall rules, and verify that the target service is running.
68	Stopped	The process or scan was stopped. If unexpected, check system logs for out-of-memory kills or resource exhaustion events.
69	Error message varies.	Verify that the Tenable Nessus service is running on the scanner by running service nessusd status. Check the network connectivity between Tenable Security Center and the scanner on port 8834. Confirm that no intermediate firewalls or Intrusion Prevention Systems (IPS) are dropping connection packets.
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.
71	License error	The license is invalid or cannot be validated. Navigate to System > Configuration > License to verify the license. If the issue persists, contact Tenable Support.
72	Evaluation license error	Your evaluation period has ended. Contact your Tenable representative to transition to a production license.
73	Cannot signal process	The application failed to communicate with a backend service. Restart Tenable Security Center with the following command: Copy `# /bin/systemctl restart SecurityCenter`
74	Authentication failure	Authentication credentials are invalid. Verify your username and password. For LDAP or SAML users, check the status of the external authentication provider.
75	Locking error	A database or resource lock conflict occurred. Retry the operation after a brief delay. If the issue persists, check for stuck processes holding locks and restart Tenable Security Center.
101	File read error	Unable to read the specified file. Check file permissions and verify the file exists. Ensure the tns user has read access to the file path.
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.
103	File format error	The uploaded or processed file has an invalid format. Verify the file type matches what the system expects (for example, .nessus, .xml, or .csv).
104	Missing file	A required file was not found at the expected location. Verify the referenced file has not been moved or deleted.
105	File open error	Unable to open the file. Verify the file is not locked by another process, the path is valid, and the tns user has appropriate permissions.
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/.
107	Upload error	File upload failed. Check available disk space, verify the file size does not exceed server limits, and ensure the upload directory is writable by the tns user.
108	File copy error	Unable to copy the file to the destination. Verify both source and destination directories exist and are accessible, and check available disk space.
109	File rename error	Unable to rename or move the file. Verify the tns user has write permissions to both locations.
110	File already exists	A file with the same name already exists at the target location. Rename the new file or remove the existing one before retrying.
128	Process Execution Error	Review the job.log file for the specific task ID to identify which binary or script failed. Verify that all backend dependencies (for example, rsync, PHP, or OpenSSL) are correctly installed and in the system path.
141	Unexpected data	The server received data it did not expect. Verify the request payload matches the API specification. Check for version mismatches between the UI and backend.
142	Missing required input	A required field was not provided. Check the form for missing required fields, which are typically marked with an asterisk in the UI.
143	Invalid filter	The filter criteria specified are not valid. Check filter syntax and ensure referenced fields exist.
144	Name already exists	An object with the specified name already exists. Choose a unique name for the resource being created or renamed.
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.
147	Scan progress process terminated abnormally with error status '<signalNumber>'	You may have insufficient permissions to run the scan, or you may need to adjust your scan configuration.
148	Resource already exists	The resource being created already exists. Use an update operation instead, or delete the existing resource first.
149	Invalid arguments	One or more arguments provided are invalid. Check the data types, value ranges, and format of all parameters.
150	Invalid options	The specified options are not valid for this operation. Review available options and correct any unsupported values.
151	Missing arguments	Required arguments were not supplied. Verify the complete request URL and parameters.
152	Missing options	Required options were not specified. Check the Tenable Security Center API Guide for mandatory option parameters.
155	You do not have the required 'Manage Roles' permission to migrate objects during user deletion.	To migrate a user's objects during account deletion, ensure your user role has the Manage Roles permission enabled. If you do not have this permission, contact your Security Manager or Administrator to perform the deletion or update your role permissions.
161	Invalid credentials	Login credentials are invalid. Verify your username and password. For LDAP or SAML users, check the status of the external authentication provider.
162	Invalid user object	The user object is malformed or corrupted. Verify the user record is intact or recreate the user account.
163	No permission	The current user lacks the required permission for this operation. Contact your administrator to grant the required role permissions. For more information, see User Roles.
164	Not expanded	The object has not been fully loaded. Fetch the full object before attempting this operation and retry.
171	LDAP error	An error occurred communicating with the LDAP server. Verify LDAP server connectivity, check bind credentials, and confirm the LDAP configuration is correct. Test the connection from System > Configuration > LDAP.
181	SAML error	A SAML authentication or configuration error occurred. Verify the SAML IdP metadata, certificate validity, assertion consumer service URL, and clock synchronization between Tenable Security Center and the IdP.
190	Feature not active	The requested feature is not enabled in the current license or configuration. Check license entitlements under System > License.
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
201	Error: Search for CVE failed. Postgres is not currently operational.	There was a problem communicating with the PostgreSQL server. To use global search when your Tenable Security Center has more than 100,000 assets, you must connect an external PostgreSQL server. If your Tenable Security Center has fewer than 100,000 assets, please open a case with Tenable Support.
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.
203	Database busy	The database is currently locked by another operation. Wait for the current operation to complete and retry. Consider enabling write-ahead logging (WAL) journaling mode for SQLite databases to reduce locking conflicts.
255	Exit Failure	If the issue occurs during a scan, verify the scanning credentials and confirm that the target does not block the scanner IP address after multiple login attempts. Review the /var/log/messages file for Out of Memory (OOM) Killer events to determine if the server requires additional RAM.
300	Cannot parse XML	The XML data is corrupted or improperly formatted. Validate the source of the XML file.
351	JSON parse error	The system received malformed JSON data. Validate the JSON syntax before sending. Check for truncated responses or encoding issues.
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. If the error persists, contact your Tenable representative.
401	Communication error	Unable to communicate with the backend service. Refresh the page. If the error persists, verify that Tenable Security Center services are running.
404	Scan result not found.	This error can occur if the scan result was deleted or if the database is currently indexing. Wait a few minutes and refresh the Scan Results page. If the issue persists, verify the scan was not manually deleted by another user.
500	Unexpected Response	A 500 error indicates an internal server error, typically related to the PHP memory limit or a database timeout. Refresh the browser page. If the error persists, navigate to System > System Logs to find the specific PHP or SQL error. If the logs indicate memory exhaustion, increase the PHP Memory Limit in your server configuration.
2061	Repository database error	The repository associated with the scan encountered a database lock or corruption. Remove database locks or repair the corrupted repository. To prevent database locks from multiple users operating simultaneously, enable write-ahead logging (WAL) journaling mode in your databases.
12582	Job Queue Timeout	The requested task timed out in the job queue. Reduce the scan target size or enable Scan targets with multiple domain names in parallel in the scan policy options.
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.
0xC000006E	Account Restriction	The Windows target rejected the credentials due to an account restriction, such as "User must change password at next logon" or logon hour restrictions. Update the account settings on the target and re-run the scan.

Reporting

Message	Description	Recommended Action
Execution of report is not permitted	This can occur if you do not have permissions for the repository or asset used in the report.	Ensure the report creator has shared the report with your group.
Error executing ReportSource Query. Scan Result #<scanResultID> does not exist.	The report cannot find the specific scan data required to generate the output. This usually occurs if a scan result was deleted or expired before the report finished processing.	Verify that the scan results referenced in the report definition still exist in Tenable Security Center. If the results were deleted, update the report's Source settings to point to active scan data.
Error getting DataSource #<scanJobID> for Report Source.	Tenable Security Center failed to retrieve information from a specific data source linked to the report, often due to a missing scan result or a database inconsistency.	Ensure all data sources and repositories linked to the report are available. If the error persists, check the health of the specific Scan Result ID mentioned in the logs.
An error occurred when building the vuln query command.	The system was unable to construct the backend query necessary to pull vulnerability data for the report.	Check the filters applied to the report or report element. Simplify any overly complex query filters or ensure that the user running the report has the appropriate permissions to access the targeted repositories.

Other Errors

Message	Recommended Action
Error loading compliance plugin	This error indicates the plugin is missing from the local database. Navigate to System > Configuration > Plugins/Feed and click Update for the Active Plugins feed.
Operation aborted by callback	If a managed Tenable Nessus scanner fails to synchronize plugins and displays a callback error, perform the following steps to force a manual synchronization: Log in to Tenable Security Center as an Administrator. Navigate to Resources > Nessus Scanners. Select the checkbox for the affected scanner. Click Edit. Without changing any settings, click Submit to re-initialize the connection and trigger a fresh plugin push. If that does not resolve the issue, navigate to System > Configuration > Plugins/Feed and click Update for the Active Plugins feed. Additionally, verify that the network firewall allows persistent communication on port 8834 between Tenable Security Center and the managed scanner. Ensure that either Tenable Security Center or Tenable Nessus is managing the plugins, not both.
Error importing sc-vprdata.json into sc-vprdata.db	Ensure that the binutils and sqlite packages are installed and updated to the latest versions supported by your version of RHEL, as these are required for database indexing. Confirm that the tns user has full Read/Write permissions for the /opt/sc/data/feed./ directory. If that does not resolve the issue, navigate to System* > Configuration > Plugins/Feed and click Update for each plugin feed.
No such table : main.message	If you encounter this error while installing Tenable Security Center, perform the following steps: Ensure the partition hosting /opt/sc has enough free space for the initial database population, as insufficient space can cause table creation to fail. Confirm that the tns user and group have full ownership of the /opt/sc directory and all subdirectories. Incorrect permissions often prevent the installer from writing to the SQLite master files. If the error persists, review the log file located at /opt/sc/admin/logs/install.log to identify if a specific library is missing or failing.