You are currently offline, waiting for your internet to reconnect

FIX: Assertion failures occur in SQL Server 2005 when a Distributed Transaction Coordinator (DTC) transaction is rolled back while that transaction is being commited by the DTC

Extended support for SQL Server 2005 ends on April 12, 2016

If you are still running SQL Server 2005 after April 12, 2016, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.
SYMPTOMS
Consider the following scenario:
  • In Microsoft SQL Server 2005, you have a transaction that is being commited by the Distributed Transaction Coordinator (DTC).
  • One of the SQL transactions in the DTC transaction is rolled back after the DTC prepares the distributed transaction for commit. For example, a SQL transaction may be rolled back after you kill some SPIDs that are involved in the DTC transaction. Or, a SQL transaction may be rolled back when an activity that is running in the SQL transaction causes an error.
In this scenario, some assertion failures may occur, and some mini-dump files are generated in the SQL Server log folder. When this problem occurs, the following error messages are logged in the SQL Server error log file:
<Date Time> spid12s * *******************************************************************************
<Date Time> spid12s *
<Date Time> spid12s * BEGIN STACK DUMP:
<Date Time> spid12s * <Date Time> spid 12
<Date Time> spid12s *
<Date Time> spid12s * Location: xactrm.cpp:2336
<Date Time> spid12s * Expression: m_state == BaseXact::XACT_PREPARED
<Date Time> spid12s * SPID: 12
<Date Time> spid12s * Process ID: 3008

<Date Time> spid12s Error: 17066, Severity: 16, State: 1.
<Date Time> spid12s SQL Server Assertion: File: <xactrm.cpp>, line=2336 Failed Assertion = 'm_state == BaseXact::XACT_PREPARED'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
<Date Time> spid12s Error: 3624, Severity: 20, State: 1.
<Date Time> spid12s A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.

<Date Time> spid12s * *******************************************************************************
<Date Time> spid12s *
<Date Time> spid12s * BEGIN STACK DUMP:
<Date Time> spid12s * <Date Time> spid 12
<Date Time> spid12s *
<Date Time> spid12s * Location: viperrm.cpp:2587
<Date Time> spid12s * Expression: 0
<Date Time> spid12s * SPID: 12
<Date Time> spid12s * Process ID: 3008
<Date Time> spid12s * Description: No exceptions are allowed at this point

<Date Time> spid12s Error: 17065, Severity: 16, State: 1.
<Date Time> spid12s SQL Server Assertion: File: <viperrm.cpp>, line = 2587 Failed Assertion = '0' No exceptions are allowed at this point. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to make sure that in-memory data structures are not corrupted.
<Date Time> spid12s Error: 17053, Severity: 16, State: 1.
<Date Time> spid12s High priority system task thread: Operating system error Exception 0x1 encountered.
CAUSE
This issue occurs because of a logical inconsistency between the DTC and Resource Manager (SQL Server). This inconsistency triggers the assertion check.
RESOLUTION
The fix for this issue was first released in Cumulative Update 7 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
976951 Cumulative update package 7 for SQL Server 2005 Service Pack 3
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
960598 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
REFERENCES
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about how to obtain SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005
For more information about new features and improvements in SQL Server 2005 Service Pack 3, visit the following Microsoft Web site: For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Properties

Article ID: 977350 - Last Review: 12/22/2009 03:24:17 - Revision: 2.0

Microsoft SQL Server 2005 Standard Edition, Microsoft SQL Server 2005 Enterprise Edition, Microsoft SQL Server 2005 Developer Edition, Microsoft SQL Server 2005 Workgroup Edition, Microsoft SQL Server 2005 Standard X64 Edition, Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems, Microsoft SQL Server 2005 Enterprise X64 Edition, Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems

  • kbexpertiseadvanced kbsurveynew kbqfe kbfix KB977350
Feedback