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.
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:
INF: How to Obtain the Latest SQL Server 2000 Service Pack
: 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
: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.
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.
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.
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'.