Hyper-V failed to enable replication relationship on the Replica server: Unspecified error (0x80004005).

Event IDs on B2

Event ID 16300 Cannot load a virtual machine configuration: Unspecified error (0x80004005). (Virtual machine ID A10F389C-C365-4829-A748-36EAA9009690)

Event ID 33686 Hyper-V failed to enable replication relationship on the Replica server: Unspecified error (0x80004005).

Event IDs on B1

Hyper-V failed to enable replication for virtual machine ‘VMNAME: Unspecified error (0x80004005). (Virtual machine ID A10F389C-C365-4829-A748-36EAA9009690)

This only happens to some VMs, those that previously used Certificate based replication.

  1. Domain A VMs are replicated to Domain B via certificate based replication.
  2. Domain A servers are running Hyper-V Server 2012R2 or 2016.
  3. VM version is 5.
  4. VM is failed over to Domain B Hyper-V replica server B1 running WS2019 Datacenter host and started, no errors.
  5. VM is replicated to a different WS2019 Datacenter host B2 in Domain B and is failed over.  It’s still using certificate based replication.
  6. Replication is removed on all hosts.
  7. VM is deleted on but B2.
  8. VM is shutdown and upgraded to version 9.  VM starts and works fine.
  9. VM is deleted from B1.
  10. Enable replication fails from B2 to B1 with errors above.
  11. I can create new VMs on B2 and replicate them with or without certificate based replication without error.
  12. I have searched and removed all files/folders with A10F389C-C365-4829-A748-36EAA9009690 in their name on B1.
  13. Where is B1 still storing information about A10F389C-C365-4829-A748-36EAA9009690?

-=Chris

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 131072 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/taxonomy.php on line 3613