
	Search KbAlertz Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account

Already have an account?
[Click here to Login]

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Ads by Lake Quincy Media

Article ID: 960754 - Last Review: August 14, 2009 - Revision: 2.0

FIX: You receive the ObjectDisposedException exception when you refer to the Transaction.Current.TransactionInformation object

View products that this article applies to.

SYMPTOMS

Consider the following scenario:

You install the .NET Framework 2.0 or a later version of the .NET Framework.
You have an application that connects to Microsoft SQL Server 2008 by using the .NET Framework Data Provider for SQL Server.
The application uses the TransactionScope object to start a transaction.
In the transaction, you open a connection and enable the connection pool, and then you close the connection.

Note You can specify "Pooling=true" in the connection string to enable the connection pool. The default value is "true."

After the connection is closed, a time-out or an exception occurs. If you reference to the Transaction.Current.TransactionInformation object, you may receive the following error message:

System.ObjectDisposedException: Cannot access a disposed object
......

Back to the top

The transaction rolls back because of the time-out or the exception. This causes the transaction object to be disposed of. When you try to access the current transaction information, this triggers the ObjectDisposedException exception.

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

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

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 SP2 installed to apply 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.