TABLE OF CONTENTS Besides providing performance and usage information, periodically analyzing W3C extended log files gives you the inside view of server health status. HTTPERR and URLSCAN log files provide further details that are not captured in the W3C extended log file. Analyzing these different log files helps to ensure the stability of your IIS server. Key capabilities include identifying ASP errors with the request details, error codes, and messages; understanding the difference between client side versus service side errors; translating HTTP status code to meaningful error messages; and analyzing URLSCAN log files.
By analyzing error requests, you can determine the health of your IIS applications, find clues for troubleshooting, and identify potential risks associated with the request.
Besides the key IIS log fields introduced in previous section, you will learn more about the following new and useful log fields:
User name (cs-username) This field captures the username making the request. If anonymous access is allowed, the default IUSR_
Procotol Substatus (sc-substatus) This is a new property field for W3C extended log format introduced in IIS 6.0. In previous versions of IIS, only status codes are captured in IIS logs, making troubleshooting more troublesome, as some...
