Hyper-v orphaned replica Cannot load a virtual machine configuration: Unspecified error (0x80004005). (Virtual machine ID B3992825-272F-40A2-9B82-6965AEF78863) in data.vmcx

Question

Recently after a hard reboot Hyper-V Manager started without showing some of the target replica's.

a. I tried to reinitiate them from the source server, however this gave the dreaded 0x80004005.
b. I followed some of the online articles stating to remove the replica from the target server on C:\ProgramData\Microsoft\Windows\Hyper-V sub folders and other drives. c. Rebooted the target machine, in the log it now states Cannot load a virtual machine configuration: Unspecified error (0x80004005). (Virtual machine ID B3992825-272F-40A2-9B82-6965AEF78863)
d. double checked if no files were lingering
e. Retried to replicate from source server, same issue
f. Opened on the target server C:\ProgramData\Microsoft\Windows\Hyper-V\data.vmcx with notepad see that in the file there are references to B3992825-272F-40A2-9B82-6965AEF78863
g. used powershell Remove-VMReplication *
h. Reopened on the target server C:\ProgramData\Microsoft\Windows\Hyper-V\data.vmcx with notepad see that in the file there are references to B3992825-272F-40A2-9B82-6965AEF78863

Please help

Answer 1

sorry I made a typo in my second post. I wrote vhdx instead of vmcx. So when I copied the vmcx to the replica server, when the replica server starts it produces the error:

The description for Event ID 16300 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:

B3992825-272F-40A2-9B82-6965AEF78863
%%2147942403
0x80070003

The locale specific resource for the desired message is not present

I think the 0x80070003 means that the files cannot be found.

By the way VM does not show in the Hyper-V Manager on the replica server or in powershell

Answer 2

When you write:

"To do a quick fix in this case, I suggest that you recreate the VM with the .vhdx file on the host, then recreate the replication relationship. This way you only need to reset the configuration file of the VM, and the production environment inside the VM would remain untouched."

I need to recreate the VM on the target / replica server by creating a new machine and adding the .vhdx file as disk?

Answer 3

So on the replica target host I recreated the vm guest by creating a vm through the Hyper-V Manager with the same name and attaching the boot drive.

The following information was included with the event:

BC639C8F-2C92-446B-985A-F47A7A5FEC7B
%%2147942403
0x80070003

The locale specific resource for the desired message is not present

If the source guest has multiple drives, do all drives need to be present?

Answer 4

Restored the replica files from an old backup on the replica server. The VM guests reappeared in the Hyper-V Manager. Removed them with the Hyper-V Manager. Reinitiated the replication process from the source server. Every is now working fine. Thank you very much Microsoft for changing to our XML files to binary files. Why the hell would you use xml, json or ini like everyone else does. The person who made this decision needs to be kicked out.

Thanks everyone for the help.