SQL Server Always On Series – Exposing SQL Server Always On Downtime @jbswiki #sqlserver #sql

Channel	Publish Date	Thumbnail & View Count	Download Video
	Publish Date not found	0 Views	View on YouTube Download Video

SQL Server Always On Series – Uncovering SQL Server Always On Downtime: Fixing the Resolution Status Issue

Event ID: 41144
The local availability replica of availability group 'JBSAG' is in an error state. The replica could not read or update the persistent configuration data (SQL Server Error: 41005). To resolve this error, restart either the local Windows Server Failover Clustering (WSFC) service or the local instance of SQL Server.

Event ID: 1205
The Cluster service could not bring the cluster role 'JBSAG' completely online or offline. One or more resources may be in an unhealthy state, which may affect the availability of the cluster role.

Event ID: 1069
The cluster resource 'JBSAG' of type 'SQL Server Availability Group' in the cluster role 'JBSAG' failed.
Based on the failure policies for the resource and role, the cluster service can attempt to bring the resource online on that node or move the group to another node in the cluster and then restart it.

Event ID: 7043
The cluster service did not shut down properly after receiving a preshutdown control.

Error: 41022, Severity: 16, Status: 0.
Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (error code 5073). If this is a WSFC availability group, the WSFC service might not be running or inaccessible in its current state, or the arguments provided might be invalid. Otherwise, contact your primary support provider. For information about this error code, see /"System Error Codes/" in the Windows Development documentation.
Always On: The Availability Replica Manager is going offline because the local Windows Server Failover Clustering (WSFC) node has lost quorum. This is an informational message only. No user action is required.
Always On: The local replica of availability group JBSAG is stopped. This is an informational message only. No user action is required.

Error: 41066, Severity: 16, Status: 0.
The Windows Server Failover Clustering (WSFC) resource (ID 'ee50bbc1-93ab-4f25-85e5-a7d245555183') cannot be brought online (error code 126). If this is a WSFC availability group, the WSFC service might not be running or accessible in its current state, or the WSFC resource might not be in a state to accept the request. Otherwise, contact your primary support provider. For information about this error code, see "System Error Codes" in the Windows Development documentation.

Error: 41160, Severity: 16, Status: 0.
The local availability replica of availability group 'JBSAG' could not be made primary. The operation encountered SQL Server error 41066 and terminated. See the preceding error and the SQL Server error log for more information about the error and corrective actions.

Error: 41017, Severity: 16, Status: 1.
A node could not be added to the list of possible owners of a Windows Server Failover Clustering (WSFC) resource (error code 5908). If this is a WSFC availability group, the WSFC service might not be running or accessible in its current state, or the specified cluster resource or node handle is invalid. Otherwise, contact your primary support provider.

Understanding the problem:
Imagine the following scenario: your SQL Server environment is running smoothly, but suddenly the dreaded /"Resolving/" state occurs. Your system is in limbo and downtime is piling up. Don't panic – we're here for you! The /"Resolving/" state, often accompanied by error codes 41066 and 41160, is an obstacle that can disrupt your operations. In this video, we analyze this problem to help you regain control of your SQL Server environment.

Common causes:
It is important to understand the root causes. We will explore the possible reasons for the /"Resolving/" status. Perhaps the WSFC service is not running or inaccessible, or the resource status is uncooperative.

Step-by-step solution:
Now let's get to the exciting part – the solution! We will walk you through a systematic process to troubleshoot and resolve the Resolving status. From checking the status of the WSFC service to validating the status of the WSFC resource, we will leave no stone unturned.

️ Preventive measures:
Fixing the problem is important, but preventing it from happening again is equally important. Finally, we'll share best practices and preventative measures that you can use to proactively maintain the integrity of your availability groups.

Conclusion and call to action:
To conclude this journey through the dangerous waters of the Resolving state in Always On Availability Groups, we have demystified error messages, uncovered root causes, and equipped you with an effective solution. Remember, every challenge is an opportunity for growth. Armed with the knowledge gained from this video, you'll be ready to overcome even the most difficult database obstacles.