Adding member to DAG error

Deleted
Not applicable

Hey all,

 

Details first:

2 x Server 2022 each with Exchange 2019 CU13, different subnets.

 

I created a DAG.  Created a DAG network with the subnets the two servers are in.

 

I added one server as a member no worries.  When attempting to add the second server I get this error.

 

A server-side database availability group administrative operation failed. Error The operation failed.
CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation.
Error: Cluster API failed: "AddClusterNode() (MaxPercentage=12) failed with 0x80070005. Error: Access is denied".
[Server: first-server.domain]

 

Looking through logs there is no indication what access is being denied where.  I can see a thousand other queries online with this exact error but none of the suggested solutions seem to solve my issue.

 

The share and folder security on the Witness server shared folder has permissions set for the Exchange Trusted Subsystem.  I added permissions for the 2 exchange servers to the DAG computer object as per somewhere online.  Our existing 2013 servers are in a dag and are all on the same subnets, so no firewall or network connectivity issues.

 

Anyone have any other theories?

 

thanks

 

jc

3 Replies

Hi @Deleted 

 

The Exchange 2019 Servers are in the same Subnet for DAG and can ping each other?

IP-Less DAG or with fixed IP?

 

https://learn.microsoft.com/en-us/exchange/high-availability/database-availability-groups/database-availability-groups?view=exchserver-2019 

 

Did you try to add DAG Member with PowerShell (try also the Verbose Parameter)

Add-DatabaseAvailabilityGroupServer -Identity DAG1 -MailboxServer EX2

Add-DatabaseAvailabilityGroupServer -Identity DAG1 -MailboxServer EX2 -Verbose


Regards

Andres

 

Thanks for the reply@Andres Bohren 

 

The Exchange Servers are in different subnets:

192.168.20.10 (main)

192.168.30.10 (DR)

 

The DAG has the following IP addresses specified:

192.168.20.11

192.168.30.11

 

Only one network per server (no separate replication network).  The DR one is the one that won't join the cluster.  The DR server can ping both IP's of the main server (MAPI and cluster assigned IP), the main server can ping the DR IP.

 

I tried setting the DAG network to be manually configured and added the subnets.

 

Here is some more info from the dagtasks log:

WriteError! Exception = Microsoft.Exchange.Cluster.Replay.DagTaskOperationFailedException: A server-side database availability group administrative operation failed. Error The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API failed: "AddClusterNode() (MaxPercentage=12) failed with 0x80070005. Error: Access is denied". ---> Microsoft.Exchange.Cluster.Shared.ClusterApiException: An error occurred while attempting a cluster operation. Error: Cluster API failed: "AddClusterNode() (MaxPercentage=12) failed with 0x80070005. Error: Access is denied" ---> System.ComponentModel.Win32Exception: Access is denied

 

I tried running the powershell command from both servers and get the same error on both.  The Verbose command doesn't give any more info.

Seems there are other issues with that DR server probably causing the cluster issue.

whatwaht_0-1685415592098.png

 

Another Windows issue with dozens of solutions online that don't work!

 

The two servers where installed using the same Server 2022 iso.

 

The main Exchange server was installed using the CU12 iso then patched to CU13.  The DR Exchange was then installed using the CU13 iso.  Don't know if that makes any difference.