000015159 - Status codes in RSA DLP Datacenter

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000015159
Applies ToRSA DLP Datacenter 8.x, 9.x
 
IssueMaking sense of Datacenter codes (status codes) from the "Scan History Details" page
Resolution

The Datacenter status codes are visible in the machine "Scan History Detail" page. You can get to the "Scan History Detail" page for individual machines, by logging into Enterprise Manager with a user having privileges to configure Datacenter. Go to Admin > Datacenter> From the left pane navigate and click the agent scan group > Select the History tab (for the agent scan group) and click on any machine within the scan group to view the "Scan History Details" for the machine. You will find entries only if scans have been run for the agent scan group.


Find below the list of Datacenter codes (Status codes) with explanations and possible causes:


Status Code 0 - Successful connection and scan
Status Code 7006 - Connection\Bootstrap failed
Possible Causes:
- Invalid Run As credentials
- Invalid credentials listed on Credentials page
-Agent Scan may already be in progress on target machine
-Orphaned agent installed on machine causes bootstrapping to fail
Status Code 7011 - Remote Machine Skip
Status Code 7051 - DNS lookup failure
Status Code 7052 - DNS lookup failure for localhost
Status Code 7100 - Administrative Access Denied (Can Ping Successfully)
Possible Causes:
- System is not on the Datacenter Domain (may need to use non domain credentials field and use machine\username format).
- Domain Admin Privileges are incorrect
Status Code 7101 - Host Unreachable
Possible Causes:
- System not turned on/no system assigned to IP.
- System not on the network (not pingable).
- System is not a member of the domain (may need to use non domain credentials field and use machine\username format).
- Firewall preventing access (check port 9150/might need to add in exclusion)
- Verify the user/credentials has admin rights to the remote server.
- Machine did not respond to a ping request in the allotted time, check for slow network response.
Status Code 7200 - Successfully connected, but could not create the service on machine.
Possible Cause:
- Verify the user/credentials has admin rights to the remote server.
Status Code 7300 - The machine was missing the required .NET Framework dependency
Possible Cause:
-System is missing .NET components (currently .net version 1.1)
Status Code 8000 - The machine timed out while processing.
Possible Causes:
Generally, this is due to the remote machine temporarily disconnecting from the network, the machine rebooted, or the remote process was terminated.
Status Code 8001 - The machine timed out while processing.
Possible Causes:
General cause is remote machine has shut down or has been taken off the network. Unable to ping this host.
Status Code 9000 - Restarting, Existing Agent Failure
Status Code 9001 - Disconnection Failure
Status Code 9014 - Named Pipe Creation Failure
Possible Cause:
See solution titled "Bootstrapping can fail if Symantec Anti-virus is installed on Enterprise or Site Coordinator (Named Pipe Error)"
Status Code 9016 - Unable to create service on target machine
Possible Causes:
Agent Scan may already be in progress on target machine
Invalid Credentials or Credentials without enough rights
Status Code 9017 - Attempting Connection
Status Code 9018 - Installing needed .Net version
Status Code 9019 - Boot Strap Completed
Status Code 9111 - User has Cancelled Scan

Legacy Article IDa40762

Attachments

    Outcomes