ANN: ASP.NET 1.1 June 2003 Hotfix Rollup Package

• Previous message: Olaf Lüder: "Re: Problem mit ASP.NET auf IIS"
• Messages sorted by: [ date ] [ thread ]

Date: Sun, 20 Jun 2004 10:12:42 +0200

Hallo,

hier ist eine Info auf das aktuelle ASP.NET-Hotfixpaket, das allerdings nur
eingespielt werden sollte, wenn eines der unten beschriebenen Phänomene
auftreten sollte.

http://support.microsoft.com/default.aspx?kbid=821156

INFO: ASP.NET 1.1 June 2003 Hotfix Rollup Package

SUMMARY
This article contains information about a hotfix package that addresses the
symptoms that are discussed in the "More Information" section.
RESOLUTION
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, Microsoft recommends that you wait for the next .NET Framework 1.1
sevice pack that contains this hotfix.
[..]

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
819450 FIX: Intermittent "Underlying connection was closed" error messages
when you call a Web service from ASP.NET
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 INFO: 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 Mode
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 INFO: ASP.NET Hotfix Rollup
817854 FIX: ASP.NET Web application cannot deliver a client certificate to a
secure Web site

-- 
Jürgen Beck
MCSD.NET, MCDBA, MCSE, MCT, MVP .NET
MCP CRM Application/Installation/Customization
www.Juergen-Beck.de

• Previous message: Olaf Lüder: "Re: Problem mit ASP.NET auf IIS"
• Messages sorted by: [ date ] [ thread ]