This error triggers when the Backup Exec server tries to communicate with the VM Manager (vCenter/Hyper-V) to perform this synchronization, but the data is out of date or the communication state is invalid.
Common causes include:
Error 0xe00086cc often appears when backing up a Hyper-V guest.
Collect logs from:
Contact Veritas support with the logs and error code.
0xe00086cc in Backup Exec typically indicates an "Access Denied"
failure during a backup job or remote agent installation. This usually happens when the Backup Exec services or the specific job lack the necessary permissions to access the target system or data. Veritas Technologies Top Troubleshooting Article & Solutions
The most comprehensive technical guide for this error is the
Veritas Support article on troubleshooting Access Denied errors 0xe00086cc backup exec
Depending on your specific scenario, follow these steps to resolve it: 1. Synchronize Logon Accounts The most common cause is a mismatch between the System Logon Account (SLA) and the account running the Backup Exec services. Veritas Technologies Open the Backup Exec console and navigate to Network > Logon Accounts
Ensure the credentials stored in the System Logon Account match those assigned to the Backup Exec services. To update service credentials, go to Tools > Backup Exec Services > Service Credentials , enter the updated info, and restart services. Veritas Technologies 2. Check for Account Lockouts
If you are using a dedicated Backup Exec Service Account (BESA), ensure it isn't locked out in Active Directory. Veritas Technologies Active Directory Users and Computers Locate the account, right-click Properties > Account tab , and uncheck "Account is locked out". Veritas Technologies 3. Verify Local Security Policies
The account must have specific rights on the target server to perform backups: Veritas Technologies Backup files and directories Restore files and directories Logon as a service Logon as a batch job (required for newer Windows Server versions). Veritas Technologies 4. Application-Specific Issues (Exchange/SQL)
If you see this error during an Exchange backup, try disabling the "Enable restore of individual messages" option to see if the job completes.
Ensure the service account has appropriate "Sysadmin" or "Backup Operator" roles within the SQL instance. Experts Exchange Quick Summary Table Likely Cause Credential Mismatch
Re-enter credentials for the System Logon Account and restart services. Locked Account Unlock the BESA account in Active Directory. Permission Denied Ensure the account is a member of the Local Administrators group on the target server. VSS Service Error vssadmin list writers in CMD to check for failed application writers. To help narrow this down, are you seeing this during a backup job or while trying to install a remote agent Solved: Backup exec access is denied - Experts Exchange
Blog Title: Deep Dive: Conquering the Backup Exec 0xe00086cc (V-79-57344-39628) Error This error triggers when the Backup Exec server
Published: October 26, 2023 | Category: Backup & Disaster Recovery
If you manage a Windows backup environment, you know the moment of dread: You walk into the office, check your email, and see a failure notification from Backup Exec. Among the most frustrating and cryptic errors you’ll encounter is 0xe00086cc (sometimes accompanied by the description V-79-57344-39628).
This error typically translates to: "The directory or file was not found, or could not be accessed."
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.
A full or corrupted shadow storage area can cause I/O write failures.
On the failing volume (e.g., C:):
vssadmin delete shadows /for=C: /all
vssadmin resize shadowstorage /for=C: /on=C: /maxsize=10GB
Warning: Deleting shadows removes existing restore points. This is safe for backup servers but ensure you don’t need local shadow copies for restore.
After resizing, rerun the backup job.
If the error points specifically to System State or Registry, you may have registry corruption.
Check Network Connectivity:
Ensure Resource Availability:
Review Backup Job Configuration:
Logs and Detailed Error Messages:
Update and Patch Backup Exec:
The most frequent cause of 0xe00086cc is simply using the wrong credentials.
Action: Create a dedicated service account for backups, add it to BUILTIN\Administrators and BUILTIN\Backup Operators, then reassign it to the affected backup job. Contact Veritas support with the logs and error code
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.