Many antivirus tools lock VSS files (e.g., ..System Volume Information\GUID), causing 0xe00086cc.
Exclude the following paths in your AV policy on the backup source and media server:
After exclusions, reboot and test the backup.
The error code "0xe00086cc" in Backup Exec points towards authentication or access issues during a backup job. By methodically checking the potential causes and performing thorough troubleshooting, you should be able to resolve the issue. If problems persist, referring to detailed documentation or contacting Symantec support (or reaching out to a qualified IT professional) may provide more targeted assistance.
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. 0xe00086cc backup exec
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 Many antivirus tools lock VSS files (e
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 hexadecimal code 0xe00086cc corresponds to a specific error message in Veritas Backup Exec: "The Virtual Machine is not synchronized with the Virtual Machine Manager." After exclusions, reboot and test the backup
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.
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.
If none of the above work, the issue isn't the target—it's the source’s catalog. The Backup Exec database (BEDB) sometimes loses track of a file that doesn't exist or thinks a drive letter changed.