After exclusions, reboot and test the backup.
Update the firmware and drivers for the backup server’s NICs, HBAs, and storage controllers.
: 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 you observe that error 0xe00086cc appears after prolonged uptime, consider scheduling weekly or bi‑weekly restarts of Backup Exec services during maintenance windows to clear any accumulated state issues. 0xe00086cc backup exec
Create a dedicated service account for backups, add it to BUILTIN\Administrators and BUILTIN\Backup Operators , then reassign it to the affected backup job.
Believe it or not, 0xe00086cc often points to a pending file rename operation. Windows updates or application installs sometimes mark files for deletion/rename on reboot. Backup Exec trips over this pending flag.
After analyzing various user reports and technical documents, we've identified some common causes of the 0xe00086cc error: After exclusions, reboot and test the backup
Your primary step is ensuring that the global account executing the network commands holds consistent credentials across the infrastructure. Backup Exec Remote Agent Install Fail - Access Denied
If name resolution fails, check DNS settings or consider using IP addresses temporarily for testing. Next, verify that TCP port 10000 is reachable and not blocked. Use Telnet or Test‑NetConnection in PowerShell:
If you have exhausted all troubleshooting steps without success, engaging Veritas Technical Support may be required. Before contacting support, gather the following information: Believe it or not, 0xe00086cc often points to
Look for amber warning lights on your server, NAS, SAN, or tape library that indicate drive failures.
Verify that a valid exists. If it is missing, create a new one and mark it as the Default Logon Account .