0xe00086cc Backup Exec [portable] May 2026

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

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 0xe00086cc backup exec

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 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:

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

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. It looks like you're encountering the error 0xe00086cc

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 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.

What is Error 0xe00086cc in Backup Exec?

Error code 0xe00086cc is a VSS (Volume Shadow Copy Service) related failure. The full error message often reads:

"VSS reported an error. The I/O writes have failed. Check the Windows Event Viewer for more details. Access is denied."

In technical terms, the error translates to VSS_E_ACCESS_DENIED (0x8004230C). This indicates that Backup Exec’s AOFO (Advanced Open File Option) or the VSS infrastructure was unable to read one or more volumes on the target machine because the process lacked the necessary permissions.

Step 3: Run a Hardware Diagnostic Test

Run a diagnostic test on the server, storage, and network hardware to identify any issues.
Check for firmware updates for your hardware and apply them if necessary.

What is actually happening?

When you see 0xe00086cc, the backup job usually starts successfully, runs for a few seconds or minutes, then crashes. In the job log, you’ll likely see the failure pointing to a specific Volume Shadow Copy Service (VSS) writer or a specific system state component (like the Registry or COM+ Class Database).

The core problem: Backup Exec requested a snapshot of a volume (usually C:) or a specific system component from VSS. The VSS writer responded, "I don't know where that file is," or "Someone locked this exclusively," causing the snapshot to become unstable.

Step 7: Re-register VSS DLLs (If Windows Server is Corrupted)

If none of the above works, VSS system files may be corrupted.

On the backup source server:

cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
net start vss
net start swprv

Reboot and re-test.

The takeaway

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 code 0xe00086cc in Veritas Backup Exec typically occurs during a push installation or upgrade of the Agent for Windows (RAWS). It is often closely related to error 0xe00086c0, which indicates that the version of the agent already on the target computer is not supported for a direct upgrade by your current Backup Exec media server. Primary Cause This error is usually triggered because:

Incompatible Upgrade Path: The existing Remote Agent on the target machine is too old (e.g., several versions behind) for the current Backup Exec version to upgrade it automatically.

Connection/WMI Issues: In some cases, environmental blockers like a firewall, disabled Windows Management Instrumentation (WMI), or the Remote Registry service being stopped can prevent the installer from correctly identifying the remote agent's state. Recommended Solutions Manual Uninstall and Reinstall (Most Reliable) Log on to the target remote computer.

Use Add/Remove Programs (or Apps & Features) to manually uninstall the existing Backup Exec Remote Agent. Restart the target computer.

Push the installation again from the Backup Exec media server or perform a manual installation using the installation media found in the RAWSX64 or RAWS32 folders. Verify WMI and Network Settings

Ensure the Windows Management Instrumentation (WMI) service is running and set to Automatic on the target machine.

Verify that the Windows Firewall is not blocking WMI or File and Printer Sharing. Check that the Remote Registry service is started. Establish Trust Relationship

If you can see the server in the "Backup and Restore" tab, right-click it and select Establish Trust to ensure the media server has the correct security handshake with the remote agent. Check Service Credentials

Ensure the System Logon Account (SLA) used for the installation has local administrative rights on the target server.

Note: Be aware that Backup Exec has reached its end of sale as of March 31, 2026, with end-of-life support scheduled for April 30, 2029. "VSS reported an error

Conclusion

Error 0xe00086cc in Backup Exec is intimidating but almost always solvable by methodically checking permissions, VSS health, and third-party interference. Start with the simplest fix—verifying the backup service account credentials—and escalate through VSS writer resets, shadow storage cleanup, and antivirus exclusions.

In 90% of cases, the issue resolves at Step 1 or Step 2. For the remaining 10%, the VSS DLL re-registration or Hyper-V permission adjustment will restore your backup reliability. If all else fails, Veritas Support can analyze the verbose logs generated from the steps above.

Remember: 0xe00086cc is not a hardware failure; it is a permission or service glitch. With patience and this guide, your backups will be running successfully again within the hour.

Last updated: For Backup Exec versions 16 through 22 (and 22.1+). Always test fixes in a non-production environment first.

The 0xe00086cc error in Veritas Backup Exec typically indicates a communication failure between the Backup Exec server and the Remote Agent. This occurs when the media server cannot establish a secure connection or loses synchronization with the target machine during a job. Understanding Error 0xe00086cc

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

Service Crashes: The Remote Agent service (beremote.exe) on the target server has stopped or hung.

Network Latency: High "packet loss" or "timeout" issues during heavy data transfer.

Port Blocking: Firewalls blocking the default NDMP port (10000) or dynamic port ranges.

Security Mismatch: Incompatibility between the encryption levels of the server and the agent.

DNS Issues: 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 it fails, check your Windows Firewall or hardware firewall settings. 3. Check for Automated Updates A version mismatch can trigger 0xe00086cc. Go to the Backup Exec console. Check if there are pending Service Packs (SP) or Hotfixes.

If you updated the Media Server recently, you must push the updated agent to all remote servers. 4. Optimize Network Settings

If the error occurs mid-backup (partial success), it’s likely a timeout.

Disable TCP Chimney Offload on the network cards of both servers. Ensure NIC drivers are up to date.

In Backup Exec settings, try reducing the network throttle to see if stability improves. Advanced Resolution: Trust Relationships

In newer versions of Backup Exec, the "Trust" between the server and agent must be established. Right-click the server in the Backup and Restore tab. Select Establish Trust.

If the trust is broken, the connection will be rejected with error 0xe00086cc.

💡 Pro Tip: Check the Windows Event Viewer on the remote server at the exact time of the failure. Look for "Application" errors related to beremote.exe. If the agent is crashing, you may need to perform a clean re-install of the Remote Agent software. To help me narrow this down for you, could you tell me: Did this start happening suddenly or after an update?

Is it happening to all servers or just one specific machine?

What version of Backup Exec (e.g., 21.x, 22.x) are you currently running?

The hexadecimal code 0xe00086cc corresponds to a specific error message in Veritas Backup Exec: "The Virtual Machine is not synchronized with the Virtual Machine Manager."

While an error message might not seem like a "feature" at first glance, the resolution for this error introduces a helpful feature designed to maintain data integrity during backups.

Here is a breakdown of the error and the "helpful feature" involved in resolving it.