Troubleshoot Scan Jobs

Each target in a Scan job’s results reports a status. Use this reference to identify the cause and the required action.

Connection and Credential Issues

Status	Cause	Action
NoAnswer	The target is unreachable.	Check the scope and firewalls, and confirm the device is powered on.
NoConnection	The target responds to ping, but none of the required ports are open.	Check firewall ports — see Network prerequisites for scanning.
ConnectionTimedOut	The login timed out.	Confirm the connection is reachable manually and not blocked by antivirus software or a firewall.
DNSResolutionFailed	The target hostname in the scope couldn’t be resolved to an IP address.	Check DNS resolution from the appliance.
CredentialFailed	Authentication failed with the provided credential.	Check the credential — see Credential and access prerequisites.
NoCredential	The target and its type were identified, but no matching credential exists in the scan job.	Add the required credential to a keychain used by the scan job.
CredentialNoLongerWorks	A credential that previously worked has stopped working.	Check and update the credential.
LockedAccount	Too many authentication failures locked the account.	Confirm the credential is correct and assigned to the right scan job; unlock the account on the target if needed.
InsufficientPrivilege	The credential can’t run the commands needed to generate a durable unique identifier.	Check the credential’s privileges — see Credential and access prerequisites.
UnusableConnection	The connection succeeded, but required services (for example RPC) are missing on the target.	Check firewalls and target health. For Windows, confirm access to WMI, Remote Registry, RPC, and the SMB (C$) share.

Scan Completion Issues

Status	Cause	Action
PartialScan	Connected with sufficient privileges and a trustable identifier, but some data (disks, filesystems, processes, connections) wasn’t collected. Application scan failures can also cause this.	Check logs for the specific step that failed.
ScanFailure	An unrecoverable or unexpected error, an untrustable identifier, missing key configuration items, or a timed-out/aborted scan.	Check logs.
ConnectionFailed	An unexpected connection error, distinct from a credential or privilege failure.	Check logs.
Aborted	The scan was aborted.	Check logs.
NoResult	No scan result was received for this target.	Check logs.
Unknown	An unexpected condition occurred.	Check logs.

Skipped Targets

Status	Cause
SkippedAsSameAs	This target was already scanned in the same scan job via a different IP.
SkippedAsExcluded	The target is in an exclusion scope for this scan job.
SkippedAsWorkStation	The target’s OS was identified as a workstation edition.

Skipped targets require no action.

Diagnosing a Specific Target

For deeper detail on any target, open its Scan Info link in the Scan Status view. Common diagnostic messages include:

Message	Meaning	Action
Failed to gather process connections	An OS command couldn’t list local-to-remote process connections, used for dependency mapping.	Check the credential’s permission to run netstat on *nix machines.
Truncated process command line	The OS limited how much of a process’s command line could be returned, so the executable couldn’t be fully identified.	No action — this is an OS limitation.
dmidecode command not available	The scan couldn’t uniquely identify the server without this command.	Check the credential’s permission to run dmidecode; install the package if it’s optional on that OS.
Failed to gather identifier	No available command could establish a unique identifier for the target.	Check the credential’s permissions for identity commands; contact support to identify which command is failing.
SELECT SERIALNUMBER FROM Win32_BIOS failed	The WMI command used to uniquely identify the server didn’t return a result.	Check the credential’s permission to run this command over WMI.