Hyper-V could not replicate changes for virtual machine '%1' because the Replica server refused the connection. This may be because there is a pending replication operation in the Replica server for the same virtual machine which is taking longer than expected or has an existing connection. (Virtual machine ID %2)
Hyper-V could not replicate changes for virtual machine '%1' (Virtual machine ID %2). Replica virtual machine was found to ...
Hyper-V could not replicate changes for virtual machine '%1' as Hyper-V is not in a state to accept replication on the Replica ...
Hyper-V could not replicate changes for virtual machine '%1' as replication is suspended on the Replica server. (Virtual ...
Hyper-V could not replicate changes for virtual machine '%1' because the operation was cancelled. (Virtual machine ID %2) ...
Hyper-V could not replicate changes for virtual machine '%1' because the Replica server refused the connection. This may ...
Hyper-V could not replicate changes for virtual machine '%1' because the virtual machine was not found on the Replica server. ...
Hyper-V could not replicate changes for virtual machine '%1' because virtual machine migration is in progress on the Replica ...
Hyper-V could not replicate changes for virtual machine '%1' because virtual machine migration is in progress. (Virtual machine ...
Hyper-V could not revert one or more volumes of the application-consistent checkpoint set of Replica virtual machine '%1'. ...