0xe00086cc Backup Exec -
If the error persists, gather logs for Veritas support:
Error 0xe00086cc is almost never about a actually missing file. It is a VSS communication failure. Stop searching your drive for "missing file.txt" and start focusing on the integrity of the Volume Shadow Copy service on the target machine.
Have you conquered this error with a different trick? Let me know in the comments below!
Disclaimer: Backup Exec is a product of Veritas Technologies. Always test fixes in a non-production environment first. This post refers to Backup Exec versions 16 through 22. For 2010/2012 versions, the solution usually requires upgrading the remote agent.
The error 0xe00086cc in Veritas Backup Exec typically points to an "Access Denied" failure. This often occurs when the Backup Exec engine cannot authenticate or communicate with a remote server, such as a SQL instance or a Windows agent. The Story of Error 0xe00086cc: The Failed Handshake
Imagine a backup job as a late-night courier (the Backup Exec Server) arriving at a high-security warehouse (your Remote Server). The courier has a manifest to pick up data, but when they reach the gate, they are turned away. This "Access Denied" story usually unfolds in one of these ways:
1. The Invalid ID (Credential Mismatch)The courier is using an old ID card. In Backup Exec terms, the Logon Account used for the job might have an outdated password, or it may not have the right to "Log on as a batch job" or "Log on as a service" on the remote machine.
2. The Guard Doesn’t Recognize the Courier (Trust Issues)In newer versions of Backup Exec, the server and the remote machine must "trust" each other. If this trust relationship hasn't been established, the remote server ignores the backup request. You can fix this by right-clicking the server in the Backup and Restore tab and selecting Establish Trust.
3. The Gate is Locked (Firewalls & WMI)The courier can’t even get to the gate because it's locked. Firewalls often block the communication ports (like NDMP port 10000) or WMI (Windows Management Instrumentation) services needed for the "push" installation or initial connection. How to Fix the "Access Denied" Plot Twist Solved: Backup exec access is denied - Experts Exchange
The Backup Exec error code 0xe00086cc 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
Understanding the root cause is the first step toward a resolution. The most frequent triggers include:
Unsupported Upgrade Paths: The version of the agent already on the target computer may be too old to be directly upgraded by your current version of Backup Exec.
Corrupt Installation Files: Residual files from a failed or partial uninstallation can block new installation attempts.
Security & Permissions: Insufficient local administrator rights or restrictive firewall settings (blocking WMI or NDMP ports) can prevent the push installation from completing.
Environmental Conflicts: Third-party applications, such as antivirus software or other backup agents, may be locking files required for the Backup Exec installation. Step-by-Step Troubleshooting Guide 1. Perform a Manual Uninstallation
If a push installation fails with this error, the most effective fix is to manually clean the target machine. Log into the remote server directly.
Use Add/Remove Programs to uninstall any existing Backup Exec Remote Agent.
If the standard uninstall fails, you may need to manually remove the installation folder (typically located in C:\Program Files\Veritas\Backup Exec\RAWS) and clear related registry keys under HKLM\Software\Veritas or HKLM\Software\Symantec. 2. Verify Service Account and Permissions
Ensure the account you are using for the installation has full administrative control.
Confirm that the Backup Exec Service Account (BESA) is not locked out in Active Directory.
Verify that the account has Full Control over the target installation directories.
Check that the Remote Registry service is started on the target machine. 3. Check Network Connectivity and Ports
Backup Exec relies on specific ports to communicate with its agents.
WMI and NDMP: Ensure Windows Management Instrumentation (WMI) is enabled and not blocked by a firewall.
Port 10000: This is the default port for the Network Data Management Protocol (NDMP) used by Backup Exec. Ensure it is not being used by another application. 4. Run a Manual Agent Installation
If push installation continues to fail, bypass the media server's push mechanism.
Copy the agent installation files (found on the media server in the Agents folder) directly to the remote server. Run setup.exe locally as an Administrator. 5. Establish Trust Relationships
For modern versions of Backup Exec, a security trust must be established. Solved: Backup exec access is denied - Experts Exchange
The Backup Exec error 0xe00086cc is a common security-related failure typically accompanied by the message "Access Denied". It most frequently occurs when the Backup Exec server attempts to communicate with a remote computer (like a SQL Instance) without the proper authorization or credentials. Core Causes of Error 0xe00086cc
The underlying issue is almost always a failure in the authentication handshake between the Backup Exec Media Server and the target Remote Agent. Specific triggers include: 0xe00086cc backup exec
Credential Mismatch: The Backup Exec Service Account (BESA) or the System Logon Account has incorrect or outdated credentials compared to what the remote resource requires.
Locked or Disabled Accounts: The account used for the backup job is locked in Active Directory, disabled, or has an expired password.
Missing Local Admin Rights: The account assigned to the Backup Exec services lacks "Local Administrator" privileges on the target remote server.
Lack of Established Trust: A manual trust relationship has not been established between the Media Server and the Remote Agent. Comprehensive Troubleshooting Steps 1. Verify and Update Logon Accounts
Ensure the Backup Exec services are using valid credentials that match the target environment.
In the Backup Exec console, navigate to Configuration and Settings > Logon Accounts > Manage Logon Accounts.
Verify that a System Logon Account exists and is set as the default.
If the credentials have changed recently, select the account, click Edit, and re-enter the correct password. 2. Check Backup Exec Service Account (BESA) Permissions
The account running the services must have specific rights to function.
Local Admin Group: Confirm the account is a member of the Local Administrators group on both the Media Server and the remote resource.
Active Directory Status: Check Active Directory Users and Computers to ensure the account is not locked out or disabled.
Rights Verification: You can run gpresult /Z from a command prompt on the server to verify the account has all necessary rights. 3. Establish Manual Trust
If the "Access Denied" error occurs during a backup attempt of a newly added server:
Go to the Backup and Restore tab in the Backup Exec console. Right-click the remote server that is failing.
Select Establish Trust to manually verify the security connection. 4. Configure Remote Agent Services Solved: Backup exec access is denied - Experts Exchange
It looks like you're encountering the error 0xe00086cc (often associated with 0xe00086ce or similar codes) while trying to install or use a Veritas Backup Exec Remote Agent.
While the error itself is frustrating, user reviews of Veritas Backup Exec generally highlight its reliability once configured, though they note that its complexity can lead to cryptic error codes like the one you're seeing. Positive Highlights from User Reviews
Despite setup hurdles, long-term users and IT professionals often rate Backup Exec highly (averaging 7.8/10 to 9.5/10 on sites like PeerSpot) for the following reasons:
Granular Recovery: Users on Software Advice praise the ability to restore individual files, emails, or SharePoint documents rather than entire databases.
Unified Management: It offers a single console to manage backups across physical, virtual (VMware/Hyper-V), and cloud environments.
Stability: Reviewers on Gartner Peer Insights frequently mention its high uptime and consistent performance once the initial "trust relationship" and agents are established.
Affordability for SMBs: Compared to high-end enterprise solutions, it is often viewed as a cost-effective choice for small-to-medium businesses. Understanding Error 0xe00086cc
This error typically indicates a connection or trust issue between the media server and the remote computer. To get back to a "good experience," Veritas and community experts suggest these steps:
Establish Trust: Go to the "Backup and Restore" tab, right-click the remote server, and select Establish Trust.
Check WMI Services: Ensure that Windows Management Instrumentation (WMI) is running on the target machine and isn't blocked by a firewall.
Manual Install: If the "Push Install" continues to fail with this code, users often find success by performing a manual agent installation directly on the remote server.
For more detailed troubleshooting, you can check official guides on the Veritas Support Portal.
Are you attempting a push installation from the main server, or did this error appear during a scheduled job? Backup Exec Reviews - Gartner Peer Insights
The error code 0xe00086cc in Veritas Backup Exec typically signals a "Connection has not been authorized" or "Access Denied" issue. If the error persists, gather logs for Veritas
In the world of IT, this error usually marks the start of a classic troubleshooting "detective story" involving credentials, permissions, and network trusts. The Story of a Failed Backup: Error 0xe00086cc
It’s Friday night. The office is quiet, and the System Administrator is ready to head home—until the Backup Exec console flashes red. A critical backup job has failed with the cryptic hex code: 0xe00086cc.
The Mystery:The server and the remote agent were talking just fine yesterday. Now, they are suddenly acting like strangers. The Backup Exec server tries to reach out to the remote computer, but the connection is rejected. The Investigation:
The Identity Crisis: The admin realizes the System Logon Account on the Backup Exec server might not match the credentials expected by the remote server.
The Broken Trust: Sometimes, the "handshake" between the media server and the remote computer expires. The admin has to right-click the server in the console and select Establish Trust to renew their digital friendship.
The Password Change: It turns out a service account password was updated earlier that day, but the Backup Exec Services were still trying to use the old one. The admin must go to Tools > Backup Exec Services to update the Service Credentials.
The Resolution:The admin updates the credentials, restarts the services in the correct order to ensure they "wake up" properly, and clicks Run Now. The status bar turns green. The data is safe, the story ends with a successful backup, and the admin finally gets to go home. How to Fix It (The Short Version) If you are seeing this error, follow these standard steps:
Check Credentials: Ensure the System Logon Account in Backup Exec matches the permissions on the remote server.
Establish Trust: Right-click the remote server in the Backup and Restore tab and select Establish Trust.
Update Services: Go to Tools > Backup Exec Services > Services Credentials and ensure the service account information is up to date.
Restart Services: Use the Backup Exec Services Manager to restart all services in the correct sequence.
How to troubleshoot "Access Denied to Remote Agent" and/ ... - Veritas
The error code 0xe00086cc in Veritas Backup Exec is a common stumbling block for administrators, typically signaling that the software cannot find a specific resource or that a connection to a remote agent has failed. This essay explores the technical nature of the error, its primary causes, and the methodical steps required for resolution. The Anatomy of Error 0xe00086cc At its core, this error is a resource discovery failure
. Backup Exec operates on a client-server model where the media server must establish a stable handshake with the Remote Agent for Windows Servers (RAWS) or Linux Servers (RALUS). When the media server attempts to initialize a job—be it a backup, restore, or simple browse—and finds that the target volume, database, or virtual machine is unreachable, it throws the 0xe00086cc exception. Primary Triggers The root causes generally fall into three categories: Network and Connectivity Issues:
This is the most frequent culprit. If DNS resolution fails, the media server may attempt to contact the remote host using an outdated IP address. Similarly, hardware firewalls or Windows Firewall may block the default port (10000) used by the Backup Exec Agent. Service Failures: For a backup to succeed, the Remote Agent service
must be running on the target machine. If this service has crashed or is hung in a "Starting" state, the media server will report a resource failure. Authentication and Permissions: Changes in the System Logon Account
or the specific credentials used to access a resource (like a SQL instance or an Exchange mailbox) can lead to this error. If the account lacks the "Log on as a service" right or has had its password changed without being updated in the Backup Exec console, the handshake will fail. Strategic Troubleshooting
To resolve 0xe00086cc, a structured approach is necessary. The first step should always be verifying the status of the Backup Exec Remote Agent service
on the target server. Restarting this service often clears temporary communication glitches. If the service is functional, the focus shifts to network transparency . Admins should use tools like
to ensure name resolution is accurate. Furthermore, checking the Selection List
is vital; if a folder was deleted or a drive letter changed on the target server since the job was originally created, the software will fail to find the "resource," triggering the error. Re-selecting the backup sources often refreshes the pointer and resolves the conflict. Conclusion
While 0xe00086cc can be frustrating, it is rarely a sign of data corruption. Instead, it serves as a diagnostic signal that the bridge between the media server and its target has been broken. By systematically checking service health, network paths, and credential validity, administrators can quickly restore the integrity of their backup environment. specific environment
, such as a virtual machine or a SQL database, where this error is occurring?
I’m unable to provide a “full story” for the error 0xe00086cc in Backup Exec because it’s not a narrative or lore — it’s a technical error code. However, I can give you a complete technical breakdown of what the error means, why it happens, and how to resolve it.
Collect logs from:
Contact Veritas support with the logs and error code.
The error code 0xe00086cc in Backup Exec typically occurs during a Remote Agent push installation
indicates a communication or permission failure between the Backup Exec server and the remote machine you are trying to protect Veritas Technologies Common Causes WMI Issues:
Windows Management Instrumentation (WMI) might be blocked or corrupted on the remote server. Firewall Blocks: Disclaimer: Backup Exec is a product of Veritas Technologies
The Windows Firewall or a third-party firewall may be blocking the necessary ports for WMI, file/printer sharing, or Remote Registry. Permission Denied:
The account used for the push installation lacks local administrative rights on the target computer. Disabled Services: Critical services like Remote Registry might not be running on the remote machine. Spiceworks Community How to Resolve It Enable Remote Registry: Ensure the Remote Registry
service is set to "Automatic" and is currently "Started" on the remote server. Verify Firewall Rules:
Temporarily disable the firewall on the remote machine to test the connection. If it works, create exceptions for WMI and File and Printer Sharing. Check Admin Rights: Ensure the Backup Exec Service Account (BESA)
or the account you provided during the push install has full administrative privileges on the target server. Run WMI Diagnosis: If the issue persists, use the WMI Diagnosis Tool
(WMIDiag.vbs) on the remote server to identify internal WMI errors. Manual Installation:
If the push install continues to fail, you can manually install the agent by copying the installation files (usually found in the
folder on the Backup Exec server) to the remote machine and running required for Backup Exec communication? Backup Exec Remote Agent Install Fail - Access Denied
In the landscape of modern data management, Veritas Backup Exec stands as a cornerstone for organizational resilience. However, few things disrupt the peace of a system administrator like the cryptic arrival of an error code. Among these, 0xe00086cc—often accompanied by the message "A failure occurred while connecting to the Backup Exec Remote Agent"—is a particularly common hurdle that highlights the intricate handshake required between a media server and its remote targets. The Anatomy of the Error
At its core, error 0xe00086cc is a communication failure. It signifies that the Backup Exec media server attempted to establish a secure link with the Remote Agent for Windows (RAWS) on a target machine but was rebuffed. This isn't merely a "plug unplugged" scenario; it usually points to a breakdown in the authentication or networking protocols that govern how these two entities trust one another. Primary Catalysts Several factors typically trigger this disruption:
The Trust Relationship: Modern versions of Backup Exec require an explicit "trust" to be established between the server and the remote agent. If this certificate-based handshake is revoked or expires, the connection fails immediately with 0xe00086cc.
Network Interruption: Firewalls are frequent culprits. If the required ports (traditionally NDMP port 10000) are blocked by a local Windows Firewall or a network appliance, the media server remains "blind" to the remote agent's presence.
Service Status: Occasionally, the solution is as simple as the Remote Agent service on the target machine being stopped or hung, preventing it from listening for incoming requests. Path to Resolution
Resolving the 0xe00086cc error requires a methodical approach to infrastructure troubleshooting:
Re-establish Trust: The most effective fix is often right-clicking the remote server within the Backup Exec console and selecting "Establish Trust." This refreshes the security certificates.
Verify Services: Ensure the Backup Exec Remote Agent for Windows is running on the target server and set to 'Automatic.'
Audit Connectivity: Use tools like telnet or Test-NetConnection to verify that port 10000 is open and reachable between the two machines. Conclusion
While error 0xe00086cc can temporarily halt backup operations, it serves as a vital diagnostic signal. By addressing the underlying trust and connectivity issues, administrators not only clear the error but also reinforce the security and reliability of their entire data protection strategy.
If you are currently troubleshooting this, I can help further if you let me know: What version of Backup Exec you are using? If you recently updated or changed credentials? If this is happening to one server or all of them?
The error code 0xe00086cc in Veritas Backup Exec typically indicates a communication or trust failure between the media server and the Remote Agent on the target machine. This specific hex code (often paired with "Access is denied" or "The resource could not be backed up") usually stems from mismatched credentials, outdated agents, or a broken security certificate. Core Causes of Error 0xe00086cc
Trust Relationship Issues: The security certificate between the Backup Exec server and the remote computer is missing or invalid.
Credential Mismatch: The Backup Exec Service Account (BESA) or the System Logon Account has a password that has expired or does not match the credentials on the target server.
Version Discrepancy: The Remote Agent (RAWS) on the target machine is older than the version running on the media server.
Network/WMI Blocks: Firewall rules or disabled services (like WMI) are preventing the initial handshake. Step-by-Step Troubleshooting Guide 1. Establish a Manual Trust Relationship
If the trust was not established during the initial "push" install, you must do it manually:
In the Backup Exec console, go to the Backup and Restore tab. Right-click the server that failed with the error. Select Establish Trust from the menu. 2. Update the Remote Agent
Backup Exec generally requires the Remote Agent on target servers to match the Media Server’s version.
Check Versions: On both machines, go to Help and Documentation > About Backup Exec to verify the build numbers.
Push Reinstall: Right-click the server in the console and choose to update or reinstall the agent. 3. Verify and Reset Logon Credentials A common culprit is an outdated System Logon Account.
How to determine the installed version for Backup Exec - Veritas
The error code "0xe00086cc" in Backup Exec is a specific issue that users may encounter. Let's dive into what this code generally signifies and potential steps to resolve it.