Locate the problem server in your managed machines index list.
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
Follow these systematic solutions to resolve the error and restore your backup pipeline. 1. Verify and Unlock the Backup Exec Service Account (BESA)
The most comprehensive technical guide for this error is the
: Run cleaning jobs on tape drives and replace media when necessary. Outdated or worn media can cause communication errors that manifest as error 0xe00086cc. 0xe00086cc backup exec
Verify that the Windows Firewall is not blocking WMI or File and Printer Sharing. Check that the service is started. Establish Trust Relationship
Quick checks (do these first)
Close the Backup Exec application. From the Windows Control Panel, select (or Programs and Features ), choose Backup Exec, and click Change . Select Local installation and then Repair . The repair process stops all Backup Exec services, reinstalls corrupted files and registry keys, reinstalls tape devices, and restarts the services. The database is not reinstalled during a repair, so existing backup data and job configurations remain intact.
: The security certificate between the Backup Exec server and the remote computer is missing or invalid. Locate the problem server in your managed machines
If you are currently troubleshooting this, I can help further if you let me know: What you are using? If you recently updated or changed credentials ? If this is happening to one server or all of them ?
💡 Check the Windows Event Viewer on the remote server at the exact time of the failure. Look for "Application" errors related to beremote.exe . If the agent is crashing, you may need to perform a clean re-install of the Remote Agent software. To help me narrow this down for you, could you tell me: Did this start happening suddenly or after an update?
Backup Exec uses specific ports for communication between the media server and remote agents, primarily TCP port 10000 for the Remote Agent service. Firewalls, both Windows built‑in and third‑party, may block this port or the associated executable ( beremote.exe ). Additionally, issues such as DNS resolution failures, incorrect hostname entries, or VPN connectivity problems can all manifest as error 0xe00086cc.
Test-NetConnection <remote_IP> -Port 10000 If you share with third parties, their policies apply
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
The error in Veritas Backup Exec typically points to an "Access Denied" failure. This often occurs when the Backup Exec engine cannot authenticate or communicate with a remote server, such as a SQL instance or a Windows agent. The Story of Error 0xe00086cc: The Failed Handshake
Backup Exec generally requires the Remote Agent on target servers to match the Media Server’s version.
Verify that a valid exists. If it is missing, create a new one and mark it as the Default Logon Account .
Veritas Backup Exec error 0xe00086cc is a signal that your backup software lost its grip on your storage media. By systematically checking your physical connections, updating drivers, and disabling aggressive network power-saving features, you can restore stability to your backup environment and ensure your data remains safely protected. If you(NAS, SAN, Tape, local disk, or cloud?) What is hosting your Backup Exec server?