FIX: Managed Application That Makes COM to COM+ Calls May Experience an Access Violation Error

This article has been archived. It is offered "as is" and will no longer be updated.
For a Microsoft .NET Framework 1.1 version of this article, see 823140.
If your managed application makes a COM to COM+ call under the following conditions, the application may quit unexpectedly (crash):
  • The target method has an Enum as its first argument.

  • Some reference types are included as other arguments.

  • Garbage collection occurs before the call is completed.
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. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next .NET Framework service pack that contains this fix.

To resolve this problem immediately, 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 typical 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   --------------------------------------------------------------   18-Jun-2003  02:53  1.0.3705.436    200,704  Aspnet_isapi.dll   18-Jun-2003  02:53                  510,714  Aspnet_perf2.ini   18-Jun-2003  02:46                    4,169  Aspnet_perf.h   18-Jun-2003  02:53                  513,302  Aspnet_perf.ini   18-Jun-2003  02:53  1.0.3705.436     28,672  Aspnet_rc.dll   18-Jun-2003  02:53  1.0.3705.436     24,576  Aspnet_regiis.exe   18-Jun-2003  02:53  1.0.3705.436     28,672  Aspnet_wp.exe   18-Jun-2003  02:15  1.0.3705.436     69,632  Corperfmonext.dll   18-Jun-2003  02:13  1.0.3705.436    303,104  Mscorjit.dll   18-Jun-2003  12:31  1.0.3705.436  1,953,792  Mscorlib.dll   18-Jun-2003  02:14  1.0.3705.436  2,269,184  Mscorsvr.dll   01-Aug-2002  19:38                       15  Smartnav.htm   17-Oct-2002  15:55                    8,728  Smartnav.js   18-Jun-2003  02:14  1.0.3705.436  2,269,184  Mscorwks.dll   18-Jun-2003  12:35  1.0.3705.436  1,196,032  System.web.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Article ID: 823202 - Last Review: 10/26/2013 19:03:58 - Revision: 2.4

  • Microsoft .NET Framework 1.0
  • kbnosurvey kbarchive kbbug kbfix kbqfe kbnetframe100presp3fix kbhotfixserver KB823202