Scan Statuses
Each scan gets assigned a status to provide information on its current state. You can view the status of any scan by selecting Scans > Scan Activity, and then selecting the desired scan. The scan's status appears under General Information.
If you received notification that there was a problem with your scan, or you notice a scan in the Scan Activity page with an error, you can view the error type under Scan Status Details to determine next steps. See ERRORED for more information.
BLACKOUT
The scan is currently paused as a result of a blackout window configured in the RNA profile.
CANCELING
Fortra VM is attempting to cancel the scan on the RNA. If the RNA is offline or otherwise in a bad state, this may take some time to complete.
CANCELED
The scan was canceled on the RNA.
ERRORED
Scan does not have a scanner
FVM has determined that there is no scanner assigned to this scan.
Solution: Correct the scanner and scan again.
Scan could not launch
The RNA was offline at the time of the scan.
Solution: Ensure adequate power to the RNA and reboot before running the scan again.
Launching scan
The RNA may have been in an state of error at the time of the scan.
Solution: Reboot the RNA and run the scan again.
RNA ERROR: SCAN DID NOT COMPLETE ON THE RNA
Only partial scan results are produced because the scan failed on the RNA. Contact your Client Advocate for support.
Solution: Run the scan again after support investigation is complete.
FAILED INSERT SCAN CHUNK AFTER _ ATTEMPTS
This indicates that one of the partial result sets sent back to Fortra VM could not be inserted into the database, resulting in a scan error. Contact your Client Advocate for support and further investigation.
Solution: Run the scan again after the investigation is complete.
ScanExceededContractLimits: Scan exceeds hard limits
This scan does not meet the limits defined in the service subscription.
Solution: Change the parameters of the scan to operate within the scope of your subscribed services.
RNA Error: Scan results could not transfer back to FVM.
This scan is no longer running on the RNA.
Solution: Reboot the RNA and attempt the scan again.
RNA Error: Scan did not complete on the RNA.
The scan died on the RNA. This sort of scan interruption occurs when the RNA reboots during a scan or the RNA is short on memory space.
Solution: Lower the chunk size for the scan by altering the scan policy can help resolve a memory issue. You can also reduce the number of scans running concurrently on the RNA. For those running large scale scans it is recommended to assign more RAM to the RNA.
Inserting scan attempt 2
The scan failed to insert in Fortra VM, but it did complete on the RNA.
Solution: Contact your Client Advocate for support. It is possible that the scan data can be re-inserted in Fortra VM.
Scan is loading
The scan failed to insert in Fortra VM, but it did complete on the RNA.
Solution: Contact your Client Advocate for support. It is possible that the scan data can be re-inserted in Fortra VM.
LAUNCHING
Fortra VM is attempting to launch the scan on the RNA.
PAUSING
A request to pause the scan was manually made in Fortra VM. Once the scan is actually paused, the status will change to PAUSED.
PAUSED
The scan is currently paused on the RNA.
QUEUED
The scan is currently queued on the RNA. Once a free scan slot is available, the scan will move up in the queue in the order it arrived on the RNA until it can eventually run.
RESUMING
Fortra VM is attempting to contact the RNA to resume a manually paused scan.
RUNNING
The scan is currently running on the RNA.