user wants a comprehensive article about the "0xe00086cc backup exec" error. I need to cover its meaning, causes, solutions, and preventive measures. I'll start by searching for general information about this error. search results show some potentially relevant links. The Microsoft Q&A link might be about Azure backup, not specifically Backup Exec. Result 0 from the first search seems to be about a Microsoft Q&A page for Azure backup, not Backup Exec. Result 2 from the first search is a French manual page. Result 0 from the second search is a Japanese Fujitsu page. Result 2 from the second search is a Japanese FAQ page. Result 0 from the third search is a Chinese blog post. Result 1 from the third search is a Veritas page about Event ID 57860. Result 0 from the fourth search is a Veritas page about pending reboot. Result 5 from the fourth search is a Spiceworks thread about job engine stopping. Result 0 from the fifth search is a Huawei page about SQL DBCC. I need to open the most relevant pages. search results for the error code did not yield a definitive source, but we have several relevant pages. The Veritas article (100016185) is particularly important as it mentions the bedssql2.dll file and SQL Server. The CSDN blog also mentions this. The Japanese Fujitsu page (index 0 from second search) might be relevant. The Veritas page about repair installation (index 0 from fourth search) could be useful. The Spiceworks thread (index 5 from fourth search) might be relevant. The Huawei page (index 0 from fifth search) is about a DBCC problem. The Veritas page about service not starting (index 0 from fourth search) is about a pending reboot. I will also search for "0xe00086cc" more generally. search for the exact error code did not yield a specific article. The search results show general guides. I will open the Japanese Fujitsu page and the Spiceworks thread. PDF mentions that the error message about the Job Engine service might be ignorable. The Spiceworks thread discusses a job engine service crashing issue. I need to structure the article. I will also search for "0xe00086cc Backup Exec registry". search results show some registry-related articles. The Veritas article "Backup Exec for Windows console will not launch" (index 4) might be relevant. I will open it. I need to search for "0xe00086cc" in the context of "Backup Exec" and "corrupt job". search results for the error code did not yield a definitive source, but we have several relevant pages. The Veritas article (100016185) is particularly important as it mentions the bedssql2.dll file and SQL Server. The CSDN blog also mentions this. The Japanese Fujitsu page (index 0 from second search) might be relevant. The Veritas page about repair installation (index 0 from fourth search) could be useful. The Spiceworks thread (index 5 from fourth search) might be relevant. The Huawei page (index 0 from fifth search) is about a DBCC problem. The Veritas page about service not starting (index 0 from fourth search) is about a pending reboot. I will also search for "0xe00086cc" more generally.
Error 0xe00086cc in Backup Exec is a challenging but ultimately solvable problem. The error most frequently stems from issues with the Backup Exec System Logon Account, making credential verification the logical starting point for any troubleshooting effort. When credential checks do not resolve the issue, the systematic approach described in this article—checking agent status, network connectivity, service health, and log files—will lead to a resolution in the vast majority of cases.
Resolving this issue requires isolating permissions gaps across the active system components, authentication services, and network layers. 🛠️ Core Technical Causes of Error 0xe00086cc
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. 0xe00086cc backup exec
Follow these sequential steps to isolate and resolve the 0xe00086cc error code. 1. Inspect Hardware and Physical Connections
Try disabling GRT temporarily to see if the full backup completes. If it does, the issue is with the GRT indexing, which often requires a repair of the Remote Agent installation. Proactive Maintenance to Prevent 0xe00086cc
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 user wants a comprehensive article about the "0xe00086cc
If it does exist, select it, click , and re-type the password to overwrite any corrupted entries in the Backup Exec database. 4. Configure Antivirus Exclusions
TCP Chimney Offload and Receive Side Scaling (RSS) are designed to transfer network processing from the CPU to the network adapter. However, they frequently cause packet loss and timeout drops during high-volume backup streams.
Right-click the problematic storage device and select . search results show some potentially relevant links
If the trust is broken, the connection will be rejected with error 0xe00086cc.
This Windows feature can cause packet loss under heavy backup loads. Open Command Prompt as Administrator and run: netsh int tcp set global chimney=disabled
This error can occur in various Backup Exec versions, from older releases such as Backup Exec 2010 R3 and Backup Exec 2012 up to more recent versions like Backup Exec 15 and Backup Exec 20.
The media server cannot resolve the IP address of the remote agent correctly. Step-by-Step Troubleshooting Guide 1. Restart Remote Services The simplest fix is often the most effective. Log into the target server (the one being backed up). Open services.msc . Locate Backup Exec Remote Agent for Windows . Restart the service. Ensure the service is set to Automatic . 2. Verify Port 10000 Availability Backup Exec uses port 10000 for NDMP communication. Run telnet [ServerIP] 10000 from the media server. If the screen goes blank, the port is open.
Although error 0xe00086cc is predominantly a connectivity error, hardware problems can sometimes trigger the same error code. The following hardware‑related checks are worth performing when software troubleshooting fails to resolve the issue: