0xe00086cc Backup Exec May 2026

VSS requires that the SYSTEM account have full control over the volume root and the System Volume Information folder.

For NAS or networked storage, ensure the Backup Exec service account has Full Control on the share and NTFS permissions.

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. VSS requires that the SYSTEM account have full

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

The error code "0xe00086cc" in Backup Exec is a specific issue that users may encounter. Let's dive into what this code generally signifies and potential steps to resolve it.

Error 0xe00086cc 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.

In 90% of cases, the issue resolves at Step 1 or Step 2. For the remaining 10%, the VSS DLL re-registration or Hyper-V permission adjustment will restore your backup reliability. If all else fails, Veritas Support can analyze the verbose logs generated from the steps above. For NAS or networked storage, ensure the Backup

Remember: 0xe00086cc is not a hardware failure; it is a permission or service glitch. With patience and this guide, your backups will be running successfully again within the hour.

Last updated: For Backup Exec versions 16 through 22 (and 22.1+). Always test fixes in a non-production environment first.

Many antivirus tools lock VSS files (e.g., ..System Volume Information\GUID), causing 0xe00086cc.

Exclude the following paths in your AV policy on the backup source and media server:

After exclusions, reboot and test the backup.

Before jumping into fixes, you must identify the root cause. The error typically stems from one of the following scenarios: