Unable to Remove Failed Server from DAG in Exchange Server 2010

When an Exchange Server 2010 Mailbox server that is a member of a Database Availability Group has failed, part of the recovery process is to remove it from DAG membership.

In some scenarios this process may result in an error “A quorum of cluster nodes was not present to form a cluster“.  The full error text is below.

[PS] C:\>Remove-DatabaseAvailabilityGroupServer -Identity DAG -MailboxServer EX2

Confirm
Are you sure you want to perform this action?
Removing Mailbox server "EX2" from database availability group "dag".
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): y
WARNING: The operation wasn't successful because an error was encountered. You may find more details in log file
"C:\ExchangeSetupLogs\DagTasks\dagtask_2010-11-25_03-48-09.814_remove-databaseavailabiltygroupserver.log".
There was a problem changing the quorum model for database availability group dag. Error: An Active Manager operation f
ailed. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"SetClusterQuorumResource() f
ailed with 0x1725. Error: A quorum of cluster nodes was not present to form a cluster"' failed..
    + CategoryInfo          : InvalidArgument: (:) [Remove-DatabaseAvailabilityGroupServer], DagTaskProblemChangingQuo
   rumException
    + FullyQualifiedErrorId : 80D96894,Microsoft.Exchange.Management.SystemConfigurationTasks.RemoveDatabaseAvailabili
   tyGroupServer

To resolve this issue use the -ConfigurationOnly switch instead to remove the failed Mailbox server from the Exchange 2010 DAG.  In this example server EX2 is being removed.

[PS] C:\>Remove-DatabaseAvailabilityGroupServer -Identity DAG -MailboxServer EX2 -ConfigurationOnly

Next, evict the failed node from the Windows Failover Cluster.

Note: you need to import the Failover Cluster module into your Exchange Management Shell session to perform this task.

[PS] C:\>Import-Module FailoverClusters
[PS] C:\>Get-ClusterNode EX2 | Remove-ClusterNode -Force

The failed server has now been removed from the Exchange 2010 DAG and the Windows Failover Cluster.

About Paul Cunningham

Paul is a Microsoft Exchange Server MVP and publisher of Exchange Server Pro. He also holds several Microsoft certifications including for Exchange Server 2007, 2010 and 2013. Connect with Paul on Twitter and Google+.

Comments

  1. Great post! It works like a champ…!

  2. Hi

    I am trying to import Import-Module FailoverClusters but msem shell is not getting this command please help

    Thanks

    • what is “msem”?

      The command is a PowerShell command and should work on a Windows 2008 R2 server that is an Exchange 2010 DAG member.

      • Hi
        msem is microsoft excange management shell, Actually i was Using Pssession from local machine
        Thank you so much it works from Dag member.

  3. Thanks sir, this was a great help today!

  4. I have an two exchange 2010 sp2 multi-role servers. In EMC it shows the replication is up to date with no queue built up. However, the DR server shows in the event viewer.

    “passive/active copy is not UP according to clustering”

    In cluster failover management the node shows as offline and so does the NIC. Both are online and the replication seems to be fine. The primary dag server shows all is well. Can I use the above to remove and readd the recovery exchange server? Do I need to remove all DB copies first or can I just execute the commands above and it will take care of it?

  5. You have no idea how this helped. I couldn’t remove the member server from DAG because Windows Cluster Service would not start. Thanks!

  6. Hi Paul and Thanks Again
    In my cluster and DAG everything was OK
    situation is :
    Two Ex 2010 SP1 in the DAG (mailbox01 and Mailbox02) and Two SP3 Added to DAG (mailbox1 and Mailbox2)
    Now I want to remove the previous ones

    but this error show up again and again while removing mailbox01 with no database copy on it

    anyway i used first cmdlet
    [PS] C:\>Remove-DatabaseAvailabilityGroupServer -Identity DAG -MailboxServer Mailbox0X2 -ConfigurationOnly

    and it is removed from DAG but second ones

    [PS] C:\Windows\system32>Get-ClusterNetwork Maibox01 | Remove-ClusterNode -Force
    Get-ClusterNetwork : Failed to retrieve the network ‘Maibox01′ from the cluster ‘DAG’.
    An error occurred opening network ‘Maibox01′.
    The cluster network was not found
    At line:1 char:19

    do not work, give me following error and the server is not removed from windows failover cluster

    • oh sorry
      i had no patience :)
      just needed some time maybe to clear the configurations from the cluster and then it worked
      i think you should mention that some time is needed between running those commands ;)

  7. Baffajo Beita says:

    Always on point! your articles always work!

  8. Erik Santos says:

    Paul.. great help!
    Thanks

  9. Rune Goksør says:

    I ran these commands on a server that was still in the environment but halfway uninstalled from before. I was unable to uninstall Exchange 2013 from this “orphan” server after running the commands in this article because the server seemed to think that it was still a part of the DAG. MS helped me out with running this command first on one of the servers that is left in the DAG:

    cluster node ORPHAN-MBX /forcecleanup

    After that I could uninstall Exchange from this “orphan” server, and thus clean up AD properly.

  10. Thanks so much Paul , your always helpful for me .

    God blesses you,

    imran safi
    from afghanistan

Leave a Comment

*

We are an Authorized DigiCert™ SSL Partner.