Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: The Aspnet_wp.exe process may stop responding when you use the Response.BinaryWrite method to download large files from an ASP.NET page


View products that this article applies to.

For a Microsoft .NET Framework 1.1 version of this article, see 823409 (http://support.microsoft.com/kb/823409/ ) .
For a Microsoft .NET Framework 1.1 version of this article, see 823409 (http://support.microsoft.com/kb/823409/ ) .

↑ Back to the top


Symptoms

When you use the Response.BinaryWrite method to download files that are 400 MB or larger from an ASP.NET page, the Aspnet_wp.exe process may stop responding (crash). You may see the following event logged in the application log of the Event Viewer:
Source: ASP.NET 1.0.3705.0
Event Category: None
Event ID: 1000
Date: 5/16/2002
Time: 11:01:11 AM
User: N/A
Computer: <COMPUTERNAME>
Description: Aspnet_wp.exe (PID: 9999) stopped unexpectedly.

↑ Back to the top


Cause

In this scenario, the following things occur:
  1. The code typically causes the download box to appear.
  2. The Inetinfo.exe process starts to heavily exhaust memory.
  3. Private Bytes in Inetinfo.exe increase until you run out of virtual memory.
  4. When you run out of virtual memory, you experience an unexpected recycle of the Aspnet_wp.exe process. (Private Bytes in Aspnet_wp.exe are not affected; the number of Aspnet_wp.exe Private Bytes does not significantly increase.)
  5. Inetinfo.exe does not release the memory until the download is complete (or canceled).

Note If you perform simultaneous downloads, you may compound the problem.

↑ Back to the top


Resolution

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

The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.
   Date         Time   Version       Size       File name
   --------------------------------------------------------------
   28-May-2003  00:47  1.0.3705.429    200,704  Aspnet_isapi.dll
   28-May-2003  00:42                    4,169  Aspnet_perf.h
   28-May-2003  00:47                  513,302  Aspnet_perf.ini
   28-May-2003  00:47                  510,714  Aspnet_perf2.ini
   28-May-2003  00:47  1.0.3705.429     28,672  Aspnet_rc.dll
   28-May-2003  00:47  1.0.3705.429     24,576  Aspnet_regiis.exe
   28-May-2003  00:47  1.0.3705.429     28,672  Aspnet_wp.exe
   27-May-2003  23:55  1.0.3705.429     69,632  Corperfmonext.dll
   27-May-2003  23:53  1.0.3705.429    303,104  Mscorjit.dll
   28-May-2003  11:59  1.0.3705.429  1,953,792  Mscorlib.dll
   27-May-2003  23:46                   10,284  Mscorlib.ldo
   27-May-2003  23:54  1.0.3705.429  2,269,184  Mscorsvr.dll
   27-May-2003  23:53  1.0.3705.429  2,269,184  Mscorwks.dll
   01-Aug-2002  21:38                       15  Smartnav.htm
   17-Oct-2002  17:55                    8,728  Smartnav.js
   28-May-2003  12:01  1.0.3705.429  1,196,032  System.Web.dll

↑ Back to the top


Status

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

↑ Back to the top


More information

This hotfix adds another function to the Response object (Response.TransmitFile). You can use the function instead of the BinaryWrite function or instead of other functions that are used to send files to the client. Also, you can use this function regardless of the size of the file that you want to transmit. To test this new functionality, paste the following code in an empty ASPX page after you download and install the hotfix. You must change the "c:\\repro\\z.zip" line in the code to reflect a path and ZIP file that exist on a computer.
<script runat=server language=C#>
    void Page_Load() {
        Response.ContentType="application/x-zip-compressed";
        Response.AddHeader("Content-Disposition", "attachment;filename=z.zip");
        Response.TransmitFile("c:\\repro\\z.zip");
    }
</script>

↑ Back to the top


Keywords: kbqfe, kbvs2002sp1sweep, kbnetframe100presp3fix, kbqfe, kbfix, kbcodesnippet, kbbug, kbhotfixserver, KB821387

↑ Back to the top

Article Info
Article ID : 821387
Revision : 10
Created on : 10/25/2005
Published on : 10/25/2005
Exists online : False
Views : 395