How to find out source of dllhost.exe

[Rollin 4 Eva]

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

[Bob Barrows]

Rollin 4 Eva wrote:

"Aaron Bertrand - MVP" <aa***@TRASHasp faq.com> wrote in message
news:eI******** ******@TK2MSFTN GP09.phx.gbl...
OK try running this code on your server and tell me this doesn't
create an endless loop.
<%@ Language=VBScri pt %>
set rsTemp = conn.execute("s ome sql syntax that does nothing")

I'd like to try this but I have no idea what "some sql syntax that does
nothing" means. If you mean to use a statement that raises an error, well,
you would want to detect that error before attempting to loop through a
recordset wouldn't you? Since you are using On Error Resume Next, then it
seems that it would seem logical to use

If err <> 0 then
'handle the error
else
do until rsTemp.EOF
'etc
loop
end if

wouldn't it?

Bob Barrows
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

[Rollin 4 Eva]

Well see that's where my problem is. My problem comes from a page that I
wrote in my inefficient/without error handling code writing days. I'm
pretty good about handling errors nowadays, but I find myself chasing the
ghosts of coding past. And considering that there's at least 50 different
websites on the server, I was hoping that there could be an easier way to
find the cause of the error than to manually go through every asp page on
the server and make sure error handling is handled properly.
"Bob Barrows" <re******@NOyah oo.SPAMcom> wrote in message
news:ek******** *****@TK2MSFTNG P10.phx.gbl...

Rollin 4 Eva wrote:

"Aaron Bertrand - MVP" <aa***@TRASHasp faq.com> wrote in message
news:eI******** ******@TK2MSFTN GP09.phx.gbl...

OK try running this code on your server and tell me this doesn't
create an endless loop.
<%@ Language=VBScri pt %>
set rsTemp = conn.execute("s ome sql syntax that does nothing")

I'd like to try this but I have no idea what "some sql syntax that does
nothing" means. If you mean to use a statement that raises an error, well,
you would want to detect that error before attempting to loop through a
recordset wouldn't you? Since you are using On Error Resume Next, then it
seems that it would seem logical to use

If err <> 0 then
'handle the error
else
do until rsTemp.EOF
'etc
loop
end if

wouldn't it?

Bob Barrows
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.