0xe00086cc Backup Exec Here

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

I’m unable to provide a “full story” for the error 0xe00086cc in Backup Exec because it’s not a narrative or lore — it’s a technical error code. However, I can give you a complete technical breakdown of what the error means, why it happens, and how to resolve it.

Common Job Types Affected

  • Backup of system state
  • Backup of Hyper-V virtual machines (host-level backups)
  • Backup of SQL Server or Exchange databases
  • Backup of large file servers with open files

3. How to Fix It (Re-enabling the Feature)

To resolve 0xe00086cc and restore the helpful synchronization feature, follow these standard troubleshooting steps:

  1. Resync the VM:
    • Open the Backup Exec console.
    • Go to the Backup and Restore tab.
    • Right-click the specific Virtual Machine causing the error.
    • Select Synchronize (or "Resynchronize"). This forces Backup Exec to reset its tracking and realign with the VM Manager.
  2. Run a Full Backup:
    • After synchronizing, run a Full Backup of the VM. This creates a fresh baseline, effectively resetting the Change Block Tracking.
  3. Restart Services:
    • If the issue persists, try restarting the Backup Exec Remote Agent for Windows Systems service on the VM itself and the Backup Exec Server service on the media server.

Summary: The error 0xe00086cc acts as a safeguard for the Incremental Backup feature. It stops the job to prevent data corruption, alerting you that the "map" of changed data is outdated. By "synchronizing" (the fix), you restore the efficiency of incremental backups.

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

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

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.

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 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

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

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 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. Common Job Types Affected

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 0xe00086cc error in Veritas Backup Exec typically indicates a communication failure between the Backup Exec server and the Remote Agent. This occurs when the media server cannot establish a secure connection or loses synchronization with the target machine during a job. Understanding Error 0xe00086cc

This error is often labeled as "A failure occurred while establishing a connection to the Remote Agent." It is a generic communication fault that points to networking, authentication, or service-level hang-ups. Top Causes for the Error

Service Crashes: The Remote Agent service (beremote.exe) on the target server has stopped or hung.

Network Latency: High "packet loss" or "timeout" issues during heavy data transfer.

Port Blocking: Firewalls blocking the default NDMP port (10000) or dynamic port ranges.

Security Mismatch: Incompatibility between the encryption levels of the server and the agent.

DNS Issues: The media server cannot resolve the IP address of the remote agent correctly. Step-by-Step Troubleshooting Guide 1. Restart Remote Services The simplest fix is often the most effective. Log into the target server (the one being backed up). Open services.msc. Locate Backup Exec Remote Agent for Windows. Restart the service. Ensure the service is set to Automatic. 2. Verify Port 10000 Availability Backup Exec uses port 10000 for NDMP communication. Run telnet [ServerIP] 10000 from the media server. If the screen goes blank, the port is open.

If it fails, check your Windows Firewall or hardware firewall settings. 3. Check for Automated Updates A version mismatch can trigger 0xe00086cc. Go to the Backup Exec console. Check if there are pending Service Packs (SP) or Hotfixes.

If you updated the Media Server recently, you must push the updated agent to all remote servers. 4. Optimize Network Settings

If the error occurs mid-backup (partial success), it’s likely a timeout.

Disable TCP Chimney Offload on the network cards of both servers. Ensure NIC drivers are up to date.

In Backup Exec settings, try reducing the network throttle to see if stability improves. Advanced Resolution: Trust Relationships

In newer versions of Backup Exec, the "Trust" between the server and agent must be established. Right-click the server in the Backup and Restore tab. Select Establish Trust.

If the trust is broken, the connection will be rejected with error 0xe00086cc.

💡 Pro Tip: Check the Windows Event Viewer on the remote server at the exact time of the failure. Look for "Application" errors related to beremote.exe. If the agent is crashing, you may need to perform a clean re-install of the Remote Agent software. To help me narrow this down for you, could you tell me: Did this start happening suddenly or after an update?

Is it happening to all servers or just one specific machine?

What version of Backup Exec (e.g., 21.x, 22.x) are you currently running?

Step-by-Step Troubleshooting to Fix 0xe00086cc

Follow these steps in order. The first few are quick checks; later steps involve deeper system modifications.

7. Verify service account permissions

  • Backup Exec services must run as a domain admin or local system account with full control over storage paths and devices.