Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
FIX: Various Problems When You Call Transactional COM+ Components from ASP.NET
Article ID: 318000 - View products that this article applies to.
This article was previously published under Q318000
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
When you call managed or unmanaged transactional COM+ components from ASP.NET, one or more of the following problems may occur in your application:
This behavior can occur because of the following conditions:
If you are using COM+ components from ASP.NET on a Microsoft Windows 2000 production Web server, use the following methods, in the order presented, to work around these issues:
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/312118/EN-US/ )BUG: High Memory Usage and Handle Counts When an Application Contains ServicedComponent Objects
Fixes will be publicly available in Windows 2000 SP3 and MDAC 2.7 SP1. If a fix is required before the release of the aforementioned service packs, please contact Microsoft Product Support Services.
Article ID: 318000 - Last Review: November 4, 2003 - Revision: 2.5