FIX: You cannot roll back changes in a transaction after you call the ITransactionLocal::Abort method by setting the fRetaining flag to TRUE in a SQL Server 2005-based application that uses the SQL Native Client OLE DB provider

This article describes the following information about this hotfix release:

• The issues that are fixed by this hotfix
• The prerequisites to apply this hotfix
• Whether you must restart the computer after you install this hotfix
• Whether the hotfix package is replaced by any other hotfix
• Whether you must make any registry changes
• The files that are contained in this hotfix

Consider the following scenario. You use the SQL Native Client OLE DB provider to connect to an instance of Microsoft SQL Server 2005 in an application. In the connection, you start a transaction that enables the xact_abort option. After the option in enabled, SQL Server rolls back the transaction if a deadlock or an integrity violation occurs. Then, you try to abort the transaction. To do this, you call the ITransactionLocal::Abort method by setting the fRetaining flag of the ITransactionLocal::Abort method to TRUE.

In this scenario, you expect a new transaction to start in manual-commit mode after you abort the current transaction. Therefore, you expect that you can roll back the later TRANSACT-SQL statements after you call the ITransactionLocal::Abort method. However, you cannot roll back the later statements.

This issue occurs because the SQL Native Client OLE DB provider incorrectly switches the commit mode of the connection from manual-commit to auto-commit. Therefore, any changes in the later TRANSACT-SQL statements are immediately committed.

Cumulative update information

To resolve this problem, obtain cumulative update package 3 for Microsoft SQL Server 2005 Service Pack 2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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

• Microsoft SQL Server 2005 Service Pack 2
  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:
  913089  (http://support.microsoft.com/kb/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.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

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

To work around this issue, call the ITransactionLocal::Abort method to exit the transaction by setting the fRetaining flag to FALSE. Then, start a new transaction.

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

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: