Failed to bring availability group 'SQL00CansaAG01' online. The operation timed out. Verify that the local Windows Server Failover Clustering (WSFC) node is online. Msg 41131, Level 16, State 0, Line 3
---------------------------------------------------------------------------------------------------------------------Issue:-
Msg 41131, Level 16, State 0, Line 3
Failed to bring availability group 'SQL00CansaAG01' online.
The operation timed out. Verify that the local Windows Server Failover Clustering (WSFC) node is online.
Then verify that the availability group resource exists in the WSFC cluster. If the problem persists, you might need to drop the availability group and create it again.
Disconnecting connection from WIN2K8R2-3...
and in AlwaysOn....
Connecting to WIN2K8R2-3...
Msg 41066, Level 16, State 0, Line 3
Cannot bring the Windows Server Failover Clustering (WSFC) resource (ID '6d9c7675-aabb-40ab-903e-f54b5eaf472d') online (Error code 5942).
The WSFC service may not be running or may not be accessible in its current state, or the WSFC resource may not be in a state that could accept the request. For information about this error code, see "System Error Codes" in the Windows Development documentation.
Msg 41160, Level 16, State 0, Line 3
Failed to designate the local availability replica of availability group 'SQL00CansaAG01' as the primary replica. The operation encountered SQL Server error 41066 and has been terminated. Check the preceding error and the SQL Server error log for more details about the error and corrective actions.
Connecting to WIN2K8R2-3...
Msg 41131, Level 16, State 0, Line 3
Failed to bring availability group 'SQL00CansaAG01' online.
The operation timed out. Verify that the local Windows Server Failover Clustering (WSFC) node is online.
Then verify that the availability group resource exists in the WSFC cluster. If the problem persists, you might need to drop the availability group and create it again.
Disconnecting connection from WIN2K8R2-3...
Problem:-
AlwaysOn failover gets fail from Node-1 to Node-3(where Node-3 is in multisubnet environment.
Resolution:-
This error is usually caused due to the lack of permission for [NT AUTHORITY\SYSTEM] account to create the high-availability group. Running the below SQL script in all the replica secondaries fixed this issue.
Hence in order to fix this issue, give [NT AUTHORITY\SYSTEM] to sysadmin privilege.
go to the 3rd node and execute below command.
ALTER SERVER ROLE [sysadmin] ADD MEMBER [NT AUTHORITY\SYSTEM]
GO
---> The issue will get resolved.
Then you will start getting this error.
Connecting to WIN2K8R2-3...
Msg 41066, Level 16, State 0, Line 3
Cannot bring the Windows Server Failover Clustering (WSFC) resource (ID '6d9c7675-aabb-40ab-903e-f54b5eaf472d') online (Error code 5942).
The WSFC service may not be running or may not be accessible in its current state, or the WSFC resource may not be in a state that could accept the request. For information about this error code, see "System Error Codes" in the Windows Development documentation.
Msg 41160, Level 16, State 0, Line 3
Failed to designate the local availability replica of availability group 'SQL00CansaAG01' as the primary replica. The operation encountered SQL Server error 41066 and has been terminated. Check the preceding error and the SQL Server error log for more details about the error and corrective actions.
Disconnecting connection from WIN2K8R2-3...
Resolution:-
In order to solve this issue, make sure you do not have IP conflicts among the nodes and Listeners.
This Error mostly comes when Ip address conflicts occur.
so go to windows Cluster Admin and change the IP address of 2nd listener. here my earlier Listener Ip address was 192.168.2.13, which i changed to 192.168.2.200.
after doing this Issue resolved.
Thanks for reading, Hope this will help someone in resolving this issue, Kindly give a feedback..