: The existing Remote Agent on the target machine is too old (e.g., several versions behind) for the current Backup Exec version to upgrade it automatically.
The error code in Veritas Backup Exec typically occurs during a push installation or upgrade of the Agent for Windows (RAWS). It is often closely related to error 0xe00086c0 , which indicates that the version of the agent already on the target computer is not supported for a direct upgrade by your current Backup Exec media server. Primary Cause This error is usually triggered because: 0xe00086cc backup exec
At its core, error 0xe00086cc is a communication failure. It signifies that the Backup Exec media server attempted to establish a secure link with the Remote Agent for Windows (RAWS) on a target machine but was rebuffed. This isn't merely a "plug unplugged" scenario; it usually points to a breakdown in the authentication or networking protocols that govern how these two entities trust one another. Primary Catalysts Several factors typically trigger this disruption: : The existing Remote Agent on the target
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. Primary Cause This error is usually triggered because:
In 90% of cases, the issue resolves at Step 1 or Step 2. For the remaining 10%, the VSS DLL re-registration or Hyper-V permission adjustment will restore your backup reliability. If all else fails, Veritas Support can analyze the verbose logs generated from the steps above.
The hexadecimal code 0xe00086cc corresponds to a specific error message in Veritas Backup Exec: