Consider the following scenario. You create an application that is based on the .NET Framework 2.0. In the application, you use a SqlConnection object to open a connection to Microsoft SQL Server. You execute a transaction on the connection. However, before the transaction is finished, you call the Abort method of the thread that executes the transaction. In this scenario, a query against a table that is used in the transaction cannot finish successfully.

This problem may occur if the following conditions are true:

• The application is a Web application.
• The transaction takes a long time to finish.

This problem does not in the .NET Framework 1.0 or in the .NET Framework 1.1.

This problem also occurs in the .NET Framework 2.0 with Service Pack 1 (SP1).
For more information about a hotfix that corrects this problem in the .NET Framework 2.0 with Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

This problem occurs because the .NET Framework 2.0 does not clean up the SqlConnection object. The transactions that the SqlConnection object manages are still active. Therefore, these transactions maintain locks on tables or on table rows until the application exits.

When a Web application uses a SqlConnection object to execute a transaction, Internet Information Services (IIS) calls the Abort method of the thread that executes the transaction if the transaction time exceeds the value of the HttpRuntimeSection.ExecutionTimeout property of IIS. Therefore, this transaction maintains locks on tables or on table rows until you restart the application pool.

Note By default, the value of the HttpRuntimeSection.ExecutionTimeout property is 90. This value represents 90 seconds.

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 .NET Framework 2.0 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

There are no prerequisites for this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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.

The .NET Framework 2.0, x86-based versions

The .NET Framework 2.0, x64-based versions

The .NET Framework 2.0, Itanium architecture versions

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

For more information about related problems, 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: