FIX: Abort of DTC Transaction in tempdb May Cause 7105 Errors, Assertions, and Possible Shutdown of SQL Server

Article ID: 304847 - View products that this article applies to.
This article was previously published under Q304847
BUG #: 355018 (SHILOH_BUGS)
Expand all | Collapse all

On This Page

SYMPTOMS

An abort of a Microsoft Distributed Transaction Coordinator (DTC) transaction during tempdb activity, may result in 7105 errors, retail assertions, and potentially a failure during rollback in tempdb that may cause the server to shutdown.
Back to the top | Give Feedback

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211
(http://support.microsoft.com/kb/290211/EN-US/ )
INF: How to Obtain the Latest SQL Server 2000 Service Pack

Hotfix

NOTE: The following hotfix was created prior to Microsoft SQL Server 2000 Service Pack 2.

The English version of this fix should have the following file attributes or later: 
   Version     File name       Platform
   -------------------------------------
   8.00.430    Sqlservr.exe    i386
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.

Back to the top | Give Feedback

WORKAROUND

This problem has occurred in cases where the application's distributed transaction timeout causes the DTC manager to abort the transaction.

To work around the problem, eliminate the cause of the timeouts or increase the timeout value.
Back to the top | Give Feedback

STATUS

Microsoft has confirmed this to be a problem in SQL Server 2000. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.
Back to the top | Give Feedback

MORE INFORMATION

The 7105 error message that appears in the error log is similar to:
Error: 7105, Severity: 22, State: 6 Page (1:123232), slot 3 for text, ntext, or image node does not exist..
One or more of the following assertion messages appear in the error log if this problem occurs (based on a SQL Server 2000 retail build 194):
SQL Server Assertion: File: <SpcAlloc.cpp>, line=378 Failed Assertion = 'pPage->IsType (Page::TEXT_MIX_PAGE)'.
SQL Server Assertion: File: <page.cpp>, line=2777 Failed Assertion = 'rowLength >= offset + deleteLength'.
SQL Server Assertion: File: <logscan.cpp>, line=3037 Failed Assertion = 'm_lastLSN == NullLSN || startLSN < m_lastLSN'.
SQL Server Assertion: File: <page.cpp>, line=3429 Failed Assertion = 'm_freeCnt + emptySlots * sizeof (Slot) >= spaceNeed'.
The following message may also appear in the error log when this problem occurs:
AllocPageFromTargetExtent failed: extId=1:357672 pages_seen=8
Followed by a large dump of the internal SQL Server Lock manager and table this assertion:
SQL Server Assertion: File: <alloc.cpp>, line=10649 Failed Assertion = 'force_success == FALSE'.
Back to the top | Give Feedback

Properties

Article ID: 304847 - Last Review: September 26, 2005 - Revision: 3.2
APPLIES TO
  • Microsoft SQL Server 2000 Standard Edition
Keywords: 
kbhotfixserver kbqfe kbbug kbfix kbsqlserv2000presp2fix KB304847
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top