Open Software Solutions

Consider the following scenario.

•	You create a Web project that is built on the Microsoft .NET Framework 2.0 Service Pack 1 (SP1).
•	You run a long-running stored procedure or an SQL script inside an externally initiated transaction in the Web project.
•	After the procedure runs for a long time, the thread is killed because the execution time exceeds the value of the ExecutionTimeout setting on the server.

In this scenario, you cannot manipulate the data table that is used in the transaction. This behavior occurs until the connection to the database is reset.

Note The connection to the database can be reset only if the database is located on the Web server. If the database is located on the Web server, the database can be reset in about 2.5 minutes.

Back to the top

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

You must have the .NET Framework 2.0 SP1 installed to apply this hotfix.

Restart information

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

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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.

The .NET Framework 2.0, x86-based versions

File name	File version	File size	Date	Time	Platform
System.data.dll	2.0.50727.1813	2998272	15-Feb-2008	04:49	x86
System.data.oracleclient.dll	2.0.50727.1813	484352	15-Feb-2008	04:49	x86

The .NET Framework 2.0, Itanium architecture versions

File name	File version	File size	Date	Time	Platform
System.data.dll	2.0.50727.1813	2998272	15-Feb-2008	04:49	x86
System.data.dll	2.0.50727.1813	3208192	15-Feb-2008	01:25	IA-64
System.data.oracleclient.dll	2.0.50727.1813	484352	15-Feb-2008	04:49	x86
System.data.oracleclient.dll	2.0.50727.1813	503808	15-Feb-2008	01:25	IA-64

The .NET Framework 2.0, x64-based versions

File name	File version	File size	Date	Time	Platform
System.data.dll	2.0.50727.1813	2998272	15-Feb-2008	04:49	x86
System.data.dll	2.0.50727.1810	3113472	14-Feb-2008	23:36	x64
System.data.oracleclient.dll	2.0.50727.1813	484352	15-Feb-2008	04:49	x86
System.data.oracleclient.dll	2.0.50727.1810	499712	14-Feb-2008	01:25	x64

Back to the top

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

Back to the top

If you experience this problem when you use the release version of the .NET Framework 2.0, you can also apply the hotfix that is described in the following Microsoft Knowledge Base article:

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top