Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
FIX: An ongoing MS DTC transaction is orphaned in SQL Server 2005
| Article ID | : | 949075 |
| Last Review | : | April 29, 2008 |
| Revision | : | 1.1 |
Bug #: 50002406 (SQL Hotfix)
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.
On This Page
SUMMARY
This article describes the following about this hotfix release:
| • | The issues that are fixed by the hotfix package |
| • | The prerequisites for installing the hotfix package |
| • | Whether you must restart the computer after you install the hotfix package |
| • | Whether the hotfix package is replaced by any other hotfix package |
| • | Whether you must make any registry changes |
| • | The files that are contained in the hotfix package |
Back to the top
SYMPTOMS
Consider the following scenario. A Microsoft Windows Communication Foundation (WCF) application or a Microsoft ASP.NET application runs inside an Internet Information Services (IIS) 6.0 application pool. The application uses the
System.Transactions namespace to work together with a remote server that is running Microsoft SQL Server 2005. You use the
System.Data namespace to promote a Promotable Single Phase Enlistment (PSPE) transaction. In this scenario, an ongoing Microsoft Distributed Transaction Coordinator (MS DTC) transaction is orphaned if the IIS 6.0 application pool crashes because of an unhandled exception.
Note You may experience different symptoms in different scenarios.
Back to the top
CAUSE
This problem occurs when multiple connections are at work on the same MS DTC transaction. This problem occurs because no connections try to roll back the MS DTC transaction if the connections close correctly. Therefore, the MS DTC transaction is orphaned.
Back to the top
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2005 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
| • | SQL Server 2005 Service Pack 1
For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
913089 (http://kbalertz.com/Feedback.aspx?kbNumber=913089/)
How to obtain the latest service pack for SQL Server 2005
|
Restart information
You do not have to restart the computer after you apply this hotfix.
Registry information
You do not have to change the registry.
Back to the top
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top
MORE INFORMATION
To determine whether the MS DTC transaction is orphaned, run the following statement.
SELECT DISTINCT(req_transactionUOW) FROM sys.syslockinfo WHERE req_spid = -2
If the MS DTC transaction is orphaned, this statement returns the unit of work (UOW) of the MS DTC transaction.
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 (http://kbalertz.com/Feedback.aspx?kbNumber=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 (http://kbalertz.com/Feedback.aspx?kbNumber=824684/LN/) Description of the standard terminology that is used to describe Microsoft software updates
Back to the top
APPLIES TO
| • | Microsoft SQL Server 2005 Standard Edition |
| • | Microsoft SQL Server 2005 Developer Edition |
| • | Microsoft SQL Server 2005 Enterprise 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 |
Back to the top
| kbexpertiseadvanced kbfix kbsql2005engine kbpubtypekc kbqfe kbhotfixserver KB949075 |
Back to the top
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please