Article ID: 320068 - Last Review: September 27, 2005 - Revision: 1.1

FIX: DTC May Experience a Spinloop That Causes SQL Server to Become Unresponsive

View products that this article applies to.

This article was previously published under Q320068

BUG #: 102506 (SQLBUG_70)

SYMPTOMS

Microsoft Distributed Transaction Coordinator (DTC) queries that use linked servers may experience an infinite spinloop (infinitely waiting to acquire a spin lock), which can lead to the server that is running SQL Server to becoming unresponsive. If the server becomes unresponsive, no new connections can be made to the server and no existing connections on the server work.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 7.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

301511 (http://support.microsoft.com/kb/301511/EN-US/ ) INF: How to Obtain the Latest SQL Server 7.0 Service Pack

NOTE: The following hotfix was created prior to Microsoft SQL Server 7.0 Service Pack 4.

Intel:

The English version of this fix should have the following file attributes or later:

   Date        Time      Version     Size      File name
   ---------------------------------------------------------

   3/19/2002   7:43 PM   7.00.1027   4937 KB   Sqlservr.exe

NOTE: Because of file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.

Alpha:

The English version of this fix should have the following file attributes or later:

   Date        Time      Version     Size       File name
   ---------------------------------------------------------

   3/19/2002   7:44 PM   7.00.1027   11374 KB   Sqlservr.exe

NOTE: Because of file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 7.0 Service Pack 4.

Back to the top