Microsoft distributes Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release.
Assume that you try to create multiple availability groups in a Microsoft SQL Server 2012 AlwaysOnfailover clustering environment. Each availability group contains multiple availability databases. In this scenario, non-yield scheduler events may occur in SQL Server. When this issue occurs, error events that resemble the following are logged in the SQL Server Error log file:
Date Time Process Error: 41009, Severity: 16, State: 5.
Date Time Process The Windows Server Failover Clustering (WSFC) resource control API returned error code 5908. The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
Date Time Server * Non-yielding Scheduler
Date Time Server *
Date Time Server * *******************************************************************************
Date Time Server Stack Signature for the dump is 0x00000000000001BF
Date Time Server Error: 19407, Severity: 16, State: 1.
Date Time Server The lease between availability group 'NAMCRMS001AG00' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster.
Date Time Server AlwaysOn: The local replica of availability group 'NAMCRMS001AG00' is going offline because either the lease expired or lease renewal failed. This is an informational message only. No user action is required.
Date Time Server The state of the local availability replica in availability group 'NAMCRMS001AG00' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
This issue occurs because a cluster API call by SQL Server was not responded to by the Windows failover cluster.
Cumulative update information
SQL Server 2012
The fix for this issue was first released in Cumulative Update 2 for SQL Server 2012 Service Pack RTM. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2703275 Cumulative update package 2 for SQL Server 2012Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released Microsoft SQL Server 2012 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2012 Service Pack RTM hotfix to an installation of SQL Server 2012 Service Pack RTM. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about AlwaysOn Availability Groups, go to the following MSDN website: