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

Article translations Article translations
Article ID: 320068 - View products that this article applies to.
This article was previously published under Q320068
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 102506 (SQLBUG_70)
Expand all | Collapse all

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.

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 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.

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.

Properties

Article ID: 320068 - Last Review: October 26, 2013 - Revision: 2.0
Applies to
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbsqlserv700presp4fix KB320068

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com