Logging begins automatically in the System, Security, and Application logs whenever Windows is started. For each type of log, you can filter the events to be viewed, designate the number of entries to view, decide how long to save entries, and decide whether to automatically overwrite existing events when the log becomes full.
ASP errors are sent to the Windows Event Log (in the Application Log) when the Write unsuccessful client requests to event log check box is selected on the Process Options property sheet. This check box corresponds to the metabase property AspLogErrorRequests; that is, when this check box is selected, AspLogErrorRequests has a value of TRUE. When this check box is not selected, AspLogErrorRequests has a value of FALSE.
Another metabase property, AspErrorsToNTLog, determines which ASP errors are sent to the Windows Event Log. The default value of AspErrorsToNTLog is FALSE. This means that only a certain subset of ASP errors are sent to the Windows Event Log. If AspErrorsToNTLog has a value of TRUE, then all ASP errors are sent to the Windows Event Log.
The following ASP errors will be sent to the Windows Event Log when the Write unsuccessful client requests to event log check box is selected on the Process Options property sheet and AspErrorsToNTLog has a value of FALSE due to their important nature:
100, 101, 102, 103, 104, 105, 106, 107, 115, 190, 191, 192, 193, 194, 240, 241, 242.
For descriptions of these errors, see Active Server Pages Events.
The value of AspErrorsToNTLog cannot be set through the use of the IIS snap-in; you must programmtically set this property. For more information on the metabase and programmatic administration of IIS, see Administering IIS Programmatically.
Note If logging ASP errors to the IIS log fails, these errors will be sent to the Windows Event Log.