The error code in Veritas Backup Exec typically signals a "Connection has not been authorized" or "Access Denied" issue.
This error code indicates that Backup Exec lost its connection to the target server or remote agent mid-operation. It can also mean the backup engine encountered an unexpected data structure it could not process.
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. 0xe00086cc backup exec
The storage controller or network switch becomes overwhelmed by the volume of concurrent data streams.
: On both machines, go to Help and Documentation > About Backup Exec to verify the build numbers. The error code in Veritas Backup Exec typically
Disable TCP Chimney Offload by running: netsh int tcp set global chimney=disabled
Backup Exec agents and the central backup server must maintain a certain level of compatibility. Each version of Backup Exec is designed to be compatible with a specific number of legacy agent versions for upgrades. If a remote system has an older agent version that is not supported by the newer Backup Exec server version, connection attempts fail. This is particularly relevant during rolling upgrades, where some systems may retain older agents while the central server is updated. Backup Exec requested a snapshot of a volume
To resolve 0xe00086cc and restore the helpful synchronization feature, follow these standard troubleshooting steps:
The error code 0xe00086cc in Backup Exec typically indicates a problem with the backup job, specifically related to the access or authentication to the backup destination. When you encounter this error, you may see a message similar to:
The error can occur when Backup Exec is unable to access the backup destination, which can be a local disk, network share, or cloud storage. This error may also occur due to issues with the backup job configuration, credentials, or network connectivity.
Check the status of every writer. If any writer shows a state other than [1] Stable or displays a Last error: Failed message, restart the Volume Shadow Copy service. You may need to reboot the target server to reset stuck writers. 3. Adjust Network TCP/IP Settings