Lemonde
  • Lemonde
  • Advanced Member Topic Starter
5 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:

32000

0

2

0

0

0x8000000000000000

2807

Microsoft-Windows-Hyper-V-VMMS-Admin

server.domain.suffix

VM

6DD15EEA-228A-4F26-ABC9-4BCAD1D1A40F

%%2147500036

0x80004004


Sponsor

Want to thank us? Use: Patreon or PayPal or Bitcoins: 12G4A52Znm5s35buKDEmKU2p2vQY69Nsyo

Protect your visitors with SSL, from $3.44

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