0xe00086cc Backup Exec [work] -
Understanding why this block occurs helps narrow down the fix:
Collect logs from:
Go to the tab in the Backup Exec console. Right-click the remote server that is failing.
Transient drops in network connectivity between the Backup Exec server and a Network Attached Storage (NAS) or deduplication appliance. 0xe00086cc backup exec
In the Backup Exec console, navigate to > Logon Accounts > Manage Logon Accounts .
1. Validate and Synchronize the Backup Exec Service Account (BESA)
Backup Exec relies on hundreds of registry keys. If any become corrupted or missing—often due to improper uninstallations, malware, or system issues—services may fail to start correctly. Understanding why this block occurs helps narrow down
After extensive research of community forums, official documentation, and real‑world troubleshooting cases, several primary causes consistently appear as the source of error 0xe00086cc:
Reduce the number of concurrent jobs sent to that specific storage device to prevent overloading its controller. 5. Check Windows Event Viewer
Ensure a exists. If it does not, create one. Select the account and click Edit . In the Backup Exec console, navigate to >
At its core, error 0xe00086cc translates to a storage communication failure, often accompanied by the description: "The device is not ready" or "The request could not be performed because of an I/O device error." This indicates that while Backup Exec successfully initiated a job, it lost reliable contact with the target destination—typically a tape drive, a disk-based storage folder, or a deduplication disk. In technical terms, the software’s SCSI (Small Computer System Interface) or network commands are being rejected by the physical or virtual storage layer. This is not a corruption of the data itself, but rather a disruption of the conduit through which that data must flow.
Windows Power Management settings putting network adapters or USB controllers to sleep during long backup windows. Step-by-Step Troubleshooting Guide