Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: COM+ managed service components may not be immediately released by the Release method, and the components may not call the Dispose method when a call to the Activate method fails in the .NET Framework 1.1 SP1


View products that this article applies to.

Symptoms

On a computer that is running Microsoft Windows Server 2003 Service Pack 1 together with the Microsoft .NET Framework 1.1 Service Pack 1 (SP1), you may experience the following symptoms:
  • When a call to the Activate method fails, Microsoft COM+ managed service components are not immediately released by the Release method.
  • The COM+ managed service components objects do not call the Dispose method to dispose of the managed service components after the components are no longer used.
For example, when you configure a COM+ application to use memory pooling, COM+ statistics may display a COM+ managed service component count increase. Additionally, the COM+ application may leak memory. You do not experience this problem with COM+ unmanaged service components.

↑ Back to the top


Resolution

A 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 .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: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.

Prerequisites

You must have the Microsoft .NET Framework 1.1 SP1 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other software updates.

Hotfix file information

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 tool in Control Panel.
   Date         Time   Version        Size     File name
   -------------------------------------------------------------------------------
   24-May-2005  02:46  1.1.4322.2326  241,664  System.enterpriseservices.dll
   24-May-2005  02:46  1.1.4322.2326   66,560  System.enterpriseservices.thunk.dll

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

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

↑ Back to the top


Keywords: KB900095, kbhotfixserver, kbqfe, kbbug, kbfix, kbtshoot, kbprb, kbwinserv2003sp2fix

↑ Back to the top

Article Info
Article ID : 900095
Revision : 8
Created on : 3/23/2007
Published on : 3/23/2007
Exists online : False
Views : 503