It is important to understand how to enable tracing and create rules to capture the events you are looking for.
A key aspect of failed request tracing is the understanding of how to scope rules to remove noise from the log files and help narrow down the problem. In such cases, you might only want to establish rules for a particular error or condition
To use tracing in IIS 7.0, we first must add in Windows:
1. Click the Windows button and navigate to Control Panel.
2. From Control Panel Home (not Classic View, although you could take that route as well), click Programs | Turn Windows features on or off.
3. From within the Windows Features window, expand Internet Information Services | World Wide Web Services | Health and Diagnostics.
4. Check the Tracing check box and then click the OK button
Using IIS Manager
To start the configuration Failed Request Tracing Rules, you use IIS Manager to enable Failed Request Tracing for a given Web application. Although you can define rules by virtual directory or by Web application level, the failed request tracing feature must be enabled at the site level first:
1. Using IIS Manager, navigate down to your target Web site.
2. Click Failed Request Tracing Rules and then click the Open Feature in the Actions pane.
3. Click Edit Site Tracing… from the Actions pane.
4. Check the Enable check box.
5. Define the directory location where all failed request files will be stored and the maximum number of log files you’d like maintained.
6. Click the OK button.