| Aaron King 2004-01-24, 1:46 am |
| My advice would be to wait untill the problem occurs then run :
iisstate -p 1000
This will log all the threads of the process while in the error state. If
you have multiple w3wp.exe processes run iisstate for each PID, then check
in the log to try and match the PID to the application in question. You
might also want to log the inetinfo process if all of IIS is hanging.
Aaron
<scott_mcarthur2003@yahoo.co.uk> wrote in message
news:92c92d63.0401160425.3eaa2abd@posting.google.com...quote:
> I am experiencing periodic periods when iis6 grinds to a halt. I am
> trying to use iisstate to debug however I am a bit unsure about how to
> run it.
>
> 1. Should I wait until the web site hangs and then run iissate from
> the command line like iisstate.exe -p 1000
>
> 2. Or should i run it using the a command like iisstate.exe -p 1000
> -sc with the soft crash action. If so I understand this would
> terminate the process. Does this mean that IIS would be stopped
> completely when iisstate runs?
>
> Scott
|