Consider the following scenario. In the Microsoft .NET Framework 2.0, you use the BeginGetRequestStream method and the EndGetRequestStream method in the HttpWebRequest class to complete an asynchronous HTTP request. In this scenario, when you try to access the Stream object that is returned by the EndGetRequestStream method, you receive a System.ObjectDisposedException exception.

Note This problem only occurs if you set the Method property in the HttpWebRequest class to a protocol property that uploads data. For example, you set the Method property to POST.

Back to the top

This problem occurs when the Web server resets or closes the connection after the client application sends the HTTP header. The HttpWebRequest class automatically tries to reopen a connection to the Web server to complete the transfer. When the transfer is successful, the EndGetRequestStream method incorrectly returns the Stream object from the first failed connection attempt, instead of the Stream object from the successful connection attempt. When the client application tries to use this disposed Stream object, a System.ObjectDisposedException exception is thrown.

Back to the top

Download information

The following file is available for download from the Microsoft Download Center:
Download the 271515_intl_i386_zip.exe package or the 288503_intl_x64_zip.exe package now. (https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=7255)

Release Date: 6/20/2007

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it 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 Product Support Services to obtain the hotfix. For a complete list of Microsoft Product 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 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.

File name	File version	File size	Date	Time
System.dll	2.0.50727.109	3,018,752	01-May-2006	21:15

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

For more information about the HttpWebRequest class, visit the following Microsoft Developer Network (MSDN) Web site: For more information about the System.ObjectDisposedException class, visit the following MSDN Web site: For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top