FIX: Abort of Multi-Database Transaction Can Fail with Assertion

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


An abort of a transaction, which involves modifications to multiple databases, can fail with an assertion error. The user connection is dropped when the error occurs.

The SQL Server error log contains a stack dump, and these error messages follow:
kernel   SQL Server Assertion: File: <xdesmgr.c>, line = 1800
Failed Assertion = 'FALSE' Invalid XDES state transition from PREPARED to ACTIVE context: 4
Error: 3624, Severity: 20, State: 1.
An abort of a transaction can be either an error message that occurs when a statement is being modified, or an attention that is initiated by the client.


Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.


Article ID: 278280 - Last Review: October 21, 2013 - Revision: 2.0
  • Microsoft SQL Server 7.0 Standard Edition
kbnosurvey kbarchive kbbug kbfix kbqfe KB278280

Contact us for more help

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