Hyper-V failed to enable replication (Network Steve Forum)

Hyper-V failed to enable replication

Dear sir,

Problem : Hyper-V failed to enable replication for virtual machine 'xxx' : Cannot create a file when that file already exists. (0x800700B7). Virtual machine ID 27bxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx

Replication scenario : I am getting this error while i am enabling the replication again as it was disturbed so i need to re-enable it. But getting upper error.

Replication for other two VMs are running. But other replication of two VMs are stopped so i have removed the replication and deleted the VM folder from replica. still it is showing as above and not enabling the replication.

Please help.

Mitesh.

January 6th, 2014 9:35am

Mitesh - which folders did you delete on the replica server? Can you delete the replica VM instead and retry enabling replication on the primary VM? Is this between standalone servers or is the replica site in a cluster?

Can you also check the primary server's and replica server's event viewer node under the Hyper-V role and copy-paste the error message which is seen?

Praveen

Free Windows Admin Tool Kit Click here and download it now

January 6th, 2014 10:11am

Dear Praveen,

Consider my primary server is A and replica server is B.

Replication is running A to B. There are four VMs replicating from A to B. Two of them are asking resume and showing resynchronization required. I have tried to resume replication both the VMs but replication is not resumed.

So first i have removed replication from A and From B for those two VMs. Then removed VM from B and respective folder of VM (folder name on 'VM ID').

And trying to enable replication again. For other two VMs replication is working.

Mitesh.

January 6th, 2014 10:34am

Dear Praveen,

Updating error logs. Below are the different error logs shows in primary host server.

1) Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          04-Jan-14 11:49:55 AM
Event ID:      32000
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      Hvhost02.pent.int
Description:
Hyper-V failed to enable replication for virtual machine 'CM0175_SP2k10': An unexpected error occurred. (0x800300FD). (Virtual Machine ID FBB29089-7F0D-4A41-B3CC-544E4B81FBB8)
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>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-04T06:19:55.882851500Z" />
    <EventRecordID>8325</EventRecordID>
    <Correlation />
    <Execution ProcessID="2624" ThreadID="3096" />
    <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
    <Computer>Hvhost02.pent.int</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>CM0175_SP2k10</VmName>
      <VmId>FBB29089-7F0D-4A41-B3CC-544E4B81FBB8</VmId>
      <ErrorMessage>%%2147680509</ErrorMessage>
      <ErrorCode>0x800300FD</ErrorCode>
    </VmlEventLog>
</UserData>
</Event>

2) Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          04-Jan-14 11:50:14 AM
Event ID:      32000
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      Hvhost02.pent.int
Description:
Hyper-V failed to enable replication for virtual machine 'CM0175_SP2k10': Cannot create a file when that file already exists. (0x800700B7). (Virtual Machine ID FBB29089-7F0D-4A41-B3CC-544E4B81FBB8)
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>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-04T06:20:14.897932900Z" />
    <EventRecordID>8326</EventRecordID>
    <Correlation />
    <Execution ProcessID="2624" ThreadID="5460" />
    <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
    <Computer>Hvhost02.pent.int</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>CM0175_SP2k10</VmName>
      <VmId>FBB29089-7F0D-4A41-B3CC-544E4B81FBB8</VmId>
      <ErrorMessage>%%2147942583</ErrorMessage>
      <ErrorCode>0x800700B7</ErrorCode>
    </VmlEventLog>
</UserData>
</Event>

3) Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          04-Jan-14 11:57:03 AM
Event ID:      32000
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      Hvhost02.pent.int
Description:
Hyper-V failed to enable replication for virtual machine 'CM0175_SP2k10': Operation aborted (0x80004004). (Virtual Machine ID FBB29089-7F0D-4A41-B3CC-544E4B81FBB8)
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>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-04T06:27:03.416828300Z" />
    <EventRecordID>8335</EventRecordID>
    <Correlation />
    <Execution ProcessID="2624" ThreadID="1256" />
    <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
    <Computer>Hvhost02.pent.int</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>CM0175_SP2k10</VmName>
      <VmId>FBB29089-7F0D-4A41-B3CC-544E4B81FBB8</VmId>
      <ErrorMessage>%%2147500036</ErrorMessage>
      <ErrorCode>0x80004004</ErrorCode>
    </VmlEventLog>
</UserData>
</Event>

4) Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          06-Jan-14 11:50:08 AM
Event ID:      32000
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      Hvhost02.pent.int
Description:
Hyper-V failed to enable replication for virtual machine 'CM0173(SAP_QA)': Cannot create a file when that file already exists. (0x800700B7). (Virtual Machine ID 27BD03E2-622D-413F-8610-FB619E9558B5)
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>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-06T06:20:08.879373200Z" />
    <EventRecordID>8346</EventRecordID>
    <Correlation />
    <Execution ProcessID="2624" ThreadID="4580" />
    <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
    <Computer>Hvhost02.pent.int</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>CM0173(SAP_QA)</VmName>
      <VmId>27BD03E2-622D-413F-8610-FB619E9558B5</VmId>
      <ErrorMessage>%%2147942583</ErrorMessage>
      <ErrorCode>0x800700B7</ErrorCode>
    </VmlEventLog>
</UserData>
</Event>

5) Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          06-Jan-14 05:36:23 PM
Event ID:      32000
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      Hvhost02.pent.int
Description:
Hyper-V failed to enable replication for virtual machine 'CM0173(SAP_QA)': Operation aborted (0x80004004). (Virtual Machine ID 27BD03E2-622D-413F-8610-FB619E9558B5)
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>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-06T12:06:23.792590500Z" />
    <EventRecordID>8350</EventRecordID>
    <Correlation />
    <Execution ProcessID="2624" ThreadID="2348" />
    <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
    <Computer>Hvhost02.pent.int</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>CM0173(SAP_QA)</VmName>
      <VmId>27BD03E2-622D-413F-8610-FB619E9558B5</VmId>
      <ErrorMessage>%%2147500036</ErrorMessage>
      <ErrorCode>0x80004004</ErrorCode>
    </VmlEventLog>
</UserData>
</Event>

6) Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          06-Jan-14 05:36:23 PM
Event ID:      19050
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      Hvhost02.pent.int
Description:
'CM0173(SAP_QA)' failed to perform the operation. The virtual machine is not in a valid state to perform the operation. (Virtual machine ID 27BD03E2-622D-413F-8610-FB619E9558B5)
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>19050</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-06T12:06:23.792590500Z" />
    <EventRecordID>8349</EventRecordID>
    <Correlation />
    <Execution ProcessID="2624" ThreadID="2348" />
    <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
    <Computer>Hvhost02.pent.int</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>CM0173(SAP_QA)</VmName>
      <VmId>27BD03E2-622D-413F-8610-FB619E9558B5</VmId>
    </VmlEventLog>
</UserData>
</Event>

Edited by mitesh8888 Monday, January 06, 2014 2:33 PM

Free Windows Admin Tool Kit Click here and download it now

January 6th, 2014 2:31pm

Mitesh - as indicated earlier, can you please send me the top most event viewer logs when from the primary and replica server (from the hyper-v node). It's not very clear where the error is occurring - whether it's on the primary or whether it's on the replica. The event viewer message from both sides will help us isolate the problem.

If you hit a 'resynchronization' scenario, you should just ensure that the VM goes thro' a resync workflow. More information is available here - http://blogs.technet.com/b/virtualization/archive/2013/05/10/resynchronization-of-virtual-machines-in-hyper-v-replica.aspx - more time than not, it's much better than doing a complete initial replication.

Coming to the problem, I tried to repro the issue based on the steps you have provided, but I am unable to repro it. So not sure whether I am missing any step. If you can provide the snips of the logs, give me the path to the folder which you deleted - I can suggest a workaround. It's worth calling out that there are files/folders which are spread across the other folders under "Hyper-V Replica" in the recovery side. If you have deleted the VMId-folder under "Virtual machines", it might be worth double checking if there are other files, folders for the VM-Id in the other directories. This is assuming there is a problem in the replica side. In the primary side, open the folder where the VHD is located and check if there are any other files other than vhd, vhdx.

Praveen

January 6th, 2014 2:33pm

Dear Praveen,

Thanks for your reply, I have checked the settings again and found that one DNS is different which is given at Primary server, now the error changed.

Now it is showing different error. Now it is showing 'Operation aborted (0x80004004)' and still failing to enable replication.

Please guide accordingly.

Regards,

Mitesh.

Free Windows Admin Tool Kit Click here and download it now

January 6th, 2014 3:34pm

Hi Mitesh - I will need some error logs to guide you better.

Are the other VMs continuing to replicate to the same replica server without an issue? Is it specific to the VM, can you try a temp VM and help me with the error logs?

Praveen

January 6th, 2014 4:17pm

Dear Praveen,

Updating error logs. Below are the different error logs shows in primary host server.

Edited by mitesh8888 Monday, January 06, 2014 2:33 PM

Free Windows Admin Tool Kit Click here and download it now

January 6th, 2014 5:31pm

The log "'CM0173(SAP_QA)' failed to perform the operation. The virtual machine is not in a valid state to perform the operation. " indicates that replication has not been completely removed/deleted on the primary VM (or) the replica VM is not deleted.

As requested earlier, can you also send the replica side logs (if any) to rule out any issues. You could check the replication status of the primary VM by running the cmdlet 'get-vm -vmname <vmname> | select ReplicationMod' - it should be set to 'None. Ensure the replica VM does not exist on the replica server. If the replica server is part of a cluster, ensure that the VM is deleted both from the Failover Cluster Manager as well as the Hyper-V Manager

January 7th, 2014 6:17am

Dear Praveen,

Sending you the logs from replica server ( I mean from B).

Please reply as soon as possible.

1) Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          04-01-2014 12:01:40
Event ID:      16410
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      HVhost03.pent.int
Description:
'CM0173(SAP_QA)' cannot access the data folder of the virtual machine. (Virtual machine ID 27BD03E2-622D-413F-8610-FB619E9558B5)
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>16410</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-04T06:31:40.508409800Z" />
    <EventRecordID>24351</EventRecordID>
    <Correlation />
    <Execution ProcessID="1996" ThreadID="3216" />
    <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
    <Computer>HVhost03.pent.int</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>CM0173(SAP_QA)</VmName>
      <VmId>27BD03E2-622D-413F-8610-FB619E9558B5</VmId>
      <ErrorMessage>%%2147943624</ErrorMessage>
      <ErrorCode>0x800704C8</ErrorCode>
    </VmlEventLog>
</UserData>
</Event>

2) Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          06-01-2014 17:36:23
Event ID:      19050
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      HVhost03.pent.int
Description:
'CM0173(SAP_QA)' failed to perform the operation. The virtual machine is not in a valid state to perform the operation. (Virtual machine ID 27BD03E2-622D-413F-8610-FB619E9558B5)
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>19050</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-06T12:06:23.646671900Z" />
    <EventRecordID>24361</EventRecordID>
    <Correlation />
    <Execution ProcessID="1996" ThreadID="3784" />
    <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
    <Computer>HVhost03.pent.int</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>CM0173(SAP_QA)</VmName>
      <VmId>27BD03E2-622D-413F-8610-FB619E9558B5</VmId>
    </VmlEventLog>
</UserData>
</Event>

3) Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          04-01-2014 12:01:40
Event ID:      16410
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      HVhost03.pent.int
Description:
'CM0173(SAP_QA)' cannot access the data folder of the virtual machine. (Virtual machine ID 27BD03E2-622D-413F-8610-FB619E9558B5)
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>16410</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-04T06:31:40.508409800Z" />
    <EventRecordID>24351</EventRecordID>
    <Correlation />
    <Execution ProcessID="1996" ThreadID="3216" />
    <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
    <Computer>HVhost03.pent.int</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>CM0173(SAP_QA)</VmName>
      <VmId>27BD03E2-622D-413F-8610-FB619E9558B5</VmId>
      <ErrorMessage>%%2147943624</ErrorMessage>
      <ErrorCode>0x800704C8</ErrorCode>
    </VmlEventLog>
</UserData>
</Event>

Free Windows Admin Tool Kit Click here and download it now

January 7th, 2014 9:04am

Assuming the same error happened as part of copy-pasting the logs, you can notice the following events:

(1) & (3) 'CM0173(SAP_QA)' cannot access the data folder of the virtual machine. (Virtual machine ID 27BD03E2-622D-413F-8610-FB619E9558B5) ==> Hyper-V is unable to create a VM in the folder which has been configured to receive replication traffic. What is the storage subsystem on the replica server? Is it on a SMB share or is it local storage? Ensure you have the right permissions on the folder. Eg: Assume you have configured the Replica server to create the replica VMs in e:\HVR. Double-check by creating a temp-VM on the replica server and provide e:\hvr as the location to create the config file, VHDs etc. If this step succeeds, then enabling replication from the primary server should also succeed.

(2) 'CM0173(SAP_QA)' failed to perform the operation. The virtual machine is not in a valid state to perform the operation. (Virtual machine ID 27BD03E2-622D-413F-8610-FB619E9558B5) ==> The replica VM is still around in the system, ensure that it's deleted before you enable replication on the other side.

January 7th, 2014 10:51am

Dear Praveen,

I have removed whole folder from the replica server. Is there any other location where system is storing VM information?

Also, I am saving VMs in local folder.

Otherwise i have to format the drive and restart the replication.

Is there any other file which is to be deleted from different location?

Please suggest asap.

Mitesh.

Free Windows Admin Tool Kit Click here and download it now

January 7th, 2014 12:09pm

As I mentioned earlier, try out the following two steps:

1) You will need to ensure that the VM is deleted from the Hyper-V server, the error message which you have copy-pasted indicates that the replica VM still exists in the system.

2) Create a VM in the same folder (place VM config, VHD etc in that location) - ensure that it succeeds.

Is your replica server clustered? Run the get-vm cmdlet to see if the VM is still registered in the server.

Praveen

January 7th, 2014 5:13pm

Dear Praveen,

I have done following things to be sure that no any VM related file will remain at respective folder location where the replication data is stored. This is done on replica server.

1) Have removed the replication which was running and formatted the drive in which the replication was running.

2) Then i have removed the Hyper-V role, restarted the server, Again installed Hyper-V role.

3) Started replication for one VM, it was started. (Replication was giving error earlier for this VM while i was enabling before doing activity).

4) But it was giving same error while i am enabling replication for other three VMs. Replication was running for Two of them as i have mentioned earlier.

Currently, it is still giving the below same error to enable replication.

Operation aborted (0x80004004) and showing that VM is not in a valid state to perform the operation.

I am confused what to do.

Please give proper syntax so that i can give that command to send you the result as i don't know more on command base.

Please reply.

Mitesh.

Free Windows Admin Tool Kit Click here and download it now

January 9th, 2014 4:26pm

Dear Praveen,

Waiting for your reply as i think problem is critical.

Regards,

Mitesh.

January 16th, 2014 3:52pm

Hi Mitesh,

Sorry for the delay .

As for this error "Operation aborted (0x80004004) and showing that VM is not in a valid state to perform the operation."

Have the replication setup been done on both Hosts ?

Best Regards

Elton Ji

Free Windows Admin Tool Kit Click here and download it now

January 21st, 2014 4:52am

The error message indicates that one of the VMs is not in the right state. You will need to delete the replication - can you follow the steps outlined before? Specifically run the cmdlet 'get-vm -vmname <vmname> | select ReplicationMode, ReplicationState ' from an elevated PowerShell window on both your primary and replica server on the VM which is causing the issue. You are bound to get some info that the VMs are enabled for replication.

Praveen

January 21st, 2014 12:07pm

In our case, it is certificate problem. We need to re-create it.

Hyper-V failed to enable replication with 0x80004004 - Resolution ...

Free Windows Admin Tool Kit Click here and download it now

March 29th, 2014 2:28pm

I just ran into this issue. Not sure which step exactly fixed this, but:

I had initially setup these machines using makecert self signed certificates. I disabled certificate revocation checking to allow self-certs to function in this lab. So, I simply re-enabled certificate revocation checking and restarted the servers for good measure:

Deleted the subkey HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\FailoverReplication

Changed the value of HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\Replication\DisableCertRevocationCheck from 1 to 0.

I restarted all servers.

After the servers restarted, I was able to enable replication without issue.

Edited by Eric Parr 2014 10 minutes ago

March 20th, 2015 2:53am

This topic is archived. No further replies will be accepted.