Resolve Job Status Errors¶
Introduction¶
A job status error may occur preventing a configuration assessment from completing. This guide explains the causes of various job status errors and how to troubleshoot them.
- An unknown error occurred
- An XML file was parsed, but contained an invalid signature
- SecureSuite encountered invalid assessment content
- An XML file was parsed but XML schema validation errors
- Could not parse an XML file required for assessment
An unknown error occurred¶
Potential Causes
- Username was incorrect
- Password was incorrect
- User does not have admin or
sudo
permissions - Wrong IP or domain name of system
- Unsupported Benchmark selected
Solutions
- Verify username and password and privilege to run scan on target system
- Verify SecureSuite log for more detail on error
- Only use the unchanged Benchmarks delivered with the application
An XML file was parsed but contained invalid signature¶
Potential Causes
The signature in the Benchmark file is not valid. By modifying the XCCDF (e.g., adding extra text the title of the Benchmark), the signature can be invalidated.
Solution
Only use the unchanged Benchmarks delivered with the application
SecureSuite encountered invalid assessment content¶
Potential Causes
- The Assessor parsed the assessment file requested to be run but could not determine what type of assessment it is for (e.g., Benchmark assessment).
- For configuration assessments, the root of the Benchmark file should be Benchmark or data-stream-collection.
- For OVAL definitions, the root of the file should be oval_definitions.
Solution
Only use the unchanged Benchmarks delivered with the application
An XML file was parsed but XML Schema validation errors¶
Potential Causes
An XML file has schema validation errors. This exit code is used when validating the schema for the Benchmark file requested to be run.
Solution
Only use the unchanged Benchmarks delivered with the application.
Could not parse an XML file required for assessment¶
Potential Causes
The assessment content (e.g., Benchmark file) contains XML formatting errors. For example, an end tag for an element does not match the start tag.
Solution
Only use the unchanged Benchmarks delivered with the application.
Contact CIS Product Technical Support¶
If you are encountering an issue that is not covered anywhere in the CIS SecureSuite Platform Guide, open a ticket with CIS Product Technical Support.
Please provide as much information as possible to expedite the support process.