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.
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 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 0xe00086cc backup exec
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?
Troubleshooting Backup Exec Error 0xe00086cc: A Comprehensive Guide
Are you experiencing issues with your Backup Exec software, specifically encountering the error code 0xe00086cc? This error can be frustrating, especially when you're relying on your backups to ensure business continuity. In this blog post, we'll explore the possible causes of this error, provide step-by-step troubleshooting guides, and offer solutions to help you resolve the issue.
What is Backup Exec Error 0xe00086cc?
The error code 0xe00086cc is a common issue encountered in Backup Exec, a popular backup and disaster recovery software developed by Veritas. This error typically occurs when the software is unable to complete a backup job, and it can be caused by a variety of factors.
Possible Causes of Error 0xe00086cc
Before we dive into the troubleshooting guide, let's explore some possible causes of the error:
Troubleshooting Steps for Error 0xe00086cc
To resolve the error 0xe00086cc, follow these step-by-step troubleshooting guides:
Encountering a backup failure is a system administrator’s worst nightmare. When you check the job log in Veritas Backup Exec and see the cryptic error code 0xe00086cc, accompanied by the message "Access is denied," it can bring your data protection strategy to a screeching halt.
This error is one of the most common yet frustrating issues in Backup Exec environments, typically occurring during backups of Windows servers, Hyper-V hosts, or VMware virtual machines. In this comprehensive guide, we will dissect what error 0xe00086cc means, its primary causes (ranging from credential issues to VSS writer failures), and provide a step-by-step methodology to resolve it permanently.
If none of the above works, VSS system files may be corrupted. When you see 0xe00086cc , the backup job
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.
Corrupted VSS writers can trigger the 0xe00086cc error directly.
On the affected server (the backup source):
vssadmin list writers again—all should show State: [1] Stable.If you are rushing to fix this during production hours, here is your cheat sheet:
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. Troubleshooting Steps for Error 0xe00086cc To resolve the