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.
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
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 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:
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 0xe00086cc backup exec
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.
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
The Backup Exec error 0xe00086cc is a common security-related failure typically accompanied by the message "Access Denied". It most frequently occurs when the Backup Exec server attempts to communicate with a remote computer (like a SQL Instance) without the proper authorization or credentials. Core Causes of Error 0xe00086cc
The underlying issue is almost always a failure in the authentication handshake between the Backup Exec Media Server and the target Remote Agent. Specific triggers include:
Credential Mismatch: The Backup Exec Service Account (BESA) or the System Logon Account has incorrect or outdated credentials compared to what the remote resource requires.
Locked or Disabled Accounts: The account used for the backup job is locked in Active Directory, disabled, or has an expired password.
Missing Local Admin Rights: The account assigned to the Backup Exec services lacks "Local Administrator" privileges on the target remote server.
Lack of Established Trust: A manual trust relationship has not been established between the Media Server and the Remote Agent. Comprehensive Troubleshooting Steps 1. Verify and Update Logon Accounts
Ensure the Backup Exec services are using valid credentials that match the target environment.
In the Backup Exec console, navigate to Configuration and Settings > Logon Accounts > Manage Logon Accounts.
Verify that a System Logon Account exists and is set as the default.
If the credentials have changed recently, select the account, click Edit, and re-enter the correct password. 2. Check Backup Exec Service Account (BESA) Permissions
The account running the services must have specific rights to function.
Local Admin Group: Confirm the account is a member of the Local Administrators group on both the Media Server and the remote resource.
Active Directory Status: Check Active Directory Users and Computers to ensure the account is not locked out or disabled.
Rights Verification: You can run gpresult /Z from a command prompt on the server to verify the account has all necessary rights. 3. Establish Manual Trust
If the "Access Denied" error occurs during a backup attempt of a newly added server:
Go to the Backup and Restore tab in the Backup Exec console. Right-click the remote server that is failing.
Select Establish Trust to manually verify the security connection. 4. Configure Remote Agent Services Solved: Backup exec access is denied - Experts Exchange The error code 0xe00086cc in Veritas Backup Exec
0xe00086cc in Backup Exec typically indicates an "Access Denied"
failure during a backup job or remote agent installation. This usually happens when the Backup Exec services or the specific job lack the necessary permissions to access the target system or data. Veritas Technologies Top Troubleshooting Article & Solutions
The most comprehensive technical guide for this error is the
Veritas Support article on troubleshooting Access Denied errors
Depending on your specific scenario, follow these steps to resolve it: 1. Synchronize Logon Accounts The most common cause is a mismatch between the System Logon Account (SLA) and the account running the Backup Exec services. Veritas Technologies Open the Backup Exec console and navigate to Network > Logon Accounts
Ensure the credentials stored in the System Logon Account match those assigned to the Backup Exec services. To update service credentials, go to Tools > Backup Exec Services > Service Credentials , enter the updated info, and restart services. Veritas Technologies 2. Check for Account Lockouts
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
The account must have specific rights on the target server to perform backups: Veritas Technologies Backup files and directories Restore files and directories Logon as a service Logon as a batch job (required for newer Windows Server versions). Veritas Technologies 4. Application-Specific Issues (Exchange/SQL)
If you see this error during an Exchange backup, try disabling the "Enable restore of individual messages" option to see if the job completes.
Ensure the service account has appropriate "Sysadmin" or "Backup Operator" roles within the SQL instance. Experts Exchange Quick Summary Table Likely Cause Credential Mismatch
Re-enter credentials for the System Logon Account and restart services. Locked Account Unlock the BESA account in Active Directory. Permission Denied Ensure the account is a member of the Local Administrators group on the target server. VSS Service Error vssadmin list writers in CMD to check for failed application writers. To help narrow this down, are you seeing this during a backup job or while trying to install a remote agent Solved: Backup exec access is denied - Experts Exchange
The error 0xe00086cc in Veritas Backup Exec typically points to an "Access Denied" failure. This often occurs when the Backup Exec engine cannot authenticate or communicate with a remote server, such as a SQL instance or a Windows agent. The Story of Error 0xe00086cc: The Failed Handshake
Imagine a backup job as a late-night courier (the Backup Exec Server) arriving at a high-security warehouse (your Remote Server). The courier has a manifest to pick up data, but when they reach the gate, they are turned away. This "Access Denied" story usually unfolds in one of these ways:
1. The Invalid ID (Credential Mismatch)The courier is using an old ID card. In Backup Exec terms, the Logon Account used for the job might have an outdated password, or it may not have the right to "Log on as a batch job" or "Log on as a service" on the remote machine.
2. The Guard Doesn’t Recognize the Courier (Trust Issues)In newer versions of Backup Exec, the server and the remote machine must "trust" each other. If this trust relationship hasn't been established, the remote server ignores the backup request. You can fix this by right-clicking the server in the Backup and Restore tab and selecting Establish Trust.
3. The Gate is Locked (Firewalls & WMI)The courier can’t even get to the gate because it's locked. Firewalls often block the communication ports (like NDMP port 10000) or WMI (Windows Management Instrumentation) services needed for the "push" installation or initial connection. How to Fix the "Access Denied" Plot Twist Solved: Backup exec access is denied - Experts Exchange
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.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtmsSvc → Start=4) and reboot. Backup Exec must control tape drives exclusively.A real‑world example:
A backup administrator replaced a failed tape drive, but Windows assigned a new SCSI address. Backup Exec still pointed to the old device path. When the backup job ran, BE returned 0xe00086cc because the “old” tape drive no longer existed.
Fix: Rescanned devices, removed the missing drive, reconfigured the backup job to use the new drive → error cleared. Blog Title: Deep Dive: Conquering the Backup Exec
Collect logs from:
%ProgramData%\Symantec\Backup Exec\Logs)Contact Veritas support with the logs and error code.
0xe00086cc in Backup Exec typically indicates an "Access Denied"
failure during a backup or restore job, often specifically related to the Backup Exec Remote Agent Backup Exec Service Account (BESA)
lacking the necessary permissions to access a remote resource. www.veritas.com Common Causes of Error 0xe00086cc Credential Mismatch
: The username or password for the service account has changed, been disabled, or is locked out in Active Directory. Missing Permissions : The BESA does not have Local Administrator rights on the target remote server. Restricted Resource Access
: Certain directories (like "Profile Compatibility Junctions") or offline files cannot be traversed by Backup Exec because of underlying system access rights. Firewall or Network Blocks : Ports required for communication (like TCP Port 10000
for NDMP) are blocked by a firewall or another application on the remote machine. Third-Party Conflicts
: Antivirus scans or third-party snapshot providers may interfere with Backup Exec's ability to use the Microsoft VSS provider. www.veritas.com Recommended Troubleshooting Steps Backup Exec Tutorial How to restart the services
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.
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 hexadecimal code 0xe00086cc corresponds to a specific error message in Veritas Backup Exec: "The Virtual Machine is not synchronized with the Virtual Machine Manager."
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.