Either a connection couldn't be established to host server '%VMHostID;' or the virtual machine '%VMName;' ('%ID;') in cloud/site '%CloudName;' isn't in a valid state.
Disk '%DiskName;' under virtual machine'%VmRoleName;' and cloud service '%HostedServiceName;' couldn't be attached. Azure ...
Do one of the following and retry the test failover: 1. Provide a different logical network to use for the test. 2. Complete ...
Do one of the following and retry the test failover: 1. Specify a different logical network to use for the test failover. ...
Either (1) the virtual machine isn't located in a protected VMM cloud/site, or (2) The virtual machine is already protected, ...
Either a connection couldn't be established to host server '%VMHostID;' or the virtual machine '%VMName;' ('%ID;') in cloud/site ...
Either completion of test failover was left unattended for more than two weeks, or the operation failed because of an internal ...
Either completion of the manual action was left unattended for more than three days, or the operation failed because of an ...
Either Hyper-V host cluster %DRAClusterName; contains at least one static network adapter, or no connected adapters are configured ...
Either replication traffic couldn't be sent successfully to the recovery server, or the recovery server couldn't process ...