ASP.NET 1.1 June 2003 Hotfix Rollup Package (821156)

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for the Microsoft .NET Framework 1.1. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

885055 How to obtain Microsoft .NET Framework 1.1 Service Pack 1

Hotfix information

Important This hotfix contains two types of packages: a Microsoft Windows Installer package, and an Optional Component Manager (OCM) package. If you use Windows Server 2003, you must specify that you require the Windows Server 2003 (OCM) update. If you use an operating system different from Windows Server 2003, you must continue to use the Windows Installer package. For Windows Server 2003, Windows File Protection monitors the .NET Framework 1.1 files.

To correctly install the hotfix on Windows Server 2003, you must install the OCM hotfix package. If you try to install the Windows Installer package on Windows Server 2003, you receive the following error message:

The installer cannot install the upgrade patch because the program being upgraded may be missing or the upgrade patch updates a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.

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

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.

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 tool in Control Panel.

   Date         Time   Version            Size    File name
   -------------------------------------------------------------------------
   07-Jun-2003  00:44  1.1.4322.910      253,952  Aspnet_isapi.dll
   07-Jun-2003  00:44  1.1.4322.910       20,480  Aspnet_regiis.exe
   07-Jun-2003  00:44  1.1.4322.910       32,768  Aspnet_wp.exe
   15-May-2003  23:49                     33,522  Installpersistsqlstate.sql
   15-May-2003  23:49                     34,150  Installsqlstate.sql
   07-Jun-2003  12:52  1.1.4322.910    1,216,512  System.dll
   07-Jun-2003  00:39                     14,472  Webuivalidation.js
   07-Jun-2003  12:52  1.1.4322.910    1,249,280  System.Web.dll

This fix is also available for the German version of Windows Server 2003.

MORE INFORMATION

The following issues are fixed with this hotfix rollup:

812686 FIX: When you call the Response.ClearHeaders method in a custom HTTPModule, extra characters are appended to the output

819612 FIX: Slow performance when the browser capabilities evaluator is removed from the cache

820621 FIX: Cannot download WinForm application configuration files

820743 FIX: ASP.NET performance counters cannot count more than 113 loaded appdomains

820747 FIX: Cannot attach a user-mode debugger to the Aspnet_wp.exe process through image file run options

821155 Background batch compile may cause a deadlock when the thread pool has been exhausted

821349 FIX: Embedded null characters may bypass request script validation

821438 FIX: Antivirus programs may cause some Web applications to restart unexpectedly

821758 FIX: Server.Transfer does not invoke IsPostBack in .NET Framework 1.1

822148 FIX: ASP.NET queues too many requests

822162 FIX: ASP.NET Session variables are incorrectly accessible between applications when you use SQLServer Session Mode

823028 FIX: HttpApplication.OnThreadEnter may fail under memory pressure

823030 FIX: DataGrid made compliant with Section 508 of the Rehabilitation Act Amendments of 1998

821346 FIX: AspNetHostingPermission intersect does not handle NULL target correctly

818803 Post-RTM .NET Framework 1.1 ASP.NET Hotfix Package symptoms

819945 FIX: ASP.NET controls do not meet accessibility guidelines

Hotfixes that are ported to the .NET Framework 1.1

Note Because these articles were written for .NET Framework 1.0 hotfixes, the hotfix file information corresponds to the .NET Framework 1.0.

818537 FIX: Requests are incorrectly treated as non-postback requests

817005 FIX: Severe performance issues when you bind session state to threads in ASPCompat

816829 FIX: When I/O thread processes a slow request, completions on named pipes between Inetinfo.exe and Aspnet_wp.exe are blocked

814206 FIX: Calling Server.Transfer skips execution of custom HTTP filters

818612 FIX: "COM object can not be used" error message when you use an STA COM object that you created by using Server.CreateObject and stored in session scope in a different Web page

818058 ASP.NET hotfix rollup

812833 FIX: You cannot run multiple processes of ASP.NET at the same time