TABLE OF CONTENTS No area in IIS 6.0 is more in need of improvement than diagnostics. Many users referred to IIS as a black box into which requests went, yet never came out. To complicate the matter further, administrators and developers were often left without any avenue to reproduce and hence correct IIS because there were no means to access request-based information at the point of failure.
In contrast, it has never been so easy to detect and isolate an error than in IIS 7.0, which offers detailed error messages that outline step-by-step instructions on what to try if a request fails. In the event that the error messages don t help, you can use IIS 7.0 s new Failed Request Tracing. This new instrumentation offers a step-bystep output as requests, one by one, enter and exit the IIS request pipeline. This detailed tracing can be enabled based on HTTP error messages or by time taken, two of the most common troubleshooting starting points. Beyond that, developers can build on IIS 7.0 s tracing to include their individual code eventing that allows administrators to see their status alongside IIS 7.0 s status. This makes debugging failures of IIS and custom code a reality without attaching a debugger.
As great as IIS 7.0 s diagnostics are, there are still areas where it can t help. It is important to understand these areas and ensure that you tackle them with the right tools to succeed.
IIS 6.0 and previous versions included custom yet not...
