The Backup Exec Remote Agent for Windows Servers (RAWS) is not communicating properly with the Backup Exec media server. Step-by-Step Solutions for 0xe00086cc 1. Verify and Update System Logon Account Credentials
Expand the server, remove the checkmark from the item causing the error, and re-select it (if it still exists in its new location).
This error indicates that Backup Exec suddenly lost connectivity to its storage destination during a critical operation. Understanding why this happens and how to fix it is essential to keeping your disaster recovery strategy intact. What Causes Error 0xe00086cc? 0xe00086cc backup exec
Ensure TCP Port 10000 is completely open bi-directionally between the media server and remote agents for NDMP communication.
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? The Backup Exec Remote Agent for Windows Servers
In the Backup Exec console, navigate to the Servers and Virtual Hosts section, right‑click the affected server, and select or Allow Backup Exec to establish a trust with the servers . This operation re‑authenticates the connection and updates the stored security information.
cd /d %windir%\system32 net stop vss net stop swprv regsvr32 /s ole32.dll regsvr32 /s vss_ps.dll vssvc /register regsvr32 /s /i swprv.dll regsvr32 /s es.dll regsvr32 /s stdprov.dll regsvr32 /s vssui.dll net start vss net start swprv This error indicates that Backup Exec suddenly lost
The account used for the push installation lacks local administrative rights on the target computer. Disabled Services: Critical services like Remote Registry might not be running on the remote machine. Spiceworks Community How to Resolve It Enable Remote Registry: Ensure the Remote Registry
Use the console to safely to apply the configuration globally. 3. Update the System Logon Account Settings
If the troubleshooting steps above do not resolve the issue, here are some potential solutions: