Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 318000 - Last Review: November 4, 2003 - Revision: 2.5
FIX: Various Problems When You Call Transactional COM+ Components from ASP.NET
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:
256986Â
(http://kbalertz.com/Feedback.aspx?kbNumber=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:
- Access violations
- Memory leaks
- Handle leaks
- Deadlocks
- Poor performance
This behavior can occur because of the following
conditions:
- A bug in COM+ 1.0 causes deadlocks, memory leaks, and
handle leaks.
- Two bugs in COM+ 1.0 cause access violations.
- A bug in MDAC 2.7 causes poor performance.
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:
- Install Windows 2000 Service Pack 2 (SP2) and the COM+
Hotfix Rollup Package 18.1. To obtain the COM+ Hotfix Rollup Package 18.1,
contact Microsoft Product Support Services. Windows 2000 Service Pack 3 (SP3)
will contain these fixes when it is released.For additional information about the COM+ Hotfix
Rollup Package 18.1, click the article number below to view the article in the
Microsoft Knowledge Base:
313582Â
(http://kbalertz.com/Feedback.aspx?kbNumber=313582/EN-US/
)
INFO: Availability of Windows 2000 Post-Service Pack 2 COM+ Hotfix Rollup Package 18.1
- If you are using SQL Server 2000, install SQL Server 2000
Service Pack 1 (SP1) or later.
For more information about the
availability of SQL Server 2000 service packs, browse to the following
Microsoft Web site: - If you need a fix for MDAC 2.7 performance issues, contact
Microsoft Product Support Services. MDAC 2.7 SP1 will contain these fixes when
it is released.
- You must explicitly call the Dispose method on objects that inherit from the System.EnterpriseServices.ServicedComponent class. Under stress, the handle count can increase by up to
several thousand (10,000 to 30,000) before being freed if you do not explicitly
call Dispose.WARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own
risk.
For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
312118Â
(http://kbalertz.com/Feedback.aspx?kbNumber=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.
APPLIES TO
- Microsoft COM+ 1.0
- Microsoft ASP.NET 1.0
- Microsoft Data Access Components 2.7
- Microsoft .NET Framework Service Pack 2
- Microsoft SQL Server 2000 Standard Edition
| kbbug kbcomservices kberrmsg kbfix kbperformance kbscalability KB318000 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate