FIX: SQL Server Does Not Properly Inform the DTC of Aborted Transactions

This article was previously published under Q248492
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 56751 (SQLBUG_70)
Under some circumstances when using the Distributed Transaction Coordinator (DTC), a transaction may be aborted on one server yet committed on another. This can happen if a situation such as the following example exists:

Consider two servers, A and B. A transaction starts on Server A and uses DTC to call a stored procedure on Server B. If a transaction abort happens on Server B (for example, a deadlock occurs), it returns the error message to Server A, but does not tell DTC to abort the transaction. As a result, Server A commits the transaction when it should have aborted it, because it was aborted on Server B.
Under some circumstances SQL Server is not passing a transaction abort to DTC.
To work around this problem, the application must interpret the incoming error message and manage the transaction itself rather then relying on DTC to abort the transaction.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.

Article ID: 248492 - Last Review: 10/22/2013 04:01:40 - Revision: 2.0

Microsoft SQL Server 7.0 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix KB248492