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
• Information about whether you must restart the computer after you install the hotfix package
• Information about whether the hotfix package is replaced by any other hotfix package
• Information about whether you must make any registry changes
• The files that are contained in the hotfix package

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 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.

This problem occurs when multiple connections are working 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.

Cumulative update information

The fix for this issue was first released in Cumulative Update 9. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: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:Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have SQL Server 2005 Service Pack 2 (SP2) installed.

For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

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.

Hotfix file information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

SQL Server 2005 32-bit version

SQL Server 2005 x64-based version

SQL Server 2005 Itanium architecture version

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

To determine whether the MS DTC transaction is orphaned, run the following statement: 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: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: