0xe00086cc Backup Exec Exclusive

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

Solutions to Error 0xe00086cc

Possible Causes

  1. The causes of this error are multifaceted, often requiring a methodical diagnostic approach. The most frequent culprit lies within the hardware stack, specifically the connection between the media server and the storage device. For tape-based backups, a failing SCSI terminator, a loose Fibre Channel cable, or an outdated tape driver can easily trigger 0xe00086cc. Similarly, for disk-based backups, a failing USB or eSATA controller, a network-attached storage (NAS) suffering from packet loss, or a local hard drive with bad sectors can produce identical symptoms. Another common cause is a resource conflict within Windows, where the operating system’s volume mount manager or a third-party filter driver (such as an antivirus real-time scanner) temporarily locks the target volume, making it appear "not ready" to Backup Exec. 0xe00086cc backup exec

    Understanding the Error Code 0xe00086cc

    The error code "0xe00086cc" in Backup Exec typically relates to issues with the backup job, often indicating a problem with the credentials or authentication used to access the resources being backed up. This could include servers, databases, or specific files and folders. The 0xe00086cc error in Veritas Backup Exec typically

    Common causes

    1. Device name changed – The storage device’s logical name (e.g., tape drive, RDX, or disk volume) has been altered or removed from the system.
    2. Device offline – The tape drive or disk is powered off, disconnected, or in an error state.
    3. Driver issues – Corrupt or incompatible tape/storage drivers.
    4. Permission problems – Backup Exec service account lacks access to the device or path.
    5. Device reservation conflict – Another process (like Windows native tape recognition) has locked the device.
    6. Storage media missing – No tape/disk in the drive, or media is corrupted.

    Disclaimer: Backup Exec is a product of Veritas Technologies. Always test fixes in a non-production environment first. This post refers to Backup Exec versions 16 through 22. For 2010/2012 versions, the solution usually requires upgrading the remote agent. Fix: Perform a full reboot of the target