0xe00086cc Backup Exec

Allow the installation to complete, then push a reboot to the remote server if prompted. 2. Verify VSS Writer Health

: For modern versions of Backup Exec, a trust must be established between the media server and the remote computer. : Right-click the remote server in the Backup and Restore tab and select Establish Trust WMI or Permission Blocks

Failing hard drives, loose cables, or malfunctioning RAID controllers on the storage target.

Residual files from a failed or partial uninstallation can block new installation attempts.

Understanding the root cause is the first step toward a resolution. The most frequent triggers include: 0xe00086cc backup exec

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

If the above steps do not resolve the issue, you can try the following additional troubleshooting steps:

Reduce the parameters slightly (e.g., lower a 64KB block size to 32KB) to create a more stable, less aggressive data stream across your network switch. Summary Checklist for Administrators Action Item Verification Target Expected Result Remote Agent for Windows Matches media server patch level exactly. VSS Check vssadmin list writers command All writers report [1] Stable / No Error . Network Fix TCP Chimney & RSS Disabled via Command Prompt on both servers. Security Fix Firewall Port 10000 & Antivirus Open port and active folder/process exclusions.

Corrupted VSS writers can trigger the error directly. Allow the installation to complete, then push a

Users on Software Advice praise the ability to restore individual files, emails, or SharePoint documents rather than entire databases.

The 0xe00086cc error code points directly to a breakdown in credentials or cryptographic trust. The problem typically stems from one of four core system environments:

Before diving into the fixes, use this matrix to identify where your system's communication loop is broken:

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: : Right-click the remote server in the Backup

: Attempting to back up resources using a modern engine while running an archaic or unpatched target agent will trigger a security rejection. Step-by-Step Resolution Strategies

A communication mismatch between the System Logon Account and the Remote Agent will trigger access denied faults.

If you are using a dedicated Backup Exec Service Account (BESA), ensure it isn't locked out in Active Directory. Veritas Technologies Active Directory Users and Computers Locate the account, right-click Properties > Account tab , and uncheck "Account is locked out". Veritas Technologies 3. Verify Local Security Policies