0xe00086cc Backup Exec

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.

Here is the battle plan. Try these in order, as the first solution resolves 80% of cases.

Solutions to Error 0xe00086cc

If the troubleshooting steps above do not resolve the issue, here are some potential solutions:

Conclusion

The error code 0xe00086cc in Veritas Backup Exec typically indicates an Access Denied"

, often occurring during remote agent installations or when attempting to back up a SQL Instance. Primary Causes & Solutions Incorrect Credentials

: This is the most common cause. The account used for the job or installation must have full administrative rights on the target machine. : Verify and re-enter the System Logon Account credentials in the Backup Exec console via Network > Logon Account Service Account Mismatch

: The Backup Exec Service Account (BESA) may not match the System Logon Account, or it could be locked in Active Directory. : Check for locked accounts in Active Directory Users and Computers . In the Backup Exec console, use the Service Credentials tool to ensure the service account is up-to-date. Missing Trust Relationship

: 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

: Windows Management Instrumentation (WMI) may be blocked by a firewall or disabled on the target server. File and Printer Sharing Remote Registry services are enabled and not blocked by a firewall. Environment Specifics (Workgroups)

: If the machine is in a Workgroup rather than a Domain, "Simple File Sharing" might interfere. Simple File Sharing in Folder Options on the remote machine. Veritas Technologies If you are seeing this while backing up a SQL Instance

, ensure that the SQL server recognizes the account and that the Backup Exec agent is properly installed and trusted on that specific node. Are you receiving this error during a backup job installing the remote agent

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

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. Encountering a backup failure is a system administrator’s

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

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 Conclusion The error code 0xe00086cc in Veritas Backup

---

Blog Title: Deep Dive: Conquering the Backup Exec 0xe00086cc (V-79-57344-39628) Error

Published: October 26, 2023 | Category: Backup & Disaster Recovery

If you manage a Windows backup environment, you know the moment of dread: You walk into the office, check your email, and see a failure notification from Backup Exec. Among the most frustrating and cryptic errors you’ll encounter is 0xe00086cc (sometimes accompanied by the description V-79-57344-39628).

This error typically translates to: "The directory or file was not found, or could not be accessed."

But in the world of Backup Exec, this generic file-not-found error is often a liar. Let’s rip off the band-aid and look at what actually causes 0xe00086cc and, more importantly, how to fix it without pulling your hair out.

0xe00086cc corresponds to:

"The media server was unable to mount the storage device because the device name may be missing or invalid, or the device may be offline or not ready."

In human terms: Backup Exec cannot access the backup storage device (tape drive, disk folder, deduplication folder, etc.) during a backup or restore job.

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.

If the error persists, gather logs for Veritas support:

Corrupted VSS writers can trigger the 0xe00086cc error directly.

On the affected server (the backup source):

Reboot the server and run vssadmin list writers again—all should show State: [1] Stable.