Cannot bring the Windows Server Failover Clustering (WSFC) resource (ID ‘xxxxxxxxxxxxx’) 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.
Failed to designate the local availability replica of availability group ‘xxxxxxx’ 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. (.Net SqlClient Data Provider)

Clustered role ‘xxxxxxx’ has exceeded its failover threshold. It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state. No additional attempts will be made to bring the role online or fail it over to another node in the cluster. Please check the events associated with the failure. After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.

The Cluster service failed to bring clustered role ‘xxxxxxxx’ completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role.

Cluster resource ‘xxxxxx’ of type ‘SQL Server Availability Group’ in clustered role ‘xxxxxx’ failed.

Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

Failed to bring the resource “xxxxxxxxx” online (IP Address)

Unable to do manual failover. Unable to bring database back online. Unable to bring Role back online in Cluster Manager, even after server reboot and cluster restart.


Cluster IP setting for the AG and the listener was not updated correctly.

The IP was updated, but the network was wrong.

Possible Fix:

Fix IP address for AG and listener.

Last modified: April 5, 2022



Write a Reply or Comment