1

Can someone recommend a good strategy for troubleshooting IIS that is hanging on Windows 2008?

Normally, I check the following in Process Explorer:

  • CPU

  • Disk I/O

  • Context Switch Delta

However, in certain situations all of these values are low and yet IIS is hung up.

Is there anything in Process Monitor (sysinternals) that should raise a red flag?

frankadelic
  • 337
  • 1
  • 4
  • 16

3 Answers3

1

When IIS is not responding but it does not look like it is doing anything, it could be that it is waiting for something. The actual problem will often depend on how your application is programmed. Here are a couple of examples.

  • A system that returns a file stored in memory to many clients. If enough clients request the file you will run out of TCP connections and the system will look like it is not doing anything.
  • The application in IIS makes a call to a web service. There is a default limit of 2 http connections, so everything gets put in a queue to wait for an available connection

Check the Httperr and IIS log

http://msdn.microsoft.com/en-us/library/aa954365(BTS.10).aspx

Shiraz Bhaiji
  • 2,229
  • 9
  • 34
  • 47
0

What do you mean by "hung up"? If you are hosting a .Net application the application itself could be hanging on a database call or something. If it is hanging while serving static files (.htm, .jpg, etc.) it could be an IIS issue.

Joshua
  • 1,546
  • 1
  • 13
  • 16
  • Specifically, it takes upwards of a 60-100 seconds to serve an ASPX page. Perhaps it is a database call - but how would I determine this using process monitoring tools? – frankadelic Sep 26 '09 at 00:25
0

Use tess blog for the procedure.

And this tool may help too.

Igal Serban
  • 1,575
  • 10
  • 6