Lemonde
  • Lemonde
  • 100% (Exalted)
  • Advanced Member Topic Starter
7 years ago
We are seeing the following when trying to commence replication on 2012 R2 Hyper-V boxes

Hyper-V failed to enable replication
Hyper-V is not ins a state to accept replication for virtual machine
Operation aborted (0x80004004)

Hyper-V could not replicate changes for virtual machine as Hyper-V is not in a state to accept replication on the replica server.

Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 22/06/2017 11:59:29
Event ID: 32000
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: server.domain.suffix
Description:
Hyper-V failed to enable replication for virtual machine 'T2M-DC4': Operation aborted (0x80004004). (Virtual machine ID 6DD15EEA-228A-4F26-ABC9-4BCAD1D1A40F)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
    <EventID>32000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2017-06-22T10:59:29.972027900Z" />
    <EventRecordID>2807</EventRecordID>
    <Correlation />
    <Execution ProcessID="2004" ThreadID="5916" />
    <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
    <Computer>server.domain.suffix</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
      <VmName>VM</VmName>
      <VmId>6DD15EEA-228A-4F26-ABC9-4BCAD1D1A40F</VmId>
      <ErrorMessage>%%2147500036</ErrorMessage>
      <ErrorCode>0x80004004</ErrorCode>
    </VmlEventLog>
  </UserData>
</Event>

Sponsor

Want to thank us? Use: Patreon or PayPal or Bitcoins: bc1q4whppe29dw77rm4kv4pln0gqae4yjnxly0dny0hky6yhnafukzjsyrsqhk

All opinions expressed within these pages are sent in by members of the public or by our staff in their spare time, and as such do not represent any opinion held by sircles.net Ltd or their partners.


sirclesadmin
6 years ago
In our case this was machines with duplicate IDs or names being live already on the destination replicating partner.

We had to copy the VM and register a new computer machine ID and then redo the replication in order for the VM ID to be accepted on the destination host machine.

We just copied the VHDX files so that the VM remained the same system in practice.