First of all, i would check these places:
- Event log
- IIS log file
- httperr log file
- Use WFetch to see what is actually returned by IIS (if anything)
If nothing above gives any result, i would do this:
- Does it work locally?
If yes, then it is not likely to be a problem with IIS. Start by checking
- Is it isolated to one specific website (application pool)?
If yes, then it is likely to be a problem with a specific application.
Debug that application.
- If IIS truly "hangs" and nothing works, use Crash/Hang agent
or Debug Diagnostic Tool v1.1
http://www.gafvert.info/iis/ - IIS Related Info
Wendell Crain wrote:
>I have an IIS 6.0 on W2K3 server sitting in one of our DMZs. All of the
>patches should be up-to-date. Starting last Thursday, users complained of
>no response from the application. From the web it appeared as though the
>site was down. Looking from the Event Viewer and the Admin Consoles,
>everything was running normally without any errors. I ended up issuing an
>'IISRESET' command to get the site back up. Less than an hour later, it
>occurred again. This time, I rebooted the server. On Friday, it happened
>in the morning-reboot. And then it happened again late afternoon and I
>used 'IISRESET'. Nothing again until Saturday afternoon and I used
>'IISRESET'. Nothing on Sunday and so far today nothing has occurred. It
>has me rather concerned as this is a new site for us replacing some older
>software. It is pretty important we keep access up 24x7 without
>unexplained downtimes. I am not familiar enough with IIS and cannot seem
>to find what is actually causing the web server to hang. Does anyone have
>a suggestion as to what it could be or where to even begin? Thanks!