One or more jobs on VMM/Hyper-V/Configuration server '%Name;' failed after the VMM/Hyper-V/Configuration server was upgraded and the Microsoft Azure Site Recovery Provider was reinstalled.
No communication from Mobility service on %HostName; since more than %TimeoutThreshold; seconds.Replication of the following ...
No site with the specified site ID - %SiteId; exists in Microsoft Azure Site recovery. Ensure the site is created before ...
No synchronization percentage is available on the replicating logical unit '%LogicalUnitName;'. Initial replication can't ...
On the VMM/Hyper-V/Configuration server, restart the VMM/Microsoft Azure Site Recovery service to restart the failed job. ...
One or more jobs on VMM/Hyper-V/Configuration server '%Name;' failed after the VMM/Hyper-V/Configuration server was upgraded ...
One or more logical units are already part of VMM replication group '%ReplicationGroupName;'. If you moved the logical units ...
One or more test virtual machines created for test failover of replication group %ReplicationGroupName; couldn't be started. ...
One or more virtual machines ('%VMNames;') managed by Microsoft Azure Site Recovery aren't members of replication group '%ReplicationGroupName;'. ...
Protection can't be enabled with the virtual machine in its current state. Check the Provider errors for more information. ...