0xe00086cc Backup Exec Site

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

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

: 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

---

Specific Scenarios: Hyper-V and VMware

Conclusion

The error code "0xe00086cc" in Backup Exec points towards authentication or access issues during a backup job. By methodically checking the potential causes and performing thorough troubleshooting, you should be able to resolve the issue. If problems persist, referring to detailed documentation or contacting Symantec support (or reaching out to a qualified IT professional) may provide more targeted assistance.

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 0xe00086cc in Veritas 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

Troubleshooting Backup Exec Error 0xe00086cc: A Comprehensive Guide Specific Scenarios: Hyper-V and VMware Conclusion The error

Are you experiencing issues with your Backup Exec software, specifically encountering the error code 0xe00086cc? This error can be frustrating, especially when you're relying on your backups to ensure business continuity. In this blog post, we'll explore the possible causes of this error, provide step-by-step troubleshooting guides, and offer solutions to help you resolve the issue.

What is Backup Exec Error 0xe00086cc?

The error code 0xe00086cc is a common issue encountered in Backup Exec, a popular backup and disaster recovery software developed by Veritas. This error typically occurs when the software is unable to complete a backup job, and it can be caused by a variety of factors.

Possible Causes of Error 0xe00086cc

Before we dive into the troubleshooting guide, let's explore some possible causes of the error:

1. Media Errors: Corruption or issues with the backup media, such as tape or disk, can cause this error.
2. Hardware Issues: Problems with the server, storage, or network hardware can prevent Backup Exec from completing the backup job.
3. Software Conflicts: Incompatibilities or conflicts with other software installed on the server can cause issues with Backup Exec.
4. Incorrect Configuration: Misconfigured backup jobs, incorrect settings, or inadequate resources can lead to this error.

Troubleshooting Steps for Error 0xe00086cc

To resolve the error 0xe00086cc, follow these step-by-step troubleshooting guides:

Step 2: Restart the VSS Writers and Related Services

Corrupted VSS writers can trigger the 0xe00086cc error directly.

On the affected server (the backup source):

1. Open Command Prompt as Administrator.
2. Run vssadmin list writers. Look for any writer showing State: [9] Failed or Last error: Timed out.
3. If writers are failed, restart the following services in order:
   • COM+ Event System
   • Volume Shadow Copy
   • Microsoft Software Shadow Copy Provider
   • Then run net stop vss and net start vss manually.
4. Reboot the server and run vssadmin list writers again—all should show State: [1] Stable.

1. Check device availability

• Open Device Manager → verify tape drive or disk device appears without yellow exclamation marks.
• For disk storage: ensure the drive letter or mount point exists and is accessible.