如何找到dllhost.exe的源代码 [英] How to find out source of dllhost.exe

问题描述

我有一台运行大约50个网站的Windows 2000服务器，所有运行ASP脚本的b
。我注意到服务器的CPU使用率有时会上升100％

，由dllhost.exe引起，我肯定是一个挂起的ASP脚本

某处在盒子上。可能是错误恢复下一行，当遇到错误时，无法在任何地方进行
。无论如何，我不确定是否有一种方法来隔离它的原始网站，甚至是这个问题所源自的网页。有没有办法做到这一点？任何帮助都会受到赞赏，因为这个问题正在减缓每个人的服务器速度。 TIA

获取任何帮助/建议。


Rollin

解决方案

" ; Rollin 4 Eva < TE ** @ test.com>在消息中写道

news：o _ ******************** @ giganews.com ...

I 有一个运行着大约50个网站的Windows 2000服务器，所有这些服务器都在运行ASP脚本。我注意到服务器的CPU使用率有时会上升100％，这可能是由dllhost.exe导致的，我肯定会在盒子的某个地方悬挂ASP
脚本。可能是错误恢复下一行，当遇到错误时，没有
去任何地方。无论如何，我不确定是否有一种方法来隔离它的起源网站，甚至是这个问题所源自的网页。有没有办法做到这一点？任何帮助都会得到
，因为这个问题正在减缓每个人的服务器速度。 TIA
任何帮助/建议。

进入组件服务MMC。点击状态视图 COM +中的按钮。它将向你显示每个DllHost进程的PID。


-

Tom Kaminski IIS MVP
< a rel =nofollowhref =http://www.iistoolshed.com/target =_ blank> http://www.iistoolshed.com/ - 用于运行IIS的工具，脚本和实用程序
http://mvp.support.microsoft.com/
http://www.microsoft.com/windowsserv。 ..y / centers / iis /

>可能是错误恢复下一行，当遇到错误时，它不会在任何地方出现

。


不，这不会导致它...错误恢复下一次不会去任何地方......

它只是忽略导致错误的行并移动到下一行

（因此恢复下一个部分）。

无论如何，我不确定是否存在这是一种隔离网站起源的方式，甚至是这个问题所源自的网页。有没有办法做到这一点？任何帮助都会得到
，因为这个问题正在减缓每个人的服务器速度。 TIA
任何帮助/建议。

我认为你必须使用试验和错误...将所有网站移动到隔离的

你应该能够以这种方式跟踪它（因为每个站点都有自己的dllhost.exe

）。


A

" Aaron Bertrand - MVP" < AA *** @ TRASHaspfaq.com>在消息中写道

news：up ************** @ TK2MSFTNGP09.phx.gbl ...

当遇到错误时，可能会出现错误恢复下一行没有去的地方。
不，这不会导致它...错误恢复下一次没有' 't" go

where...它只是忽略导致错误的行并移到下一行
（因此恢复下一个部分）。
那么当我尝试打开一个记录集时会发生错误（

主要是所有使用dbase连接的页面）？如果下一个

行没有rsTemp.EOF怎么办？

这不会导致无限循环吗？

无论如何，我不确定是否有一种方法来隔离它的原始网站，甚至是这个问题所源自的网页
。有没有办法做到这一点？任何帮助都是

赞赏，因为这个问题正在减慢每个人的服务器速度。
TIA提供任何帮助/建议。

我认为你必须使用反复试验......将所有网站移到隔离的地方
你应该能够以这种方式跟踪它（因为每个站点

有自己的dllhost.exe）。
不确定你的意思是孤立的。在Windows 2000 Server上运行IIS BTW

谢谢。

Rollin

A

I''ve got a Windows 2000 server running with about 50 websites on it, all
running ASP scripts. I''ve noticed that the servers CPU usage gets up 100%
sometimes, caused by dllhost.exe, which I''m certain is a hanging ASP script
somewhere on the box. Probably an on error resume next line that doesn''t go
anywhere when an error is an encountered. Anyways, I''m not sure if there''s
a way to isolate the website where its originating, or even the page this
problem is originating from. Is there a way to do this? Any help would be
appreciated, as this problem is slowing down the server for everyone. TIA
for any help/advice.

Rollin

解决方案

"Rollin 4 Eva" <te**@test.com> wrote in message
news:o_********************@giganews.com...

I''ve got a Windows 2000 server running with about 50 websites on it, all
running ASP scripts. I''ve noticed that the servers CPU usage gets up 100%
sometimes, caused by dllhost.exe, which I''m certain is a hanging ASP script somewhere on the box. Probably an on error resume next line that doesn''t go anywhere when an error is an encountered. Anyways, I''m not sure if there''s a way to isolate the website where its originating, or even the page this
problem is originating from. Is there a way to do this? Any help would be appreciated, as this problem is slowing down the server for everyone. TIA
for any help/advice.

Go into Component Services MMC. Click the "Status View" button in COM+. It
will show you the PID for each DllHost process.

--
Tom Kaminski IIS MVP
http://www.iistoolshed.com/ - tools, scripts, and utilities for running IIS
http://mvp.support.microsoft.com/
http://www.microsoft.com/windowsserv...y/centers/iis/

> Probably an on error resume next line that doesn''t go

anywhere when an error is an encountered.
No, that wouldn''t cause it... on error resume next doesn''t "go anywhere"...
it just ignores the line that causes the error and moves to the next line
(hence the "resume next" part).
Anyways, I''m not sure if there''s
a way to isolate the website where its originating, or even the page this
problem is originating from. Is there a way to do this? Any help would be appreciated, as this problem is slowing down the server for everyone. TIA
for any help/advice.

I think you''d have to use trial and error... move all sites into isolated
and you should be able to track it down that way (since each site would have
its own dllhost.exe).

A

"Aaron Bertrand - MVP" <aa***@TRASHaspfaq.com> wrote in message
news:up**************@TK2MSFTNGP09.phx.gbl...

Probably an on error resume next line that doesn''t go
anywhere when an error is an encountered.
No, that wouldn''t cause it... on error resume next doesn''t "go

anywhere"... it just ignores the line that causes the error and moves to the next line
(hence the "resume next" part). well what if the error happens when I try to open up a recordset (which
mostly all the pages that use a dbase connection do)? And what if the next
line is do while not rsTemp.EOF?
Wouldn''t that cause an endless loop?

Anyways, I''m not sure if there''s
a way to isolate the website where its originating, or even the page this problem is originating from. Is there a way to do this? Any help would be

appreciated, as this problem is slowing down the server for everyone. TIA for any help/advice.

I think you''d have to use trial and error... move all sites into isolated
and you should be able to track it down that way (since each site would

have its own dllhost.exe). Not sure what you mean by isolated. Running IIS on Windows 2000 Server BTW

Thanks.
Rollin

A

这篇关于如何找到dllhost.exe的源代码的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！