Any other way to find out WHY dllhost.exe is looping...bes..

I am trying to catch the beginning of the loop in DLLHOST.EXE. I have
Perfmon running, monitoring for a 50% condition. Does it make sense to
execute iisstate out of Perfmon when the condition hits? Or is there a
better way?

TIA,

Larry Woods

"David Wang [Msft]" <someone.TakeThisOut@online.microsoft.com> wrote in message
news:uPUF2SOcDHA.2460@TK2MSFTNGP10.phx.gbl...
 > Unless you know how to debug a NT process yourself given the debuggers in
 > the MS Debugging Toolkit, IISState is your only choice.
 >
 > Debugger installation should not require a reboot unless you intentionally
 > cause it to happen.
 >
 > --
 > //David
 > IIS
 > This posting is provided "AS IS" with no warranties, and confers no
rights.
 > //
 > "Larry Woods" <larry.TakeThisOut@lwoods.com> wrote in message
 > news:uz$RN9NcDHA.1492@TK2MSFTNGP12.phx.gbl...
 > My site gets into a loop about once a day. Luckily the server has dual
cpus
 > so the other dllhost.exe keeps the site up. On the other hand, once in a
 > while BOTH cpus get the loop so that brings us down. All I know is that
 > dllhost.exe is looping. How do I find out WHERE? Is iisstate the only
 > answer?
 >
 > TIA,
 >
 > Larry Woods
 >
 >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Any other way to find out WHY dllhost.exe is looping...bes.. 

Hi Larry,

Thank you for replying!

IISstate3.0 is available in IIs6 resource kit. Please go to:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=56fc
92ee-a71a-4c73-b628-ade629c89499

Furthermore, you can obtaint the 3.1 from a 3rd party web site. Please go
to:
http://www.iisfaq.com/default.aspx?View=P197&P=1

Thank you for using Microsoft NewsGroup!

Wei-Dong Xu
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
-------
This response contains a reference to a third-party World Wide Web site.
Microsoft is providing this information as a convenience to you. Microsoft
does not control these sites and has not tested any software or information
found on these sites; therefore, Microsoft cannot make any representations
regarding the quality, safety, or suitability of any software or
information found there. There are inherent dangers in the use of any
software found on the Internet, and Microsoft cautions you to make sure
that you completely understand the risk before retrieving any software from
the Internet.
 >> Stay informed about: Any other way to find out WHY dllhost.exe is looping...bes.. 

I would suggest getting any IISState capture of the machine when it is in
the error condition. Timing is a nice-to-have.

While it would be nice for the capture to happen right as the error
condition happens (the better the correlation, the more accurate the
analysis), if you're reasonably close, it's possible to figure out what
happened... especially on a loop since it'd be the one that's still hanging
around while all the non-loop threads will hopefully look idle.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Larry Woods" <larry.RemoveThis@lwoods.com> wrote in message
news:eroJ52UcDHA.1696@TK2MSFTNGP10.phx.gbl...
I am trying to catch the beginning of the loop in DLLHOST.EXE. I have
Perfmon running, monitoring for a 50% condition. Does it make sense to
execute iisstate out of Perfmon when the condition hits? Or is there a
better way?

TIA,

Larry Woods

"David Wang [Msft]" <someone.RemoveThis@online.microsoft.com> wrote in message
news:uPUF2SOcDHA.2460@TK2MSFTNGP10.phx.gbl...
 > Unless you know how to debug a NT process yourself given the debuggers in
 > the MS Debugging Toolkit, IISState is your only choice.
 >
 > Debugger installation should not require a reboot unless you intentionally
 > cause it to happen.
 >
 > --
 > //David
 > IIS
 > This posting is provided "AS IS" with no warranties, and confers no
rights.
 > //
 > "Larry Woods" <larry.RemoveThis@lwoods.com> wrote in message
 > news:uz$RN9NcDHA.1492@TK2MSFTNGP12.phx.gbl...
 > My site gets into a loop about once a day. Luckily the server has dual
cpus
 > so the other dllhost.exe keeps the site up. On the other hand, once in a
 > while BOTH cpus get the loop so that brings us down. All I know is that
 > dllhost.exe is looping. How do I find out WHERE? Is iisstate the only
 > answer?
 >
 > TIA,
 >
 > Larry Woods
 >
 >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Any other way to find out WHY dllhost.exe is looping...bes..