IIS Out-of-Process Applications Stop Responding

This article was previously published under Q328693
This article has been archived. It is offered "as is" and will no longer be updated.
When an application is configured to run out-of-process (that is, in medium or high isolation), the application may stop responding (hang) or cause Web browser requests to time out. Refreshing the browser appears to correct the problem, but the problem appears more frequently with a heavier load on the server.
This occurs in the Dllhost.exe process that is hosting the application because Asynchronous Procedure Calls (APCs) can inadvertently alert a worker thread that is responsible for cleaning up Web Application Manager (WAM) requests. When this occurs, the WAM_REQUEST and WAM_EXEC_INFO objects can be leaked.

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

Hotfix Information

To resolve this problem, obtain Microsoft COM+ Rollup Hotfix 23.
To work around this problem, set the application protection for the application to Low. When you do this, COM+ does not have to marshal data between the Inetinfo.exe and Dllhost.exe processes.
Microsoft has confirmed that this is a problem in Microsoft Internet Information Services 5.0. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 Datacenter Program and Windows 2000 Datacenter Server Product

Article ID: 328693 - Last Review: 01/17/2015 06:02:55 - Revision: 2.1

Microsoft Internet Information Services 5.0

  • kbnosurvey kbarchive kbiiscom kbwin2ksp4fix kbbug kbfix kbwin2000presp4fix KB328693
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)