Share via

ASR Troubleshooting: Enable Protection fails for VMware to Azure Scenario

  • Article

When attempting to enable protection in Azure Site Recovery (ASR), you may receive an error like the following: 

Push installation failed with error ID : 78007

Provider error code 95105

Protection could not be enabled.

Possible causes: Push installation of mobility service to the source machine failed with error code EP0856.  Either source machine not running, or there are network connectivity issues between the process server and the source machine.

Push install logs will show errors similar to the following: 

[at win\windowsremoteconnection.cpp:remoteApiLib::WindowsRemoteConnection::netconnect:400] network share connection to path: \10.1.1.1\C$ failed with error : 5(Access is denied.)

#~> (03-30-2017 16:19:13): ERROR 5636 9432 CoCreateInstance failed. Error 800401F0

#~> (03-30-2017 16:19:13): ERROR 5636 9432 Connection to WMI provider root\CIMV2 is failed

#~> (03-30-2017 16:19:13): ERROR 5636 9432 Failed to initialize the generice wmi

#~> (03-30-2017 16:19:13): ERROR 5636 9432 Host::GetIPAddress failed: nicinfo missing

#~> (03-30-2017 16:19:44): ERROR 5636 9432 CoCreateInstance failed. Error 800401F0

This error indicates that the Configuration Server does not have connectivity to the machine you are attempting to enable protection for.  Check the following settings:

  • Verify that the host's firewall allows connections from the CS
  • Verify that account used on the PS has admin rights on the server
  • Verify IP connectivity and DNS resolution are working correctly
  • Verify that you can browse the C$ share on the target computer from the CS (logged in as the installation account)
  • Verify that the target server has a secure channel with the domain and that authentication is working properly
  • As a test and/or a last resort, install the mobility agent manually