A list of the bugs that are fixed in the .NET Framework 1.1 Service Pack 1 but are not described elsewhere in individual Microsoft Knowledge Base articles

Article translations Article translations
Article ID: 888528 - View products that this article applies to.
Expand all | Collapse all

On This Page

INTRODUCTION

This article includes a list of the bugs that are fixed in the .NET Framework 1.1 Service Pack 1 and that are not described elsewhere in individual Microsoft Knowledge Base (KB) articles.

For more information about previously documented fixes in the .NET Framework 1.1 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
867460 List of bugs that are fixed in the .NET Framework 1.1 Service Pack 1

MORE INFORMATION

Admin UI and Catalog

An InvalidComObjectException error occurs when you enumerate through a ManagementObjectCollection collection after you make a call to the collection's Count property.

When you enumerate the ManagementObjectCollection collection after you make a call to the collection's Count property, you may receive the following exception error message:
InvalidComObjectException
This problem occurs when you retrieve the value of the Count property. The Count property uses the foreach construct. The foreach construct makes a call to the Dispose method on each object in the collection.

ASP.NET

When you run the "aspnet_regiis –i" command, the password is reset if the ASPNET account already exists.

You may use the ASP.NET Microsoft Internet Information Services (IIS) registration tool (Aspnet_regiis.exe) together with the -i option to register the ASP.NET ISAPI version with your ASP.NET application. However, if you do this, and the ASPNET account already exists, the aspnet_regiis –i command does not change the password as expected. Instead, the aspnet_regiis –i command resets the password.

Note When the password for the ASPNET account is reset, other programs that use the ASPNET account may not function correctly.

ASP.NET Session State Service settings are not preserved when you upgrade.

When you upgrade or apply a hotfix that includes changes to the ASP.NET Session State Service, the ASP.NET Session State Service settings are not preserved. If the ASP.NET Session State Service startup setting is set to Automatic before to the upgrade, the ASP.NET Session State Service startup setting is changed to Manual after the upgrade.

A new default behavior has been added to encode the new line character (\n) in response headers, and a configuration option has been added to disable this behavior.

By default, the new line character (\n) is encoded when it is found in the header body. This new behavior helps protect your system from "HTTP Response Splitting" attacks.

To work around this new behavior, you must set the following EnableHeaderChecking attribute to false in the <httpRuntime> element. The <httpRuntime> element is used to configure the ASP.NET HTTP runtime settings. The following is an example of how to set the EnableHeaderChecking attribute to false so that the new line character (\n) is not encoded:
<httpRuntime EnableHeaderChecking="false" .../>

The password for the ASPNET account is changed when you install the .NET Framework 1.1.

When you install either an upgrade or a service pack for the .NET Framework 1.1, the password for the ASPNET account is changed.

Note The ASPNET account is a reserved account. Therefore, we recommended that you do not manually change the password.

.NET Framework class library

You receive a "Culture ID someLCID is not a supported culture" exception error message when you try to create an instance of the CultureInfo class that is based on an ELK locale.

When you try to create an instance of the CultureInfo class that is based on an extension language kit (ELK) locale, you receive an exception error message that is similar to following:
Culture ID someLCID is not a supported culture.
Note someLCID is the language identifier.

This problem occurs when you try to create an instance of the CultureInfo class for a locale that is not supported by the .NET Framework 1.1.

The following new fallback behavior has been added to the CultureInfo class.
  • Create an instance of the CultureInfo class that is based on the current user default locale. Use the GetUserDefaultLCID function to retrieve the current user default locale identifier.
  • Create an instance of the CultureInfo class that is based on the system default locale. Use the GetSystemDefaultLCID function to retrieve the system default locale identifier.
  • Create an instance of the CultureInfo class that is based on the default language of the system. Use the GetSystemDefaultUILanguage function to retrieve the language identifier (LANGID) for the default language of the system.
  • Create an instance of the CultureInfo class that is based on the InvariantCulture property.
Note If the culture is not supported by the operating system, you receive the following exception error message:
Culture name someLCID is not supported.

The National Language Support data contains an incorrect name for Serbia and Montenegro.

The National Language Support (NLS) data contains an incorrect name for Serbia and Montenegro. The incorrect name was Serbia. This name has been changed to Serbia and Montenegro.

COM+ services

New interfaces appear in the System.Runtime.InteropServices namespace after you install the .NET Framework 1.1 SP1.

After you install the .NET Framework 1.1 SP1, new interfaces appear in the IntelliSense window. When you type system.Runtime.InteropServices. (including the period [.] character), new interfaces that start with the underline character (_) appear.

The .NET Class Library (NCL)

A "ServerProtocolViolationException" WebException error occurs when you call the HttpWebRequest GetResponse method.

To help protect your computer from "HTTP Response Splitting" attacks, parsing is performed as it is described in the Request for Comments (RFC) 2616 document. Therefore, no control characters are permitted in names or in values. For example, the carriage return (CR) character and the linefeed (LF) character are not permitted. Additionally, many other characters are not permitted in names, and every response header must have a colon.

To work around this new behavior, you must add the useUnsafeHeaderParsing attribute to the <httpWebRequest> element in the Machine.config file. The following code is an example of how to set the useUnsafeHeaderParsing attribute to true.
<system.net>
	<settings>
		<httpWebRequest
			useUnsafeHeaderParsing = "true"
		/>
	</settings>
</system.net>

Universal Runtime (URT) Integration

You cannot install a .NET Framework 1.1 admin image that includes an update or a service pack over the original release version of an admin or client image.

When you try to install a .NET Framework 1.1 image over an original release version of an admin or client image, and the image that you want to install includes an update or a service pack, the installation does not succeed.

To work around this behavior, you must apply the update or install the service pack separately.

You must repair the .NET Framework after you upgrade the operating system.

When you upgrade the operation system, you must repair the Microsoft .NET Framework before you install the .NET Framework 1.1 SP1.

For example, you must repair the .NET Framework 1.1 when you upgrade from Microsoft Windows Millennium Edition to Microsoft Windows XP. After you upgrade to Windows XP, you must perform a repair operation on the existing .NET Framework 1.1 before you install the .NET Framework 1.1 SP1. To repair the .NET Framework 1.1, follow these steps:
  1. Click Start, and then click Control Panel.
  2. Click Add or Remove Programs.
  3. Click Microsoft .NET Framework 1.1, and then click Click here for support information.

An administrative admin image of the .NET Framework 1.1 that includes the .NET Framework 1.1 SP1 does not install correctly after you install only the prerequisites for Visual Studio .NET 2003.

When you install only the prerequisites for Microsoft Visual Studio .NET 2003, and then you try to install an admin image that contains the .NET Framework 1.1 and the .NET Framework 1.1 SP1, the installation does not succeed.

This problem occurs because the Windows Installer service keeps a copy of the Mscoree.dll file in memory for 20 minutes after you install the Visual Studio .NET 2003 prerequisites.

To work around this problem, use one of the following methods:
  • Wait for 20 minutes without any Windows Installer activity and then try to install the admin image again.
  • Manually stop the Windows Installer service. To do this, type net stop msiserver at a command prompt, and then press ENTER.
  • Restart the computer.

You receive a "Specified cast is not valid" error message in BizTalk Server 2004 when you use a rule set in Rules Composer or when you use a rule set in an orchestration.

In Microsoft BizTalk Server 2004, if you use a rule set in the Rules Composer, or if you use a rule set in an orchestration, you may receive the following error message:
System.InvalidCastException: Specified cast is not valid.
For more information about how to fix this error in BizTalk Server 2004, click the following article number to view the article in the Microsoft Knowledge Base:
875540 FIX: You receive a "Specified cast is not valid" error message in BizTalk Server 2004 when you use a rule set in Rules Composer or you use a rule set in an orchestration
Note You must install the .NET Framework 1.1 SP1 before you apply the hotfix that is described in Microsoft Knowledge Base article 875540.

An administrative admin image of the .NET Framework 1.1 SP1 is not blocked from installing over an unmanaged image.

When you deploy an administrative admin image of the .NET Framework 1.1 SP1 by using a Group Policy setting, the admin image is not blocked from installing over an image that has an unmanaged hotfix applied to it. The installation of the .NET Framework 1.1 SP1 should be blocked by the unmanaged image.

Note When you try to install the .NET Framework 1.1 SP1 by using Windows Update or by double-clicking the distribution file, the installation is blocked as expected.

When you remove Windows XP Service Pack 2 from Windows XP Table PC Edition, the operation breaks the .NET Framework 1.1 installation.

In Microsoft Windows XP Tablet PC Edition 2005, when you remove Windows XP Service Pack 2 (SP2), you receive a warning message that some programs may not run correctly, such as the .NET Framework 1.1. After you remove Windows XP SP2, you must remove and then reinstall the .NET Framework 1.1 to repair the installation.

Note If you try to repair the .NET Framework 1.1 installation, the repair operation does not succeed.

XML Web services

<CustomErrors mode="Off"/> does not display inner exception messages in runtime SoapException exceptions.

When you set the mode attribute of the <CustomErrors> element to Off, the inner exception type or stack trace is not included for SoapException exception errors. The following code is an example of how to set the mode attribute of the <CustomErrors> element to Off in the Web.config file.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <system.web>
    <customErrors mode="Off"/>
  </system.web>
</configuration>
Note This behavior occurs after you install the .NET Framework 1.1 SP1.

Web service call behavior that occurs when the WebRequest.PreAuthenticate property is set to true.

When you set the PreAuthenticate property to true before you make a Web service call, the credentials are included with the request. Before you install the .NET Framework 1.1 SP1, the behavior that occurs when the PreAuthenticate property is set to true is the following:
  1. A PreAuthenticated Web service call request is made without the credentials.
  2. The Web service call is denied, and you receive an HTTP 404 error message.
  3. A PreAuthenticated Web service call request is made with the credentials.
Note The discovery steps in step 1 and in step 2 are no longer performed when PreAuthenticate property is set to true.

Windows Forms

The content of a cell continue to appear on the DataGrid control after you set its DataSource property to null.

When the DataSource property of a DataGrid control is set to null, the content of the selected cell is not cleared, and the image of the cell's contents continues to appear. This problem occurs when the following conditions are true:
  • A DataGridColumnStyle has been applied to the DataGrid control.
  • The .NET Framework 1.1 SP1 has been installed.
To work around this problem, call the GridColumnStyles.Clear method to clear the column styles before you set the DataSource property to null. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
890211 FIX: The cells are not cleared when you set the Datasource property to NULL on cells that have a custom DataGridColumnStyle property in the .NET Framework 1.1
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 888528 - Last Review: April 19, 2006 - Revision: 4.4
APPLIES TO
  • Microsoft .NET Framework 1.1
Keywords: 
kbwebclasses kbwebforms kbwebservices kbwebserver kbnetframe110sp1fix kbqfe kbfix kbbug kbtshoot kbinfo KB888528

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com