0xe00086cc Backup Exec
The media server cannot resolve the IP address of the remote agent correctly. Step-by-Step Troubleshooting Guide 1. Restart Remote Services The simplest fix is often the most effective. Log into the target server (the one being backed up). Open services.msc . Locate Backup Exec Remote Agent for Windows . Restart the service. Ensure the service is set to Automatic . 2. Verify Port 10000 Availability Backup Exec uses port 10000 for NDMP communication. Run telnet [ServerIP] 10000 from the media server. If the screen goes blank, the port is open.
If you observe that error 0xe00086cc appears after prolonged uptime, consider scheduling weekly or bi‑weekly restarts of Backup Exec services during maintenance windows to clear any accumulated state issues.
0xe00086cc in Backup Exec typically indicates an "Access Denied"
Open Backup Exec and navigate to > Logon Accounts > Manage Logon Accounts .
: The account used for the backup job is locked in Active Directory, disabled, or has an expired password. 0xe00086cc backup exec
Aggressive Endpoint Detection and Response (EDR) suites can intercept the backend data streams running across the default Network Data Management Protocol (NDMP) TCP port 10000, misinterpreting the remote agent's read commands as an unauthorized access attempt. Comprehensive Step-by-Step Resolution Guide
If the above steps do not resolve the issue, you can try the following additional troubleshooting steps:
The Backup Exec hex error code (often tied to Veritas status code V-79-57344-34508 ) is a specific hex error code that signals a critical Access Denied or Trust Relationship failure between the primary Media Server and a targeted remote agent.
It looks like you're encountering the error (often associated with 0xe00086ce or similar codes) while trying to install or use a Veritas Backup Exec Remote Agent . The media server cannot resolve the IP address
Are you experiencing issues with your Backup Exec software, specifically encountering the error code 0xe00086cc? This error can be frustrating, especially if you're relying on Backup Exec to protect your critical data. In this article, we'll explore what the error 0xe00086cc means, its possible causes, and most importantly, provide you with step-by-step guide on how to fix it.
When upgrading Backup Exec, plan a rollout that updates remote agents promptly after the central server upgrade. While Backup Exec supports rolling upgrades where older agents can continue functioning, warnings will appear in job logs, and prolonged version mismatches increase the risk of connection failures.
: Misconfiguration in Backup Exec, such as incorrect settings for the backup job, can also lead to this error.
When a Backup Exec job fails with this specific error, users often see a message like "The Backup Exec job engine system service is not responding". On many systems, this failure is accompanied by an entry in the Windows Event Log with Event ID 57860. Log into the target server (the one being backed up)
Document the Backup Exec System Logon Account and any related service accounts. When domain passwords expire or are changed, update the stored credentials in Backup Exec immediately rather than waiting for backup jobs to fail.
Reboot and re-test.
This error is often labeled as "A failure occurred while establishing a connection to the Remote Agent." It is a generic communication fault that points to networking, authentication, or service-level hang-ups. Top Causes for the Error
The Backup Exec error code typically surfaces during the installation or upgrade of the Remote Agent for Windows (RAWS) . This error generally indicates a compatibility or environment conflict, often occurring when the Backup Exec server attempts to push an agent to a remote machine that has a mismatched or corrupt previous installation. Common Causes of Error 0xe00086cc
Database-level components (such as Microsoft Exchange or SQL Server instances) lack proper administrative impersonation attributes.
An outdated remote agent is the most frequent culprit behind this error. Open the Backup Exec console on your main media server. Navigate to the tab.