Basic Availability setup but replicas went to resolving state RRS feed

  • Question

  • Hi,

    I configured the Basic Alwayson setup in two of the test SQL standard 2017 test servers(A,B). 
    As per basic configuration only one db i am able to add it in group. Configuration everything went well with automatic failover from primary-A to secondary-B once i off the sql services in primary server. Now secondary-B is primary became primary. 
    I started the sql services in previous A server and off the services in B services.But here instead of failover both servers went to Resolving mode.  To resolve this i on the sql service in B server i waited for whole night whether dbs will sync.I even tried force failover but Nothing worked. 
    Now both servers are in resolving state. Not able to understand what to do now. 
    The error i am getting as below 

    the availability replica for availability group xyz on this instance of sql server can  not become the primary replica because the wsfc cluster was started in force quorum mode.consider performing a forced manua failover (with possible data loss) error 41125. 

    I check the WSFC - Ag Role XYZ failed. 
    Both nodes are up. 

    Now both replicas went to resolve state..:(

    Anything i need to check? Please suggest. 


    • Edited by joo123 Tuesday, November 12, 2019 7:18 AM
    Tuesday, November 12, 2019 7:07 AM


  • Hi joo123,

    >> Now both servers are in resolving state. Not able to understand what to do now.

    I test it in my environment, please try to start your AG Role XYZ manually from Failover Cluster Manger by choosing the Start Role option or Move to Best Possible Node as below screenshot. And please also start the SQL service in your SQL server B. AG is become synchronized in my environment. 

    Best regards,

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to  MSDN Support, feel free to contact

    Wednesday, November 13, 2019 3:48 AM