Unable to add DAG member server in exchange 2019

Question

Unable to add DAG member server in exchange 2019

Nur Hossain 282

Need help,

I am getting following error message, while adding member server in existing DAG.

ERROR
A server-side database availability group administrative operation failed. Error The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: Windows Failover Clustering isn't installed on 'UDRPMPRD1'.. [Server: UDCPMPRD3.xyz.com.bd]

Sharon Zhao-MSFT 25,756 Reputation points Microsoft External Staff

2020-09-08T07:29:10.46+00:00

@Nur Hossain ，
According to your description, this issue is more related to Exchange. I would remove the tag of office-teams-windows-itpro. Hope you get better response.
Lucas Liu-MSFT 6,191 Reputation points

2020-09-15T09:06:20.237+00:00

Hi @Nur Hossain ,
I am writing here to confirm with you how thing going now? If the above suggestion helps, please click “Accept as answer” to mark helpful reply as an answer.Your action would be helpful to other users who encounter the same issue and read this thread.
Thanks for your understanding.

----------

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

4 answers

Your answer

Sharon Zhao-MSFT 25,756 Reputation points Microsoft External Staff

2020-09-08T07:29:10.46+00:00

@Nur Hossain ，
According to your description, this issue is more related to Exchange. I would remove the tag of office-teams-windows-itpro. Hope you get better response.
Lucas Liu-MSFT 6,191 Reputation points

2020-09-15T09:06:20.237+00:00

Hi @Nur Hossain ,
I am writing here to confirm with you how thing going now? If the above suggestion helps, please click “Accept as answer” to mark helpful reply as an answer.Your action would be helpful to other users who encounter the same issue and read this thread.
Thanks for your understanding.

----------

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 1

SHAMBHU SHARMA 26

In my case, cluster were corrupted on problematic server and I follow below solution:
If you face same problem in Exchange 2019 server:

Clear-ClusterNode -Name XXXXXX (Problematic Server) -Force (PowerShall)

Restart the server

Add-DatabaseAvailabilityGroupServer -Identity “DAG Name” -MailboxServer XXXXXX(Problematic Server)

Server should be added and validate the DAG members and FileShare.

Answer 2

Hi,

Could you please provide more information,

Detailed version of exchange server, Get-ExchangeServer | select AdminDisplayVersion

Please check the below,

Check whether the OS is same as the node which is part of DAG
Check the network adapter configuration on the node trying to add to the DAG
Are you able to ping the node trying to add
Firewall communication between the existing and the new member - cluster port, etc
Pre-requisites are properly installed on the second node trying to add
IP DAG or IP-Less DAG?
Try installing windows failover cluster from server manager and then try adding the node to the member
Try disabling IPv6 on the second node and add it

Answer 3

Hi @Nur Hossain ,

Please run the following first command to check if the Windows Failover Clustering is installed on “UDRPMPRD1”. If not, please run the second command to install the Windows Failover Clustering on “UDRPMPRD1”. And please note that after installation you need to reboot the server to complete the installation.

Get-WindowsFeature Failover-Clustering
Install-WindowsFeature Failover-Clustering

2.According to my research, enabling IPv6 may also could cause this issue. So please try to disable the IPv6 and try to add DAG member server again. You could following the steps to disable the IPv6.

Open the registry and navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\
Set the max value of DisabledComponents to 0xFF, if DisabledComponents does not exist, please create a named DisabledComponents with the type of REG_DWORD and set it.
Reboot the server. Please note: If you modify the registry incorrectly, serious problems may occur. Before making changes, please back up the registry to restore it, just in case something goes wrong. For more information you could refer to: Guidance for configuring IPv6 in Windows and How to back up and restore the registry in Windows.

If the response is helpful, please click "Accept Answer" and upvote it. Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Lucas Liu-MSFT 6,191 Reputation points

2020-09-11T05:38:37.413+00:00

Hi @Nur Hossain ,
Do suggestions above help? If the issue has been resolved, please click “Accept as answer” to mark helpful reply as an answer, this will make answer searching in the forum easier and be beneficial to other community members as well.
Thanks for your understanding.

----------

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 4

Edward van Biljon 6 Volunteer Moderator

When you added the server to the DAG, did it not install Failover Clustering? I have seen it sometimes fail if there were changes done like windows updates and after a reboot it works or if you have a larger environment maybe your AD replication has not gone through yet?

Share via

Unable to add DAG member server in exchange 2019

4 answers

Your answer