IIS and Event Logs
|
|
IIS also generates error, warning, and informational events that can be displayed using Event Viewer. Whenever a problem occurs with IIS, it’s a good idea to review the System and Application logs in Event Viewer to see if there is any useful information there that can be used for troubleshooting purposes. Events can be logged for IIS services like the WWW Service or FTP Service, for ASP or ASP.NET applications, and so on.
The list of possible events IIS can generate is long; for a detailed list, see the Events Reference in IIS Help. Here I’ll just mention a few tips regarding IIS events in the event logs.
Logging ASP Events
There are two metabase properties that can be used to configure how logging of ASP errors occurs in the Application log. AspLogErrorRequests controls whether unsuccessful client requests for ASP pages are logged to the event logs, while AspErrorsToNTLog controls whether such errors are logged to the web logs. Table 13-6 shows how configuring these two properties affects logging of ASP errors to event and web logs.
| AspLogErrorRequests | AspErrorsToNTLog | Result |
|---|---|---|
| True | True | All ASP errors are logged to Application log and also to the web logs. |
| True | False | Some common ASP errors are logged to Application log but not to the web logs. |
| False | True | All ASP errors are logged to the web logs. |
| False | False | Some common ASP errors are logged to the web logs. |
You can also completely disable logging of ASP errors using the DontLog and LogType metabase properties.
Eventquery.vbs
Windows Server 2003 includes an admin script called eventquery.vbs that can be used to list events of specified types from the command line. The output from running this script can be formatted as a table, list, or comma-separated (*.csv) file for importing into a spreadsheet or database for further analysis. For more information, see the command-line reference in the Help and Support Center.
|
|
