Freigeben über

HOWTO: Microsoft.com OPS on Debugging IIS

  • Artikel

If you are looking for information on how to troubleshoot a variety of IIS-related issues, the following week of Webcasts from Microsoft.com OPS team is not to be missed. Mark your calendars!

Of course, these sessions focus on issues AFTER you have determined that your problem is NOT with invalid configuration but with something running awry on the server. I know, I know, distinguishing misconfiguration from buggy code is not easy, but there are tools like DebugDiag and general troubleshooting steps/guidelines to help you. And if you need help with diagnosis, post the IIS State or DebugDiag log file with a clear subject line to the microsoft.public.inetserver.iis newsgroup on msnews.microsoft.com for assistance.

I consider Microsoft.com one of the closest and best customers of IIS... because they have an incredibly seasoned and talented OPS team (former IIS can't hurt...), which allows them to be on the bleeding edge and be the first and largest consumer of beta IIS builds. As a result, they have unbelievably intimate access to the IIS product developers when it comes to debugging or feature suggestions, and they are privy to a variety of internal details and conversations you simply won't find anywhere else.

Let's just say that they definitely do their homework on issues and bring a wealth of experience to the table. I am hard pressed to name another group of people of comparable skill and experience when it comes to IIS and operations.

So... I suggest listening to what they have to say about debugging IIS. But, don't just take my word for it; see it for yourself. :-)

//David

Comments

  • Anonymous
    March 06, 2006
    I read your recommendations on debugging IIS apps.  I am taking your advice but I'm having difficulty getting a stack trace dump.

    We have an asp.net web service application (3 actually) setup to run in seperate application pools.  We are finding that one of the applications hangs intermittently but does not crash.  During this time a netstat shows a large number of CLOSED_WAIT status for connections to the server.  To fix the problem, we have found that we need to delete and recreate the application pool as it seems to become corrupt.

    We are attempting to use the IIS Toolkit Debug Diagnostics tool to get a stack trace dump when the hang occurs.  However this tool appears to only create a dump when the application crashes, rather then hangs.

    Is there a way to force a stack trace dump so we can analyze where the application hangs to attempt to resolve the bug.

    Thanks.
    Boro
  • Anonymous
    March 06, 2006
    The comment has been removed
  • Anonymous
    May 13, 2008
    You can find solutions at www.howto-microsoft.com