The Backup Exec Service Account (BESA) or the System Logon Account has an outdated, expired, or modified password in Active Directory that has not synced with the local console.
Open Backup Exec and navigate to > Logon Accounts > Manage Logon Accounts .
Backup Exec uses specific ports for communication between the media server and remote agents, primarily TCP port 10000 for the Remote Agent service. Firewalls, both Windows built‑in and third‑party, may block this port or the associated executable ( beremote.exe ). Additionally, issues such as DNS resolution failures, incorrect hostname entries, or VPN connectivity problems can all manifest as error 0xe00086cc.
On your main server, run to get the newest patches.
This error is one of the most common yet frustrating issues in Backup Exec environments, typically occurring during backups of Windows servers, Hyper-V hosts, or VMware virtual machines. In this comprehensive guide, we will dissect what error means, its primary causes (ranging from credential issues to VSS writer failures), and provide a step-by-step methodology to resolve it permanently. 0xe00086cc backup exec
: The account used for the backup job is locked in Active Directory, disabled, or has an expired password.
: 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
: You can run gpresult /Z from a command prompt on the server to verify the account has all necessary rights. 3. Establish Manual Trust
, often occurring during remote agent installations or when attempting to back up a SQL Instance. Primary Causes & Solutions Incorrect Credentials The Backup Exec Service Account (BESA) or the
But in the world of Backup Exec, this generic file-not-found error is often a liar. Let’s rip off the band-aid and look at what actually causes 0xe00086cc and, more importantly, how to fix it without pulling your hair out.
The 0xe00086cc error is a common issue in Backup Exec, a popular backup and disaster recovery software developed by Veritas. This error typically occurs when the software encounters a problem while attempting to access or write to a backup device, such as a tape drive or disk storage.
The Backup Exec error code typically surfaces during the installation or upgrade of the Remote Agent for Windows (RAWS) . This error generally indicates a compatibility or environment conflict, often occurring when the Backup Exec server attempts to push an agent to a remote machine that has a mismatched or corrupt previous installation. Common Causes of Error 0xe00086cc
: The most effective fix is often right-clicking the remote server within the Backup Exec console and selecting "Establish Trust." This refreshes the security certificates. This error is one of the most common
Error 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.
Deep Dive: Conquering the Backup Exec 0xe00086cc (V-79-57344-39628) Error
At its core, error 0xe00086cc is a communication failure. It signifies that the Backup Exec media server attempted to establish a secure link with the Remote Agent for Windows (RAWS) on a target machine but was rebuffed. This isn't merely a "plug unplugged" scenario; it usually points to a breakdown in the authentication or networking protocols that govern how these two entities trust one another. Primary Catalysts Several factors typically trigger this disruption: