About Me

My photo
I am MCSE in Data Management and Analytics with specialization in MS SQL Server and MCP in Azure. I have over 13+ years of experience in IT industry with expertise in data management, Azure Cloud, Data-Canter Migration, Infrastructure Architecture planning and Virtualization and automation. Contact me if you are looking for any sort of guidance in getting your Infrastructure provisioning automated through Terraform. I sometime write for a place to store my own experiences for future search and read by own blog but can hopefully help others along the way. Thanks.

The availability replica for availability group 'Win2k12AG' on this instance of SQL Server cannot become the primary replica because the WSFC cluster was started in Force Quorum mode. Consider performing a forced manual failover (with possible data loss).


Error:-
The availability replica for availability group 'Win2k12AG' on this instance of SQL Server cannot become the primary replica because the WSFC cluster was started in Force Quorum mode. Consider performing a forced manual failover (with possible data loss).



After some change in evironment SQL Server AlwaysOn was not coming up and getting fail with below error in SQL Server Errorlog file..

 

Below error Message were appearing in SQL Server errorlog file..

2017-04-04 00:53:47.850 spid29s Always On: The local replica of availability group 'Win2k12AG' is starting. This is an informational message only. No user action is required.
2017-04-04 00:53:54.910 spid54 Always On: The local replica of availability group 'Win2k12AG' is preparing to transition to the primary role in response to a request from the Windows Server Failover Clustering (WSFC) cluster. This is an informational message only. No user action is required.
2017-04-04 00:53:54.980 spid54 The availability replica for availability group 'Win2k12AG' on this instance of SQL Server cannot become the primary replica because the WSFC cluster was started in Force Quorum mode. Consider performing a forced manual failover (with possible data loss).
2017-04-04 00:53:55.880 spid54 Always On: The local replica of availability group 'Win2k12AG' is preparing to transition to the resolving role in response to a request from the Windows Server Failover Clustering (WSFC) cluster. This is an informational message only. No user action is required.
2017-04-04 00:53:56.610 spid54 Always On: The local replica of availability group 'Win2k12AG' is preparing to transition to the primary role in response to a request from the Windows Server Failover Clustering (WSFC) cluster. This is an informational message only. No user action is required.
2017-04-04 00:53:56.650 spid54 The availability replica for availability group 'Win2k12AG' on this instance of SQL Server cannot become the primary replica because the WSFC cluster was started in Force Quorum mode. Consider performing a forced manual failover (with possible data loss).
2017-04-04 00:53:57.590 spid54 Always On: The local replica of availability group 'Win2k12AG' is preparing to transition to the resolving role in response to a request from the Windows Server Failover Clustering (WSFC) cluster. This is an informational message only. No user action is required.
2017-04-04 00:55:01.680 spid54 Always On: The local replica of availability group 'Win2k12AG' is preparing to transition to the primary role in response to a request from the Windows Server Failover Clustering (WSFC) cluster. This is an informational message only. No user action is required.
2017-04-04 00:55:01.690 spid54 The availability replica for availability group 'Win2k12AG' on this instance of SQL Server cannot become the primary replica because the WSFC cluster was started in Force Quorum mode. Consider performing a forced manual failover (with possible data loss).
2017-04-04 00:55:02.670 spid54 Always On: The local replica of availability group 'Win2k12AG' is preparing to transition to the resolving role in response to a request from the Windows Server Failover Clustering (WSFC) cluster. This is an informational message only. No user action is required. 


Based on above error it looks Windows team has stated Cluster services in force quorum mode on one of participating node..

Resolution:-

I tried to offline Cluster core resource and brought online -- No Luck
I did telnet all SQL server ports among each other -- Port was getting telnet.
I tried to stop cluster service and start it again on each node -- No Luck.

In order to troubleshhot this issue.. I executed below command from Curent primary replica to failover to another node and issue resolved

--- YOU MUST EXECUTE THE FOLLOWING SCRIPT IN SQLCMD MODE.
:Connect WIN2K12-1
ALTER AVAILABILITY GROUP [Win2k12AG] FORCE_FAILOVER_ALLOW_DATA_LOSS;
GO

GO


Thanks for reading...