Exec - 0xe00086cc Backup
The error code 0xe00086cc in Veritas Backup Exec typically signals a "Connection has not been authorized" or "Access Denied" issue.
In the world of IT, this error usually marks the start of a classic troubleshooting "detective story" involving credentials, permissions, and network trusts. The Story of a Failed Backup: Error 0xe00086cc
It’s Friday night. The office is quiet, and the System Administrator is ready to head home—until the Backup Exec console flashes red. A critical backup job has failed with the cryptic hex code: 0xe00086cc.
The Mystery:The server and the remote agent were talking just fine yesterday. Now, they are suddenly acting like strangers. The Backup Exec server tries to reach out to the remote computer, but the connection is rejected. The Investigation:
The Identity Crisis: The admin realizes the System Logon Account on the Backup Exec server might not match the credentials expected by the remote server.
The Broken Trust: Sometimes, the "handshake" between the media server and the remote computer expires. The admin has to right-click the server in the console and select Establish Trust to renew their digital friendship.
The Password Change: It turns out a service account password was updated earlier that day, but the Backup Exec Services were still trying to use the old one. The admin must go to Tools > Backup Exec Services to update the Service Credentials.
The Resolution:The admin updates the credentials, restarts the services in the correct order to ensure they "wake up" properly, and clicks Run Now. The status bar turns green. The data is safe, the story ends with a successful backup, and the admin finally gets to go home. How to Fix It (The Short Version) If you are seeing this error, follow these standard steps:
Check Credentials: Ensure the System Logon Account in Backup Exec matches the permissions on the remote server.
Establish Trust: Right-click the remote server in the Backup and Restore tab and select Establish Trust.
Update Services: Go to Tools > Backup Exec Services > Services Credentials and ensure the service account information is up to date. 0xe00086cc backup exec
Restart Services: Use the Backup Exec Services Manager to restart all services in the correct sequence.
How to troubleshoot "Access Denied to Remote Agent" and/ ... - Veritas
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 The error code 0xe00086cc in Veritas Backup Exec
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.
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: Use a cleaning tape (if tape drive)
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
Troubleshooting Guide: Resolving Backup Exec Error 0xe00086cc (Access Denied)
4. Clean and check media
- Use a cleaning tape (if tape drive).
- Try a different tape or disk to rule out media failure.
The "Nuclear" Option: Reset the Backup Exec Database
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.
- Fix 1 (Simple): Delete the failed job from the job list, restart the Backup Exec services, and recreate the selection list from scratch.
- Fix 2 (Advanced): Run
BEUtility.exeon the Backup Exec server to repair the BEDB database (SQL Express instance). Look for orphaned records referencing the missing file.
Step 6: Adjust VSS Timeout and Retry Settings in Backup Exec
Sometimes, VSS operations time out due to high I/O load.
- Open Backup Exec console.
- Go to Tools > Options > Advanced File Open Option.
- Increase the VSS snapshot timeout from 60 seconds to 300–600 seconds.
- Enable "Retry failed VSS snapshots" and set retries to 3 with 30-second intervals.
- For virtual environments: Under Hyper-V or VMware settings, increase snapshot timeout to 15 minutes.
Introduction
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.