: The Backup Exec Service Account (BESA) has an expired password, is locked out in Active Directory, or lacks local administrative privileges on the target node.
Ensure that the Backup Exec Remote Agent on all remote servers is updated to match the media server version.
While error 0xe00086cc can temporarily halt backup operations, it serves as a vital diagnostic signal. By addressing the underlying trust and connectivity issues, administrators not only clear the error but also reinforce the security and reliability of their entire data protection strategy.
When this hex error hits your job log, backup engines instantly halt data transfer to protect system security boundaries. This comprehensive guide outlines why this error disrupts your data protection workflow and details step-by-step methods to systematically resolve it. Understanding the Core Causes of 0xe00086cc 0xe00086cc backup exec
Many antivirus tools lock VSS files (e.g., ..System Volume Information\GUID ), causing .
Disable RSS by running: netsh int tcp set global rss=disabled
: If your dedicated service account password expires, encounters a lock-out within Active Directory, or loses local administrative rights on the destination node, security handshakes fail automatically. : The Backup Exec Service Account (BESA) has
For NAS or networked storage, ensure the Backup Exec service account has Full Control on the share and NTFS permissions.
A real‑world example:
The version of the agent already on the target computer may be too old to be directly upgraded by your current version of Backup Exec. By addressing the underlying trust and connectivity issues,
The Backup Exec Remote Agent for Windows (RAWS) service on target endpoints is stopped or fails local authentication.
To prevent the 0xe00086cc error from occurring in the future, follow these best practices:
When to escalate
Expand the server, remove the checkmark from the item causing the error, and re-select it (if it still exists in its new location).