NET, or for other specific conditions, but a generic rule for HTTP 500 errors is useful for discovering a variety of error conditions on your Web server.You can also enable failed request tracing from a command prompt by using the App utility with the following syntax: set config -section:system.application Host/sites /[name='Default Web Site'].trace Failed Requests Logging.enabled:"True" /commit:set config -section:system.application Host/sites /[name='Default Web Site'].trace Failed Requests Logging.directory:"%System Drive%\inetpub\logs\Failed Req Log Files" /commit:set config -section:system.application Host/sites /[name='Default Web Site'].trace Failed Requests Log Files:"50" /commit:apphost In this section, we will generate a few errors using classic ASP in order to examine how failed request tracing will help identify potential problems.Even though these examples will target specific circumstances where you know the cause of the failure, you can use the techniques that will be presented to troubleshoot situations where the cause of the failure is unknown.
This is because the ASP errors typically occur when you are not actively troubleshooting your system, so that sometimes your only option is to search your IIS activity logs and hope that the ASP module returns additional information in the log entries for failed requests.
In the following example that uses Failed Request Tracing, you have a detailed record of the failure that you can use to troubleshoot the situation.
The following steps will configure a failed request tracing rule for HTTP 500 errors, which you will use later to troubleshoot classic ASP error messages.
In this error condition, you will examine an ASP page that attempts to create an instance of an invalid COM class, and this situation is most often produced by misspelling a valid COM class.
One of the great troubleshooting features that is built in to IIS 7.0 and above is Failed Request Tracing, which lets you configure tracing rules on your server that will create detailed troubleshooting log files for custom failure conditions that you define.
For example, you can capture the details for authentication failures by creating tracing rules that create log files for HTTP 401 errors.
Failed Request Tracing in IIS can be configured to passively trace failures.
This means that you can add tracing rules to IIS that will create log files when errors occur, even if you are not actively monitoring your server.
For example, the steps in this walkthrough will show you how to create a tracing rule that will create trace logs whenever an HTTP 500 error occurs.
This method of passive tracing is known as "no-repro" tracing, which means that you can periodically examine your server's logs to check if any failures have occurred, and then take action only when IIS has created logs.
You need to make sure that you follow the steps in this document by using an account that has full administrative permissions.