Hyper-V Replication Failed

Question

Hello,

I am testing Hyper-V replication from stand alone Hyper-V 2016 (source) to 3 nodes Hyper-V cluster 2016 (destination).

Configured Hyper-V replica broker on the cluster using Kerberos (HTTP) >> port 80.

The storage is CSV volume.

Firewall inbound rule Hyper-V Replica HTTP Listener (TCP-In) us enabled on all Hyper-V servers.

When I enable replication on a VM and reach the last page (Finish), I always received the error "Enabling replication failed".

Event log from the source Hyper-V server:

The description for Event ID 32000 from source Microsoft-Windows-Hyper-V-VMMS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

if the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

5EACEC10-CAAA-4AB0-9FA0-FAD2726EC7C9

%%2147778582

0x80048016

The locale specific resource for the desired message is not present

Event log from the destination Hyper-V cluster:

The description for Event ID 33686 from source Microsoft-Windows-Hyper-V-VMMS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

%%2147778582
0x80048016

The locale specific resource for the desired message is not present.

Answer 1

Hi,

Really thank you for your further clarification and screenshots.

I did some research and found below two threads that mention the similar issue as yours.

Please kindly help to try below solutions to see if they could resolve your issue.

1. Check if the VM's configuration version is supported on the replica server:
   
   https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/upgrade-virtual-machine-version-in-hyper-v-on-windows-or-windows-server#what-happens-if-i-dont-upgrade-the-virtual-machine-configuration-version--
2. Grant NT Virtual Machine\Virtual Machines with Log on as a Service permission on the the Hyper-V host machine.
   a. Sign in to the machine as a Domain Administrator.
   b. Install the Group Policy Management feature from the Server Manager console.
   c. After installation, open the GPMC MMC snap-in and browse to the policy that manages User Rights.
   d. Edit the policy to include NT Virtual Machine\Virtual Machines in the entries for Log on as a service.
   e. Close the policy editor.
   f. Run gpupdate /force on the Hyper-V host computer to refresh policy. You may need to wait several minutes for Active Directory replication to occur.
   https://learn.microsoft.com/en-US/troubleshoot/windows-server/virtualization/starting-or-live-migrating-hyper-v-vms-fails

For your reference:
https://learn.microsoft.com/en-us/answers/questions/116707/hyper-v-server-2019-replica-problem.html
https://social.technet.microsoft.com/Forums/office/en-US/e2c8c561-ac14-4c4e-82ba-f836280eb709/unable-to-replicate-two-of-the-4-hyperv-servers-event-id-3200?forum=winserverhyperv

Thanks,

----------

If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.

Answer 2

Hi,

The event logs you shared cannot show any error message because there is no Hyper V management tool installed on the server.

Are you checking the event logs on the Hyper-V host server instead of the VM?

Event Viewer\Application and Services Logs\Microsoft\Windows\Hyper-V-VMMS
Event Viewer\Application and Services Logs\Microsoft\Windows\Hyper-V-Worker

If the event logs are from the host server, please check if you have installed Hyper-V management tool successfully on the host.

PowerShell Command:
Install-WindowsFeature -Name Hyper-V-Tools, Hyper-V-PowerShell

For your reference:
The Hyper-V Virtual Machine Management service must be running

Thanks,

----------

If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.

Answer 3

Hello,

Replicating a VM from Hyper-V 2016 to 2019 was successful.

VM configuration version compatibility is the root cause for not able to replicate a VM from Hyper--V 2019 to 2016.

Thank You for the help.

Raed