FIX: Simultaneous DTC Operations May Cause Errors

View products that this article applies to.

This article was previously published under Q256649

BUG #: 57354(SQLBUG_70)

Expand all | Collapse all

SYMPTOMS

SQL Server allows multiple system process ID (SPID) connections to enlist in the same Microsoft Distributed Transaction Coordinator (MS DTC) transaction. The SQL Server limits "active" operations to a single SPID. Simultaneous operation attempts result in the following 3910 error message:

Error 3910: Transaction context in use by another session.

NOTE: Spinlock errors are only reported to the console window and are not recorded in the SQL Server errorlog.

Back to the top

CAUSE

SQL Server is not properly gaining access to the Transaction Control Block (XCB) before handling the 3910 error conditions.

Back to the top

WORKAROUND

Identify the sources of the 3910 error and then correct them.

Back to the top

STATUS

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 (http://support.microsoft.com/kb/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.

Back to the top

MORE INFORMATION

To correct this, you need to prevent the processing of the 3910 error from leading to the unwanted behavior. SQL Server still limits the active SPIDs to 1. Applying this correction eliminates the stack traces, assertions and lock manager issues but the client continues to receive 3910 errors.

The client application should be investigated and the 3910 error conditions removed.

Back to the top