FIX: .NET Framework Implementation of IEnumConnections::Next Causes the Client Application to Stop Responding

This article has been archived. It is offered "as is" and will no longer be updated.
Unmanaged COM clients that enumerate through the current connections of a connection point (event) that is exposed by a .NET Framework component do not exit the enumeration loop. The enumeration is completed through IEnumConnections::Next, and then the client application appears to stop responding. This problem might occur in a Visual Basic 6.0 client when you use the keyword 'WithEvents'.
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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 fix has the file attributes (or later) 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.
   Date         Time   Version       Size       File name   ---------------------------------------------------------   23-Jan-2003  10:21  1.0.3705.397  1,953,792  Mscorlib.dll   22-Jan-2003  23:16  1.0.3705.397  2,269,184  Mscorsvr.dll   22-Jan-2003  23:17  1.0.3705.397  2,269,184  Mscorwks.dll

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Article ID: 813105 - Last Review: 02/27/2014 21:16:35 - Revision: 1.4

  • Microsoft .NET Framework 1.0
  • Microsoft .NET Framework Software Development Kit 1.0 Service Pack 1
  • Microsoft .NET Framework Software Development Kit 1.0 Service Pack 2
  • kbnosurvey kbarchive kbbug kbfix kbqfe kbhotfixserver KB813105