Share via

Recreating Exchange FSW in 2 member DAG

Rachel N 66 Reputation points
2022-01-11T22:16:02.767+00:00

I have a 2 member Exchange 2019 DAG with a third file server serving as the File Witness Server. After the last round of Windows updates, the DAG lost connection to the FSW quorum server and I couldn't bring it back online in Failover Cluster Manager or start it in Exchange Start-ClusterResource as it failed with the error "The cluster resource could not be brought online by the resource monitor".

I attempted to rebuild the File Share Witness resource via Set-DatabaseAvailabilityGroup back to the original values, but I got the error and now I am missing the FSW resource under Cluster Core Resources entirely.
There was a problem changing the quorum model for database availability group Exch-2019-DAG. Error: An error occurred while attempting a cluster operation. Error: Cluster API failed: "ClusterResourceControl(controlcode=CLUSCTL_RESOURCE_SET_PRIVATE_PROPERTIES) failed with 0x533. Error: This user can't sign in because this account is currently disabled"

Does anyone know how to get around the account currently disabled issue? I checked the Cluster Name Object in AD and it is disabled, but I think it is supposed to be that way.

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,412 questions
Accepted answer
  1. Andy David - MVP 142.9K Reputation points MVP
    2022-01-11T22:40:18.65+00:00

    See:
    https://social.technet.microsoft.com/Forums/office/en-US/8daace30-490f-4f4d-96b7-a687260fe4ec/quorumgroupfilesharequorum-failed?forum=exchangesvravailabilityandisasterrecovery

    he following solution has been provided to resolve your issue:

    Unable to bring the FSW of the DAG online..

    A summary of the solution is detailed below:

    Symptom - FSW cannot come online from the Failover Cluster Manager

    Cause - CNO password out of sync with AD

    Resolution - Gave currently logged on user full permissions to the CNO and did a repair from Failover Cluster Manager and then created a new FSW

    https://blog.subvertallmedia.com/2012/12/06/repairing-a-failover-cluster-in-windows-server-2012-live-migration-fails-dns-cluster-name-errors/

    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rachel N 66 Reputation points
    2022-01-12T15:35:03.88+00:00

    Well, I finally worked up the nerve to enable the CNO in AD, and for whatever reason it enabled flawlessly and let the commands to update the quorum run. So now we have a FSW again, it is showing in both failover cluster manager and in Exchange powershell, and it popped up a nice new GUID folder with the witness file on it on the witness server.

    1 person found this answer helpful.
  2. Rachel N 66 Reputation points
    2022-01-11T22:55:40.87+00:00

    I'm using a domain admin account to manage this, but just in case I gave the user explicit Full permissions on the CNO computer object but I'm still getting the error whenever I try to create a new FSW:

    There was a problem changing the quorum model for database availability group Exch-2019-DAG. Error: An error occurred while attempting a cluster
    operation. Error: Cluster API failed: "ClusterResourceControl(controlcode=CLUSCTL_RESOURCE_SET_PRIVATE_PROPERTIES) failed with 0x533. Error: This
    user can't sign in because this account is currently disabled"

    Do I have to enable the Exchange CNO in Active Directory in order to edit it?