0xe00086cc Backup Exec: ~repack~

The Backup Exec error 0xe00086cc is a common security-related failure typically accompanied by the message "Access Denied". It most frequently occurs when the Backup Exec server attempts to communicate with a remote computer (like a SQL Instance) without the proper authorization or credentials. Core Causes of Error 0xe00086cc

The underlying issue is almost always a failure in the authentication handshake between the Backup Exec Media Server and the target Remote Agent. Specific triggers include:

Credential Mismatch: The Backup Exec Service Account (BESA) or the System Logon Account has incorrect or outdated credentials compared to what the remote resource requires.

Locked or Disabled Accounts: The account used for the backup job is locked in Active Directory, disabled, or has an expired password.

Missing Local Admin Rights: The account assigned to the Backup Exec services lacks "Local Administrator" privileges on the target remote server.

Lack of Established Trust: A manual trust relationship has not been established between the Media Server and the Remote Agent. Comprehensive Troubleshooting Steps 1. Verify and Update Logon Accounts

Ensure the Backup Exec services are using valid credentials that match the target environment.

In the Backup Exec console, navigate to Configuration and Settings > Logon Accounts > Manage Logon Accounts.

Verify that a System Logon Account exists and is set as the default.

If the credentials have changed recently, select the account, click Edit, and re-enter the correct password. 2. Check Backup Exec Service Account (BESA) Permissions

The account running the services must have specific rights to function. 0xe00086cc backup exec

Local Admin Group: Confirm the account is a member of the Local Administrators group on both the Media Server and the remote resource.

Active Directory Status: Check Active Directory Users and Computers to ensure the account is not locked out or disabled.

Rights Verification: You can run gpresult /Z from a command prompt on the server to verify the account has all necessary rights. 3. Establish Manual Trust

If the "Access Denied" error occurs during a backup attempt of a newly added server:

Go to the Backup and Restore tab in the Backup Exec console. Right-click the remote server that is failing.

Select Establish Trust to manually verify the security connection. 4. Configure Remote Agent Services Solved: Backup exec access is denied - Experts Exchange

1. Collect context

   • Backup Exec version and build.
   • Tape library/autoloader model and firmware.
   • Tape drive model and firmware.
   • Exact error text and job log snippet.
   • OS and drivers for the tape device.

2. Quick checks (do these first)

   • Reboot the Backup Exec server and the tape library/drive.
   • Reseat SCSI/HBA/FC/iSCSI cables and power-cycle the library.
   • Confirm correct device drivers and HBA firmware; update to vendor-recommended versions.
   • Verify Backup Exec device configuration: remove and re-add the tape library/drive in Devices view.
   • Clean the tape drive with a manufacturer-cleaning cartridge (if due).
   • Try a different tape cartridge (to rule out bad media).

3. Device/driver and firmware actions

   • Update tape drive firmware to latest vendor release.
   • Update HBA/RAID/iSCSI drivers and firmware on the server.
   • Use vendor diagnostic tools to run drive self-tests; replace drive if diagnostics fail.

4. Backup Exec-specific steps

   • Ensure Backup Exec host ID and device mapping are correct; run Device Configuration Wizard.
   • Delete and reconfigure the device entries rather than using auto-detect if mapping mismatches.
   • Review Backup Exec event logs and job log for the underlying error code text (look for I/O, device not ready, or media error).
   • If using VTL, ensure VTL settings match Backup Exec expectations and that virtual tape mounts are healthy.
   • If encryption is used, ensure keys and encryption agents are available.

5. Network/storage layer (if applicable)

   • For SAN-attached tape: verify zoning, LUN masking, and that the server has exclusive access.
   • For NAS/VTL over network: check network stability, latency, and mounts.

6. When to escalate

   • Persistent I/O errors after cleaning and media swap → suspect hardware failure (drive or robotics).
   • Vendor diagnostics report errors → open RMA/repair with hardware vendor.
   • Backup Exec-specific errors after device reconfiguration → contact Veritas support with job logs and device logs.

7. Logs to gather before contacting support

   • Backup Exec job log and BESERVER logs.
   • Windows System and Application event logs (or OS-equivalent).
   • Tape drive/vendor diagnostics output.
   • Firmware versions and device model numbers.

If you provide the exact error text/hex code, Backup Exec version, and tape library/drive model, I can give targeted next steps.

The error code 0xe00086cc in Veritas Backup Exec typically indicates an Access Denied"

, often occurring during remote agent installations or when attempting to back up a SQL Instance. Primary Causes & Solutions Incorrect Credentials

: This is the most common cause. The account used for the job or installation must have full administrative rights on the target machine. : Verify and re-enter the System Logon Account credentials in the Backup Exec console via Network > Logon Account Service Account Mismatch

: The Backup Exec Service Account (BESA) may not match the System Logon Account, or it could be locked in Active Directory. : Check for locked accounts in Active Directory Users and Computers . In the Backup Exec console, use the Service Credentials tool to ensure the service account is up-to-date. Missing Trust Relationship

: For modern versions of Backup Exec, a trust must be established between the media server and the remote computer. : Right-click the remote server in the Backup and Restore tab and select Establish Trust WMI or Permission Blocks

: Windows Management Instrumentation (WMI) may be blocked by a firewall or disabled on the target server. File and Printer Sharing Remote Registry services are enabled and not blocked by a firewall. Environment Specifics (Workgroups) The Backup Exec error 0xe00086cc is a common

: 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

, ensure that the SQL server recognizes the account and that the Backup Exec agent is properly installed and trusted on that specific node. Are you receiving this error during a backup job installing the remote agent

8. Recreate storage device in Backup Exec

• Remove the device from BE → Rescan devices → Reconfigure storage.

Step 4: Check File System and Volume Permissions

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

• Open CMD as Admin and run:

  icacls "C:\System Volume Information" /grant SYSTEM:F
  

• Verify the volume root (e.g., C:\) has at least Read & Execute for SYSTEM and Administrators.

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

What is actually happening?

When you see 0xe00086cc, the backup job usually starts successfully, runs for a few seconds or minutes, then crashes. In the job log, you’ll likely see the failure pointing to a specific Volume Shadow Copy Service (VSS) writer or a specific system state component (like the Registry or COM+ Class Database).

The core problem: Backup Exec requested a snapshot of a volume (usually C:) or a specific system component from VSS. The VSS writer responded, "I don't know where that file is," or "Someone locked this exclusively," causing the snapshot to become unstable.

7. Verify service account permissions

• Backup Exec services must run as a domain admin or local system account with full control over storage paths and devices.

Understanding the Error Code 0xe00086cc

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.

Step 5: Disable and Re-enable Devices

1. Disable the device or media that is causing the error.
2. Wait for 30 seconds and re-enable the device or media.
3. Try running the backup job again to see if it completes successfully.

Step 2: Restart the VSS Writers and Related Services

Corrupted VSS writers can trigger the 0xe00086cc error directly.

On the affected server (the backup source):

1. Open Command Prompt as Administrator.
2. Run vssadmin list writers. Look for any writer showing State: [9] Failed or Last error: Timed out.
3. If writers are failed, restart the following services in order:
   • COM+ Event System
   • Volume Shadow Copy
   • Microsoft Software Shadow Copy Provider
   • Then run net stop vss and net start vss manually.
4. Reboot the server and run vssadmin list writers again—all should show State: [1] Stable.