Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: You take a long time to stop the SQL Server service and you cannot restart the SQL Server service in a Microsoft SQL Server 2008 cluster environment when the server is under stress

FIX: You take a long time to stop the SQL Server service and you cannot restart the SQL Server service in a Microsoft SQL Server 2008 cluster environment when the server is under stress

Microsoft distributes Microsoft SQL Server 2008 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 2008 fix release.

↑ Back to the top

Symptoms

In a Microsoft SQL Server 2008 cluster environment, the SQL Server service takes a long time to stop when there is a high load on the server. Additionally, the service state is changed to "Stop Pending" and you cannot restart the SQL Server service. You also find error messages that resemble the following are logged in the Windows Cluster log:

[RES] SQL Server <SQL Server (SQL1)>: [sqsrvres] SvcStop: Sending first Stop signal to service.

[RHS] RhsCall::DeadlockMonitor: Call TERMINATERESOURCE timed out for resource 'SQL Server (SQL1)'.

[RHS] Resource SQL Server (SQL1) handling deadlock. Cleaning current operation and terminaiting RHS process

00001858.00003154::Date Time WARN [RHS] Resource SQL Server IsAlive has indicated failure.

00001bfc.000041a4::Date Time INFO [RCM] HandleMonitorReply: FAILURENOTIFICATION for 'SQL Server', gen(0) result 1.

00001bfc.000041a4::Date Time INFO [RCM] TransitionToState(SQL Server) Online-->ProcessingFailure.

00001bfc.000069d8::Date Time ERR [RCM] rcm::RcmResource::HandleFailure: (SQL Server)

00001bfc.000069d8::Date Time INFO [RCM] resource SQL Server: failure count: 1, restartAction: 2.

00001bfc.000069d8::Date Time INFO [RCM] Will restart resource in 500 milliseconds.

00001bfc.000069d8::Date Time INFO [RCM] TransitionToState(SQL Server) ProcessingFailure-->[Terminating to DelayRestartingResource].

00001bfc.000069d8::Date Time INFO [RCM] rcm::RcmGroup::ProcessStateChange: (SQL Server (MSSQLSERVER), Online --> Pending)

00001bfc.000069d8::Date Time INFO [RCM] TransitionToState(SQL Server Agent) Online-->[Terminating to OnlineCallIssued].

00001bfc.000087fc::Date Time INFO [RCM] Restarting resource 'SQL Server Agent'.

00001858.00008f58::Date Time ERR [RES] SQL Server <SQL Server>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed

00001858.00008f58::Date Time ERR [RES] SQL Server <SQL Server>: [sqsrvres] printODBCError: sqlstate = HYT00; native error = 0; message = …..

00001858.00008f58::Date Time INFO [RES] SQL Server <SQL Server>: [sqsrvres] OnlineThread: asked to terminate while waiting for QP.

00001858.00001924::Date Time ERR [RHS] RhsCall::DeadlockMonitor: Call TERMINATERESOURCE timed out for resource 'SQL Server'.

00001858.00001924::Date Time ERR [RHS] Resource SQL Server handling deadlock. Cleaning current operation and terminaiting RHS process.

00001bfc.0000e7dc::Date Time INFO [RCM] HandleMonitorReply: FAILURENOTIFICATION for 'SQL Server', gen(1) result 4.

00001bfc.0000e7dc::Date Time INFO [RCM] rcm::RcmResource::HandleMonitorReply: Resource 'SQL Server' consecutive failure count 1.

00001bfc.0000e7dc::Date Time ERR [RCM] rcm::RcmMonitor::RecoverProcess: Recovering monitor process 0x1858.

00001bfc.0000e7dc::Date Time INFO [RCM] Created monitor process 28164 / 0x6e04

00006e04.0000e8a4::Date Time INFO [RHS] Initializing.

00001bfc.0000e7dc::Date Time INFO [RCM] rcm::RcmResource::ReattachToMonitorProcess: (SQL Server, [Terminating to DelayRestartingResource])

00001bfc.0000e7dc::Date Time INFO [RCM] TransitionToState(SQL Server) Initializing-->OpenCallIssued.

00001bfc.00004878::Date Time INFO [RCM] TransitionToState(SQL Server) [Terminating to DelayRestartingResource]-->DelayRestartingResource.

00001bfc.00004878::Date Time INFO [RCM] Delay-restarting SQL Server and any waiting dependents.

00001bfc.00004878::Date Time INFO [RCM] TransitionToState(SQL Server) DelayRestartingResource-->OnlineCallIssued.

00001bfc.0000e7dc::Date Time INFO [RCM] HandleMonitorReply: ONLINERESOURCE for 'SQL Server', gen(1) result 997.

00001bfc.0000e7dc::Date Time INFO [RCM] TransitionToState(SQL Server) OnlineCallIssued-->OnlinePending.

00006e04.00003478::Date Time INFO [RHS] Resource SQL Server has come online. RHS is about to report status change to RCM

↑ Back to the top

Cause

When the cluster service checks the status of the SQL Server service, the cluster service runs the IsAlive query. If the IsAlive query times out, the cluster service recycles the Rhs.exe process that hosts the .dll files of the SQL Server resources. The .dll files of the SQL Server resources start a SQL Server shutdown process. When the SQL Server shutdown process exceeds the time that is specified in the DeadlockTimeout property, the service cannot stop, and the state becomes "Stop Pending." This service state prevents the SQL Server service from restarting.

↑ Back to the top

Resolution

The release version of SQL Server 2008

Important You must install this fix if you are running the release version of SQL Server 2008.

The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
973601 Cumulative update package 7 for SQL Server 2008
Note 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 2008 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:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released

SQL Server 2008 Service Pack 1

Important You must install this fix if you are running SQL Server 2008 Service Pack 1.


The fix for this issue was first released in Cumulative Update 5 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
975977 Cumulative update package 5 for SQL Server 2008 Service Pack 1
Note 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 2008 fix release. Microsoft recommends 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:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

References

For more information about the PendingTimeout property, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/en-us/library/aa372194(VS.85).aspx


For more information about the DeadlockTimeout property, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/en-us/library/bb309217(VS.85).aspx

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:

935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems



For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages



For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: kb, kbexpertiseadvanced, kbqfe, kbfix, kbsurveynew

↑ Back to the top

Article Info
Article ID : 975027
Revision : 6
Created on : 9/29/2020
Published on : 9/29/2020
Exists online : False
Views : 105