Err Remove-DatabaseAvailabilityGroupServer from DAG

Sergey Potemkin 21

Hello guys,

I've cought the problem: cannot remove one of three servers from the DAG Exchange 2019.

The details from operation log are:

SetFswSharePath() caught an AmClusterApiException with errorcode=-2147467259 and NativeErrorCode=1168. ex = System.ComponentModel.Win32Exception (0x80004005): Element not found

WriteError! Exception = Microsoft.Exchange.Management.Tasks.DagTaskProblemChangingQuorumException: There was a problem changing the quorum model for database availability group <DAGNAME>. Error: An error occurred while attempting a cluster operation. Error: Cluster API failed: "ClusterResourceControl(controlcode=CLUSCTL_RESOURCE_SET_PRIVATE_PROPERTIES) failed with 0x490. Error: Element not found"

I Googled online for a few days, but no one had anything like that. In other respects, the servers work without any visible problems.

KyleXu-MSFT 26,266 Reputation points

2021-10-12T05:56:42.797+00:00

@Sergey Potemkin

Did you successfully delete the node from the DAG?
If the suggestion below helps, please be free to accept it as an answer for helping more people.
Sergey Potemkin 21 Reputation points

2021-10-14T12:28:08.473+00:00

Dear KyleXu-MSFT,

They wait from the Microsoft Employee the proper answer for the question.

Accepted answer

Sergey Potemkin 86 Reputation points

2022-04-06T22:10:48.46+00:00

Finale:
It seems, the problem have been related to the authorization of the Remove-DatabaseAvailabilityGroupServer execution.
Despite the fact that access to all objects of the DAG cluster was done correctly, and rechecking everything and everywhere did not give any result.

In the result the studying many forums on similar cluster problems led to the idea that I need to manually change the quorum type Set-ClusterQuorum -NodeAndFileShareMajority [path] -Credential (Get-Credential).

Then Remove-DatabaseAvailabilityGroupServer has been executed without failures
Please sign in to rate this answer.

2 people found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

4 additional answers

Amit Singh 4,901 Reputation points

2021-10-19T10:52:06.693+00:00
I have done some research on your error messages, and there are many potential causes for Cluster communication failures, including:

Network latency

Network outages

Faulty drivers or network cards, including TCP offload issues

Misconfigured firewall rules

Security software such as anti-virus, intrusion detection, etc.

Solutions in the articles for your reference: Failover Cluster Communication Failures and Troubleshooting cluster issue with Event ID 1135
In addition, if all of the above solutions don't work, seek a windows server expert for support.

Also if you need to recover failed member of a database availability group? Read this guide.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Andy David - MVP 149.2K Reputation points MVP

2021-10-11T17:07:01.23+00:00
This still applies:
https://practical365.com/unable-remove-failed-server-dag-exchange-server-2010/

Remove-DatabaseAvailabilityGroupServer -Identity DAG -MailboxServer EX2 -ConfigurationOnly Import-Module FailoverClusters Get-ClusterNode EX2 | Remove-ClusterNode -Force
Please sign in to rate this answer.
Sergey Potemkin 21 Reputation points

2021-10-14T12:23:32.503+00:00

Thanks Andy,

Not sure that after the "force" methods the DAG will be setted up properly. I mean the quorum FSW.

I'll put aside this as the last option.

Have you had an experience of the reducing DAG servers from 3 to 2 with FWS quorum ?

Andy David - MVP 149.2K Reputation points MVP

2021-10-14T12:41:44.843+00:00

Yes, I have done this in the past.

What will set the quorum type will be the first command, but ensure that you have quorum when you run it. In other words, ensure the other two servers are up and the FSW is defined already ( It should be)
Of course, no guarantees this will work - no can guarantee that! But this is what has worked for me in the past

Remove-DatabaseAvailabilityGroupServer -Identity DAG -MailboxServer EX2 -ConfigurationOnly

Sergey Potemkin 21 Reputation points

2021-10-14T13:54:49.937+00:00

That is the point!
The Remove-DatabaseAvailabilityGroupServer -Identity DAG -MailboxServer EX2 returns errors regarding FSW:

SetFswSharePath() caught an AmClusterApiException with errorcode=-2147467259 and NativeErrorCode=1168. ex = System.ComponentModel.Win32Exception (0x80004005): Element not found

I've tried to get results with the -ConfigurationOnly. It removes the server from DAG on Exchange level, but do nothing with the FSW. The cluster stays with two nodes without FSW, althow the witnessserver and witnessdirectory are configured in the Exschange DAG...

Andy David - MVP 149.2K Reputation points MVP

2021-10-14T14:26:59.107+00:00

So you have run the command with the -ConfigurationOnly switch? But not the Get-ClusterNode EX2 | Remove-ClusterNode -Force ?

If you run set-DatabaseAvailabilityGroup with no switches, what happens?

Sergey Potemkin 21 Reputation points

2022-04-06T22:21:16.893+00:00

Hi Andy,

You may want to see the solution below - marked as the answer.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Limitless Technology 39,676 Reputation points

2021-10-12T07:26:15.033+00:00

Hello @Sergey Potemkin

There is an official Microsoft article that is providing exact steps about best practice how to remove Database Availability Group Server:

Remove-DatabaseAvailabilityGroupServer
https://learn.microsoft.com/en-us/powershell/module/exchange/remove-databaseavailabilitygroupserver?view=exchange-ps

Try following the steps by adjusting the commands to your needs and see if it gives you the result you are expecting.

Hope this helps with your query!

---------
--If the reply is helpful, please Upvote and Accept as answer--
Please sign in to rate this answer.
Sergey Potemkin 21 Reputation points

2021-10-14T12:10:54.537+00:00

If this question could be resolved with the help of documentation, I wouldn't ask....

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
KyleXu-MSFT 26,266 Reputation points

2021-10-21T07:26:15.29+00:00

I deploy a two nodes DAG recently, the Witness Server doesn't show as a node in the Windows Cluster:

Witness is being used:

So, it is an expected behavior that Witness isn't a node.
Please sign in to rate this answer.
Dipto Adhikary 20 Reputation points

2024-07-30T17:58:12.67+00:00

I have an Exchange Server environment with Exchange Server 2016, consisting of two mailbox servers in the DC site and two in the DR site, configured in a DAG named "dag01." Currently, I am migrating to Exchange Server 2019. As part of the migration, I have deployed a similar setup with two mailbox servers in the DC site and two in the DR site for Exchange 2019, with a new DAG named "dag02." Both DAGs are IP-less and exist in the same Active Directory forest, but with different witness servers and directories, and the mailbox servers and databases are separate from the Exchange 2016 environment.

After configuring the new DAG (dag02) in the Exchange Server 2019 environment, it appears to be working correctly. However, when I run the following command:

Get-DatabaseAvailabilityGroup -Status | ft Name, Witness*, Servers

I get the following output:

For dag01:

WitnessShareInUse : None

For dag02:

WitnessShareInUse : Primary

Previously, dag01 had its WitnessShareInUse status set to "Primary." Additionally, the VerifyShareWriteAccess.txt and Witness.log files are missing from GUID folder in dag01's witness share after creating dag02.

My questions are:

Why has the status of dag01 changed to "None"?

Does this status change indicate any issues with the functionality of dag01?

How can I set the WitnessShareInUse status to "Primary" for both DAGs, or how can I resolve this issue?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Err Remove-DatabaseAvailabilityGroupServer from DAG

4 additional answers

Your answer