Verify the virtual machine state, check that the VMM/Hyper-V server is available, and retry the planned failover. Or perform an unplanned failover if the primary site isn't available.
Verify that the recovery cloud contains at least one host running a compatible version of Windows with Hyper-V Replica enabled. ...
Verify that the script exists in the required path. Check that exceptions are being handled correctly using try-catch blocks. ...
Verify that the VMM service can access the import or export path. If the path is shared, ensure that the VMM service account ...
Verify the replication state for the virtual machine in the Microsoft Azure Site Recovery vault, and retry the operation. ...
Verify the virtual machine state, check that the VMM/Hyper-V server is available, and retry the planned failover. Or perform ...
Virtual machine '%VmRoleName;' couldn't be started under deployment '%DeployementName;' and cloud service '%HostedServiceName;'. ...
Virtual machine deployment '%DeploymentName;' couldn't be deleted because another operation is running on the virtual machine ...
Virtual machine information couldn't be retrieved from the configuration server. Check the Provider errors for more information. ...
Virtual machines '%VMNames;' were not found in Azure or could not be reached for the failover operation. This can happen ...