Error applying Replication Configuration Windows Server 2019 Hyper-V Replica Broker

Question

_{Friday, August 9, 2019 9:48 AM}

Hello,

Recently we started replacing our Windows Server 2016 Hyper-V Clusters for Server 2019. On each cluster we have a Hyper-V Replica broker that allows replication from any authenticated server and stores the Replica Files to a default location of one of the Cluster Shared Volumes.

With WS2019 we run into the issue where we get an error applying the Replication Configuration settings. The error is as follows:
Error applying Replication Configuration changes. Unable to open specified location for replication storage. Failed to add authorization entry. Unable to open specified location to store Replica files 'C:\ClusterStorage\volume1\. Error: 0x80070057 (One or more arguments are invalid).

When we target the default location to a CSV where the owner node is the same as the owner node for the Broker role we don't get this error. However I don't expect this to work in production (moving roles to other nodes).

Did anyone ran into the same issue, and what might be a solution for this? Did anything changed between WS2016 & WS2019 what might cause this?

Kind regards,

Malcolm

All replies (11)

_{Monday, August 12, 2019 8:24 AM}

Anyone?

_{Monday, August 12, 2019 10:28 AM}

Hi,

Thanks for your question.

For now, I made a test with your same situation in Win2016 Cluster. And I didn't encounter this issue, Broker Replication Storage can assign a CSV with a different owner node. I'd test Win2019 environment.   

Therefore, we'd deep troubleshoot for this issue.

1)Now, did you have two clusters in your environment? Or you copied the Hyper-V Broker role to new 2019 cluster?

2)This error occurred on the "Replication settings" of FCM console? Can you "Show Critical Events" on the role? Any error message shown?

3)Please also try to patch the latest update for the nodes to see if it works.

Highly appreciate your effort and time. If you have any question or concern, please feel free to let me know.

Best regards,

Michael 

Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]

_{Monday, August 12, 2019 12:24 PM}

Hello Michael,

Thank you for your reply and taking the time to test some things out. To reply to your questions:

*1)Now, did you have two clusters in your environment? Or you copied the Hyper-V Broker role to new 2019 cluster?
*We have multiple Clusters in our environment, and usually deploy a Replica broker per Hyper-V Cluster which usually consists of 6 to 8 Nodes. For the deployment of this Cluster I created a new broker.

*2)This error occurred on the "Replication settings" of FCM console? Can you "Show Critical Events" on the role? Any error message shown?
*Yes, the error occurred when using the FCM console (similar message when using PowerShell). Only some events that i can relate to testing (failovers, reboots, etc.) nothing related to the replica configuration.

3)Please also try to patch the latest update for the nodes to see if it works.
All nodes are at the current patch level.

Best regards,

Malcolm

_{Wednesday, August 14, 2019 3:01 AM}

Hi,

Thanks for your detailed update.

Currently, according to the testing, Broker Replication Storage can assign a CSV with a different owner node. May I ask the CSV can assign to another clustered role?

Please also check the CSV's status and the link between nodes and cluster storage.

If the issue persists, as a workaround, I suggest we can try to rebuild a Hyper-V Broker to see if it works.

Best regards,

Michael 

Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]

_{Friday, August 16, 2019 8:07 AM}

Hi,

Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

Best Regards,

Michael

Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]

_{Tuesday, August 27, 2019 6:58 AM}

Hi,

How are things going on? Was your issue resolved?

Please feel free to let me know if you need further assistance.

Best regards,

Michael

Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]

_{Wednesday, September 18, 2019 10:22 PM}

Hi Michael,

I'm experiencing this same issue.  I've removed and setup the replica broker again but this didn't help.

I've removed one of the nodes from the cluster and rebuilt it with 2016 and connected to the same SAN etc. and it works without issue.  This seems to be a Windows Server 2019 issue.

I receive an error when i attempt to configure the Replica Broker using a CSV.  "Error applying Replication configurations changes.  Unable to open specified location for replication storage.  Failed to add authorization entry.  Unable to open specified locatation to store Replica files 'C:\ClusterStorage\volumename\. Error: 0x80070057 (One or more argument are invalid).

Thanks,

Barry

_{Wednesday, October 2, 2019 8:59 PM}

Hi All,

I'm running into the same issue. Hopefully someone from MS reads this and takes appropriate action.

Some extra notes:

When selected ' start initial replication'  in the fututre, the replicationis succesfully created. But when starting initial replication it fails.

Also when using the Test-VMReplicationConnection command, it shows 'succesfull' 

Regards.

_{Wednesday, October 23, 2019 8:23 PM | 1 vote}

I got around this issue by editing the following registry key on my Server 2019 Hyper-V hosts:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\Replication\AuthorizationEntries\

ReplicaStorageLocation= Path to replica folder

_{Friday, November 22, 2019 3:40 PM}

I got around this issue by editing the following registry key on my Server 2019 Hyper-V hosts:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\Replication\AuthorizationEntries\

ReplicaStorageLocation= Path to replica folder

This worked for me as well! Thanks! You would think microsoft would be aware of their issues on 2019 Hyper-v replication.

_{Friday, February 7, 2020 11:34 AM}

I have the same issues, but not sure how to apply this reg change. On the source site there is one CSV, but the destination cluster has 2 different CSV's with the VM's partially on Volume1 and partially on Volume2. 
What would I need as "ReplicaStorageLocation" then?