0xe00086cc Backup Exec =link= ✰

The error code 0xe00086cc in Backup Exec typically occurs during a Remote Agent push installation

indicates a communication or permission failure between the Backup Exec server and the remote machine you are trying to protect Veritas Technologies Common Causes WMI Issues:

Windows Management Instrumentation (WMI) might be blocked or corrupted on the remote server. Firewall Blocks:

The Windows Firewall or a third-party firewall may be blocking the necessary ports for WMI, file/printer sharing, or Remote Registry. Permission Denied:

The account used for the push installation lacks local administrative rights on the target computer. Disabled Services: Critical services like Remote Registry might not be running on the remote machine. Spiceworks Community How to Resolve It Enable Remote Registry: Ensure the Remote Registry

service is set to "Automatic" and is currently "Started" on the remote server. Verify Firewall Rules:

Temporarily disable the firewall on the remote machine to test the connection. If it works, create exceptions for WMI and File and Printer Sharing. Check Admin Rights: Ensure the Backup Exec Service Account (BESA)

or the account you provided during the push install has full administrative privileges on the target server. Run WMI Diagnosis: If the issue persists, use the WMI Diagnosis Tool

(WMIDiag.vbs) on the remote server to identify internal WMI errors. Manual Installation:

If the push install continues to fail, you can manually install the agent by copying the installation files (usually found in the 0xe00086cc backup exec

folder on the Backup Exec server) to the remote machine and running required for Backup Exec communication? Backup Exec Remote Agent Install Fail - Access Denied

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

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 Use the Tapeinst

The error code "0xe00086cc" in Backup Exec is a specific issue that users may encounter. Let's dive into what this code generally signifies and potential steps to resolve it.

Step‑by‑step resolution

5. Driver & registry fix (tape drives)

The Top 5 Culprits (And How to Fix Them)

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

Prevention Best Practices

To avoid re-encountering error 0xe00086cc:

2. Verify Backup Exec device configuration

Step 3: Clear and Recreate Shadow Storage

A full or corrupted shadow storage area can cause I/O write failures.

On the failing volume (e.g., C:):

vssadmin delete shadows /for=C: /all
vssadmin resize shadowstorage /for=C: /on=C: /maxsize=10GB

Warning: Deleting shadows removes existing restore points. This is safe for backup servers but ensure you don’t need local shadow copies for restore.

After resizing, rerun the backup job.

1. The Reboot Trap (It works 50% of the time)

Believe it or not, 0xe00086cc often points to a pending file rename operation. Windows updates or application installs sometimes mark files for deletion/rename on reboot. Backup Exec trips over this pending flag.