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

This package contains hotfixes for the symptoms that are discussed in the "More Information" section.

Service pack information

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

Hotfix information

Important Two types of packages will be available for this hotfix, a Microsoft Windows Installer (.msi) package, and an Optional Component Manager (OCM) package. If you use Windows Server 2003, you must specify that you require the Windows 2003 (OCM) patch. If you use an operating system different from Windows 2003, you must continue to use the Windows Installer package. For Windows 2003 Server, 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 following error is generated:

ERROR_PATCH_TARGET_NOT_FOUND (1642)

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

The following is a brief summary of the fixes that are included in this package:

• When the following conditions exist, you may receive a client-side script error in Microsoft Internet Explorer or in a Netscape browser:
  1. You add the following form to a user control:

     <form id="Form1" name="Form1" runat="server">

  2. You add the user control, for example, Workspace1, to a page. When you do this, an auto-generated script that is similar to the following script is added to the page:

     <form name="Workspace1:Form1" method="post" action="formtest2.aspx" id="Workspace1_Form1">

  The script error occurs because the form name and the form ID are different, and the form name contains a colon as a delimiter.
  
  Another example of the problem in the automatically generated script for a __doPostBack function is the following:

  function __doPostBack(eventTarget, eventArgument)
  {
  	var theform;
  	if (window.navigator.appName.toLowerCase().indexOf("netscape") > -1)
  	{
  		theform = document.forms["_ctl14:Form1"];
  	}
  	else
  	{
  		theform = document._ctl14:Form1;
  	}
  
  	theform.__EVENTTARGET.value = eventTarget.split("$").join(":");
  	theform.__EVENTARGUMENT.value = eventArgument;
  	theform.submit();
  }
  

  Notice that the form has a uniqueID property that contains a colon in the following lines:

  theform = document.forms["_ctl14:Form1"];
  theform = document._ctl14:Form1;
  

• You cannot load multiple ASP.NET worker processes.
  
  In Microsoft Internet Information Services 5.0 (IIS 5.0), you can configure the virtual directory to run in highly isolated mode (such as in a separate Dllhost.exe). However, ASP.NET ignores the IIS 5.0 settings. Application Domain isolation provides some level of isolation. There are major issues in supporting extensive earlier code. Because the DLLs are loaded in the Domain-neutral space, and all ASP.NET applications run in the same process, an application that contains coding errors or an application that contains malicious code can easily cause the ASP.NET worker process to fail. If this problem occurs, all the hosted applications fail.
• Client-side data validation in Microsoft Internet Explorer for Macintosh does not work as expected.
• When ASP.NET tries to unload the AppDomain under high load, one of the CPUs can experience 100 percent CPU utilization.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in the .NET Framework 1.1 Service Pack 1.

For additional information, click the following article number To view the article In the Microsoft Knowledge Base: The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.