FIX: Microsoft .NET Framework 1.1 common language runtime hotfix rollup

This article has been archived. It is offered "as is" and will no longer be updated.
The following problems in the Microsoft .NET Framework 1.1 are fixed in this hotfix rollup package:
  • When you compile some code, it may have valid Microsoft intermediate language (MSIL). However, when you run the compiled application, you receive the following unhandled exception error message:
    System.NullReferenceException: Object reference not set to an instance of an object.
    If optimization is turned off, you do not receive this exception error message.
  • Unmanaged Microsoft Component Object Model (COM) clients that enumerate through the current connections of a connection point or event that is exposed by a .NET Framework component do not exit the enumeration loop. The enumeration is completed through the IEnumConnections::Next method, and then the client application appears to stop responding. This problem may occur in a Microsoft Visual Basic 6.0 client when you use the WithEvents keyword.
  • If you call a Web service method, and if the method call takes a long time to return (typically, more than 100 seconds), the client application may receive the following exception error message:
    The underlying connection was closed
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, 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.

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 item in Control Panel.
   Date         Time   Version       Size       File name   --------------------------------------------------------------   24-Jun-2003  19:22  1.1.4322.916     77,824  Corperfmonext.dll   24-Jun-2003  19:19  1.1.4322.916    311,296  Mscorjit.dll   25-Jun-2003  08:16  1.1.4322.916  2,093,056  Mscorlib.dll   24-Jun-2003  19:12                   10,736  Mscorlib.ldo   24-Jun-2003  19:20  1.1.4322.916  2,494,464  Mscorsvr.dll   24-Jun-2003  19:21  1.1.4322.916  2,486,272  Mscorwks.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
822411 FIX: XML Messaging with the .NET Framework 1.1 hotfix rollup

Article ID: 823640 - Last Review: 12/08/2015 03:28:25 - Revision: 1.8

Microsoft .NET Framework 1.1

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbfix kbbug KB823640