FIX: An update package is available for the .NET Framework 2.0 Service Pack 1

Introduction

This article describes an update package for the Microsoft .NET Framework 2.0 Service Pack 1 (SP1). Additionally, this article describes some problems that are resolved by this update package.

This update package fixes the following issue:

• 946660  (http://support.microsoft.com/kb/946660/ ) FIX: The headers attribute of a cell is rendered incorrectly when the cell is associated with multiple headers in an ASP.NET 2.0 Web application

This update package fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

• If the computer is a domain controller and does not have the World Wide Web Publishing Service (W3SVC) installed, an Error event that resembles the following is logged in the event log every several seconds:
  Event Type: Error
  Event Source: Perflib
  Event Category: None
  Event ID: 1008
  Description:
  The Open Procedure for service "ASP.NET" in DLL "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\aspnet_perf.dll" failed. Performance data for this service will not be available. Status code returned is data DWORD 0.
  Data:
  0000: 05 40 00 80
• If Internet Information Services (IIS) uses the StaticFileHandler class to serve a large file, you may receive the following OutOfMemoryException exception:

  System.OutOfMemoryException in System.Web.HttpResponseUnmanagedBufferElement..ctor() 
  System.OutOfMemoryException
  Insufficient memory to continue the execution of the program.
  
  System.Web.HttpResponseUnmanagedBufferElement..ctor() 
  System.Web.HttpWriter.BufferData(Byte[] data, Int32 offset, Int32 size, Boolean needToCopyData) 
  System.Web.HttpWriter.WriteFromStream(Byte[] data, Int32 offset, Int32 size) 
  System.Web.HttpWriter.WriteBytes(Byte[] buffer, Int32 index, Int32 count) 
  System.Web.HttpResponse.WriteVirtualFile(VirtualFile vf) 
  System.Web.StaticFileHandler.RespondUsingVirtualFile(String virtualPath, HttpResponse response) 
  System.Web.StaticFileHandler.ProcessRequestInternal(HttpContext context) 
  System.Web.DefaultHttpHandler.BeginProcessRequest(HttpContext context, AsyncCallback callback, Object state) 
  fbs.Handlers.CustomDefaultHandler.BeginProcessRequest(HttpContext context, AsyncCallback callback, Object state) 
  System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() 
  System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

  This problem occurs even if there is sufficient memory.
• When you access the performance counters of IIS or of ASP.NET from a computer that is running the 32-bit version of Microsoft Operations Manager 2005, you cannot access the performance counters if they run in 64-bit mode.

Update package 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 .NET Framework 2.0 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: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 Service Pack 1 installed to apply this update package.

Restart requirement

You do not have to restart the computer after you apply this update package.

File information

The English version of this update package 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.

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

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: