Article ID: 281335
This article was previously published under Q281335
We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 6.0 running on Microsoft Windows Server 2003. IIS 6.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:
When you troubleshoot Internet Information Server (IIS), it is a common practice to isolate Web applications by running them in a separate memory space, which is referred to as Out-of-Process (OOP). However, sometimes if a component is used on multiple ASP pages, and in multiple Web applications, it can be difficult to isolate the module (DLL) that contains the object from the rest of the Web site. Sometimes you must isolate a COM DLL into a separate process to determine if it contributes to problems that affect Web server performance. Component Services (COM+) 1.0, in Microsoft Windows 2000, provides the ability to isolate a COM DLL into a separate process.
The steps that follow provide a procedure for isolating a DLL. After the DLL is isolated, any process that uses the isolated DLL makes RPC calls to the Dllhost.exe process that contains the isolated DLL, rather than loading the DLL within its own process space.
How to Isolate a COM DLL in Windows 2000
REFERENCESFor additional information about isolating a COM DLL in Microsoft Windows NT 4.0, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/281434/EN-US/ )How to isolate a DLL into a separate process using Microsoft Transaction Server (MTS)
(http://support.microsoft.com/kb/290884/EN-US/ )HOWTO: Determine Which Application Is Running Within a COM+ or Transaction Server Package
Article ID: 281335 - Last Review: August 31, 2012 - Revision: 2.0