0xe00086cc Backup Exec ⇒

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

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

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

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 error code 0xe00086cc in Veritas Backup Exec is a common stumbling block for administrators, typically signaling that the software cannot find a specific resource or that a connection to a remote agent has failed. This essay explores the technical nature of the error, its primary causes, and the methodical steps required for resolution. The Anatomy of Error 0xe00086cc At its core, this error is a resource discovery failure

. Backup Exec operates on a client-server model where the media server must establish a stable handshake with the Remote Agent for Windows Servers (RAWS) or Linux Servers (RALUS). When the media server attempts to initialize a job—be it a backup, restore, or simple browse—and finds that the target volume, database, or virtual machine is unreachable, it throws the 0xe00086cc exception. Primary Triggers The root causes generally fall into three categories: Network and Connectivity Issues:

This is the most frequent culprit. If DNS resolution fails, the media server may attempt to contact the remote host using an outdated IP address. Similarly, hardware firewalls or Windows Firewall may block the default port (10000) used by the Backup Exec Agent. Service Failures: For a backup to succeed, the Remote Agent service

must be running on the target machine. If this service has crashed or is hung in a "Starting" state, the media server will report a resource failure. Authentication and Permissions: Changes in the System Logon Account

or the specific credentials used to access a resource (like a SQL instance or an Exchange mailbox) can lead to this error. If the account lacks the "Log on as a service" right or has had its password changed without being updated in the Backup Exec console, the handshake will fail. Strategic Troubleshooting

To resolve 0xe00086cc, a structured approach is necessary. The first step should always be verifying the status of the Backup Exec Remote Agent service

on the target server. Restarting this service often clears temporary communication glitches. If the service is functional, the focus shifts to network transparency . Admins should use tools like

to ensure name resolution is accurate. Furthermore, checking the Selection List The error code 0xe00086cc in Veritas Backup Exec

is vital; if a folder was deleted or a drive letter changed on the target server since the job was originally created, the software will fail to find the "resource," triggering the error. Re-selecting the backup sources often refreshes the pointer and resolves the conflict. Conclusion

While 0xe00086cc can be frustrating, it is rarely a sign of data corruption. Instead, it serves as a diagnostic signal that the bridge between the media server and its target has been broken. By systematically checking service health, network paths, and credential validity, administrators can quickly restore the integrity of their backup environment. specific environment

, such as a virtual machine or a SQL database, where this error is occurring?

Error 0xe00086cc in Backup Exec: Causes, Solutions, and Prevention Strategies

Backup Exec is a popular data protection and recovery software used by organizations to backup and restore their critical data. However, like any other complex software, it's not immune to errors. One such error that has been reported by several users is the 0xe00086cc error. In this article, we'll discuss the causes, solutions, and prevention strategies for the 0xe00086cc error in Backup Exec.

What is Error 0xe00086cc?

The 0xe00086cc error is a common error code that occurs in Backup Exec, typically during the backup or restore process. The error message may vary depending on the specific situation, but it usually indicates a problem with the backup or restore operation. The error code 0xe00086cc is a hexadecimal code that represents a specific error condition.

Causes of Error 0xe00086cc

After analyzing various user reports and technical documents, we've identified some common causes of the 0xe00086cc error:

  1. Corrupted Backup Exec database: The Backup Exec database stores critical information about the backup and restore operations. If the database becomes corrupted, it can cause errors like 0xe00086cc.
  2. Insufficient disk space: Backup Exec requires sufficient disk space to perform backup and restore operations. If the disk space is low, it can lead to errors like 0xe00086cc.
  3. Network connectivity issues: Network connectivity problems can prevent Backup Exec from communicating with the backup devices or servers, resulting in errors like 0xe00086cc.
  4. Outdated or corrupted device drivers: Outdated or corrupted device drivers can cause communication problems between Backup Exec and the backup devices, leading to errors like 0xe00086cc.
  5. Conflicting software: Conflicting software or services can interfere with Backup Exec's operations, causing errors like 0xe00086cc.

Solutions to Error 0xe00086cc

To resolve the 0xe00086cc error, try the following solutions:

  1. Restart Backup Exec services: Restarting the Backup Exec services can sometimes resolve the issue. To do this, go to the Backup Exec console, click on the "Tools" menu, and select "Services." Then, restart the Backup Exec services.
  2. Check disk space: Ensure that there is sufficient disk space available for the backup and restore operations. Check the disk space on the backup device and the server.
  3. Run the Backup Exec Database Maintenance utility: The Backup Exec Database Maintenance utility can help repair corrupted databases. To run this utility, go to the Backup Exec console, click on the "Tools" menu, and select "Database Maintenance."
  4. Update device drivers: Ensure that the device drivers are up-to-date and not corrupted. Check the device manufacturer's website for updates.
  5. Disable conflicting software: Disable any software or services that may be conflicting with Backup Exec.

Advanced Solutions

If the above solutions don't work, you may need to perform more advanced troubleshooting: Corrupted Backup Exec database : The Backup Exec

  1. Check the Backup Exec logs: Analyze the Backup Exec logs to identify the root cause of the error. The logs can provide valuable information about the error.
  2. Run a diagnostic test: Run a diagnostic test on the backup device to ensure it's functioning properly.
  3. Reinstall Backup Exec: If all else fails, you may need to reinstall Backup Exec.

Prevention Strategies

To prevent the 0xe00086cc error from occurring in the future, follow these best practices:

  1. Regularly update Backup Exec: Ensure that you're running the latest version of Backup Exec.
  2. Monitor disk space: Regularly check disk space on the backup device and server.
  3. Perform regular database maintenance: Run the Backup Exec Database Maintenance utility regularly to prevent database corruption.
  4. Use reliable device drivers: Ensure that you're using reliable and up-to-date device drivers.
  5. Test backup and restore operations: Regularly test backup and restore operations to ensure they're working correctly.

Conclusion

The 0xe00086cc error in Backup Exec can be caused by various factors, including corrupted databases, insufficient disk space, network connectivity issues, outdated device drivers, and conflicting software. By understanding the causes and solutions to this error, you can quickly resolve the issue and prevent it from happening in the future. Regular maintenance, updates, and testing can help ensure that your backup and restore operations are running smoothly.

Typical scenario leading to 0xe00086cc

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.

2. Corrupt VSS Writers (The most common cause)

Open Command Prompt as Administrator on the target server. Run: vssadmin list writers Look for any writer with a status of Failed or Stable. If you see Failed, that specific writer (e.g., Registry Writer, BITS Writer) is crashing the snapshot.

Conclusion

Error 0xe00086cc in Backup Exec is intimidating but almost always solvable by methodically checking permissions, VSS health, and third-party interference. Start with the simplest fix—verifying the backup service account credentials—and escalate through VSS writer resets, shadow storage cleanup, and antivirus exclusions.

In 90% of cases, the issue resolves at Step 1 or Step 2. For the remaining 10%, the VSS DLL re-registration or Hyper-V permission adjustment will restore your backup reliability. If all else fails, Veritas Support can analyze the verbose logs generated from the steps above.

Remember: 0xe00086cc is not a hardware failure; it is a permission or service glitch. With patience and this guide, your backups will be running successfully again within the hour.

Last updated: For Backup Exec versions 16 through 22 (and 22.1+). Always test fixes in a non-production environment first.

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

Step 2: Verify Backup Media

  1. Check the backup media (tape or disk) for any issues or corruption.
  2. Ensure that the media is properly inserted or connected to the server.
  3. Try cleaning or re-formatting the media to see if it resolves the issue.

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.

7. Verify service account permissions