Article ID: 839047 - View products that this article applies to.
For a Microsoft Microsoft .NET Framework 1.0 version of this article, see 839046
When a Component Object Model (COM) object is passed as a parameter in a COM Interop function call, the object will not be released if the parameter is defined as a VARIANT parameter and the function returns a failure HRESULT.
This problem occurs because COM Interop does not correctly clean up the VARIANT parameter if the COM function returns a failure HRESULT.
Software update informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft .NET Framework 1.1 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote 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.
File informationThe English version of this software update 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-Mar-2004 00:51 1.1.4322.1012 77,824 Corperfmonext.dll 18-Mar-2004 00:48 1.1.4322.1012 282,624 Fusion.dll 18-Mar-2004 00:48 1.1.4322.1012 311,296 Mscorjit.dll 18-Mar-2004 00:52 1.1.4322.1012 102,400 Mscorld.dll 19-Mar-2004 04:22 1.1.4322.1012 2,093,056 Mscorlib.dll 18-Mar-2004 00:41 10,748 Mscorlib.ldo 18-Mar-2004 00:50 1.1.4322.1012 2,502,656 Mscorsvr.dll 18-Mar-2004 00:51 1.1.4322.1012 2,490,368 Mscorwks.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates