Share via

Hyper-V Server 2019 Replica Problem

Joe Fly 21 Reputation points
2020-10-05T11:22:48.91+00:00

Hi,
In my organization i have multiple Hyper-V Servers (2012, 2016). We are using Hyper-V replica between them.

Few days ago we installed Hyper-V Server 2019 on a new server. We are now trying to replicate some of the VMs to existing Hyper-V servers (2012, 2016), however when we try to configure replication for VM we get this event:

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:

MailServer
98C8BA14-7A2E-4F05-979A-F7F96A80B522
%%2147778582
0x80048016

The locale specific resource for the desired message is not present

The firewall is not the issue. Any suggestions ?

Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,612 questions
0 comments
Accepted answer
  1. Xiaowei He 9,876 Reputation points
    2020-10-12T05:49:23.17+00:00

    Hi,

    Please check if the VM's configuration version is supported on the replica server:

    31440-image.png

    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--

    If the configuration is supported on the replica server while we still get the error, please check the event viewer on both the primary host and the replica host, check if there are any other logs related to replication apart from the event 32000.

    Please check the event log in Event viewer> Applications and Services Logs>Microsoft>Windows>Hyper V VMMS> Admin.

    Thanks for your time!
    Best Regards,
    Anne

    -----------------------------

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

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Joe Fly 21 Reputation points
    2020-10-20T11:55:56.543+00:00

    That could be the issue. However i didn't test it. I exported VM to another host.

    0 comments
  2. Nishant Potdar 81 Reputation points
    2024-06-03T03:40:37.4066667+00:00

    In our environment, I faced a similar issue.

    I did the following steps in order to resolve the replication error:

    1. On the primary Hyper-V host, go to VM properties, check the replication setting, and compare it with other VMs on the host.
    2. Log in to the Replica partner Host and confirm the replication is ON by checking the Hyper-V settings under the Hyper-V Manager.
    3. Go to the "Replica VM" and select any drive attached to the VM, then browse, go one step up right click GUID, and choose open in new window.
    4. Make sure all the VM disks are shown in the same folder.
    5. On the replica Hyper-V host, go to the Hyper-V Manager and right-click on the replica VM, Remove Replication.
    6. Do step no. 5 for the primary VM too.
    7. Go to the replica Host, and RENAME the existing GUID folder e.g. GUIDONTHEREPLICAHOST_OLD
    8. On the primary Hyper-V host, enable the replication for the VM.
    9. The renamed old replica folder (Step no.7) can be deleted any time after the new sync is finished.
    0 comments