Microsoft KB Archive/922658

= SQL Server 2000 or SQL Server 2005 may temporarily stop responding on a Windows Server 2003 Service Pack 1-based computer =

Article ID: 922658

Article Last Modified on 11/20/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Express Edition
 * Microsoft SQL Server 2005 Express Edition with Advanced Services
 * Microsoft SQL Server 2005 Workgroup Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Personal Edition
 * Microsoft SQL Server 2000 Workgroup Edition

-





SYMPTOMS
If you run Microsoft SQL Server 2000 or Microsoft SQL Server 2005 on a Microsoft Windows Server 2003 Service Pack 1 (SP1)-based computer, SQL Server may temporarily stop responding (hang) in certain cases. Depending on the severity of the problem, this behavior may take from several milliseconds to several minutes.

In most cases, you may notice that the value in the &quot;Batch Requests/sec&quot; counter of the SQLServer:SQLStastics performance object drops significantly in the System performance monitor. Sometimes, the counter value drops to 0. Additionally, you may notice a similar decrease in CPU utilization and in disk utilization.

In some cases, the following error message may be logged in the SQL Server errorlog file:

Error: 17883, Severity: 1, State: 0 server Process 162:0 (0) UMS Context 0x11DE8B68 appears to be non-yielding on Scheduler 1.

This problem occurs when one or more of the following conditions are true:
 * SQL Server runs lots of batches in which errors are raised. These errors include both error messages that are returned to the client connection and internal exceptions such as attention events.
 * SQL Server is running on a computer that has lots of CPUs and lots of RAM installed. This problem may be more pronounced on 64-bit operating systems.



CAUSE
This problem occurs because SQL Server threads are stuck behind an internal Windows lock mechanism that identifies the process address. If lots of threads are waiting for the lock, this problem may occur.



RESOLUTION
To resolve this issue, install the hotfix for Windows Server 2003 SP1 that is described in Microsoft Knowledge Base 919341. For more information about this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:

919341 A program that uses structured exception handling may stop responding for several seconds in Microsoft Windows Server 2003 with Service Pack 1



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
We recommend that you install the following products to obtain optimal performance:
 * Windows Server 2003 SP1 together with the hotfix that is described in Microsoft Knowledge Base article 919341
 * SQL Server 2005 or later versions of SQL Server 2005
 * SQL Server 2000 build 8.00.2187 or later versions of SQL Server 2000

