Article ID: 823140 - View products that this article applies to.
For a Microsoft .NET Framework 1.0 version of this article, see 823202
If your managed application makes a COM to COM+ call under the following conditions, the application may quit unexpectedly (crash):
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:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMSNOTE: 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 -------------------------------------------------------------- 23-Jun-2003 21:17 1.1.4322.915 77,824 Corperfmonext.dll 24-Jun-2003 12:13 1.1.4322.915 2,088,960 Mscorlib.dll 23-Jun-2003 21:15 1.1.4322.915 2,494,464 Mscorsvr.dll 23-Jun-2003 21:07 10,728 Mscorlib.ldo 23-Jun-2003 21:16 1.1.4322.915 2,486,272 Mscorwks.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.