Troubleshooting Failed Requests Using Tracing in IIS 8.5
Request-based tracing is available both in stand-alone IIS Servers and on Windows Azure Web Sites (WAWS) and provides a way to determine what exactly is happening with your requests and why it is happening, provided that you can reproduce the problem that you are experiencing. Problems like poor performance on some requests, or authentication-related failures on other requests, or the server 500 error from ASP or ASP.NET can often be difficult to troubleshoot--unless you have captured the trace of the problem when it occurs. the following article discusses failed request tracing on IIS Server. For information about doing this with Windows Azure Web Sites , click here.
Failed-request tracing is designed to buffer the trace events for a request and only flush them to disk if the request "fails," where you provide the definition of "failure". If you want to know why your requests are returning a specific HTTP status code, e.g., 401 or 404, or if a request is taking a while to process or is not responding, then you can use failed request tracing.
The tasks that are illustrated in this article include:
- Enabling the failed-request tracing module
- Configuring failed-request tracing log-file semantics
- Defining the URL for which to keep failed request traces, including failure definitions and areas to trace
- Generating the failure condition and viewing the resulting trace
You must install IIS 8.5 before you can perform the tasks in this article. Browse to
http://localhost/ and verify that the Internet Information Services splash screen is displayed. If IIS is not installed, see Installing IIS 8.5 on Windows Server 2012 R2 for installation instructions. When installing IIS, make sure that you also install the following:
- ASP.NET 3.5 (under Web Server (IIS)/Web Server/Application Development Features/ASP.NET 3.5)
- ASP.NET 4.5 (under Web Server (IIS)/Web Server/Application Development Features/ASP.NET 4.5)
- Tracing (under Web Server (IIS)/Web Server/Health and Diagnostics - Tracing)
Log In as Administrator
Ensure that the account that you use to log in is the administrator account or is in the Administrators group.
Being in the Administrators group does not grant you complete administrator user rights by default. You must run applications as Administrator, which you can do by right-clicking on the application icon and selecting Run as administrator.
Make a Backup
You must make a backup of the configuration before doing the following tasks.
To make a backup of the configuration:
- Click the Windows logo key and the X key simultaneously, click Command Prompt (Admin), and then click Yes.
- In the command prompt, run the following command:
%windir%\system32\inetsrv\appcmd add backup cleanInstall
The above command creates a cleanInstall folder containing backup configuration files in
Create Sample Content
- Navigate to
- Move the content to a secure location (in case you want to restore the existing content) or delete it.
- Create a blank file and name it test.asp.
- In the command prompt, navigate to the test.asp file in \inetpub\wwwroot.
- In the test.asp file, paste the following content:
<h2>Failed Request Tracing Lab</h2><br> <br>Today's date is <% response.write(Date()) %>
ASP must be disabled for this task. ASP is disabled only as an example and for the purposes of the tasks in this article.
To disable ASP:
- Open IIS Manager and select the server.
- Double-click ISAPI and CGI Restrictions.
- In the ISAPI and CGI Restrictions pane, select Active Server Pages. In the Actions pane, click Deny to disable ASP . Active Server Pages will show as "Not Allowed".
Enable Failed-Request Tracing
After you enable failed-request tracing, you need to configure where the log files will reside. In this task, you will enable failed-request tracing for the Default Web Site and specify where to put the log files. You will then configure the failure for which to generate failure logs.
Step 1: Enable Failed-Request Tracing for the Site and Configure the Log File Directory
- Open a command prompt with administrator user rights, and navigate to
- Launch inetmgr.
- In the Connections pane, expand the machine name, expand Sites, and then click Default Web Site.
- In the Actions pane, under Configure, click Failed Request Tracing….
- In the Edit Website Failed Request Tracing Settings dialog box, configure the following:
- Select the Enable check box.
- Keep the defaults for the other settings.
- Click OK.
Failed-request tracing logging is now enabled for the Default Web Site. Check the %windir%\system32\inetsrv\config\applicationHost.config file to confirm that the configuration looks as follows:
<system.applicationHost> <!-- other system configuration --> <sites> <site name="Default Web Site" id="1"> <!-- other site configuration --> <traceFailedRequestsLogging enabled="true" /> </site> <! -- site & app defaults --> <!-- other sites configuration --> </sites> <!-- other system configuration --> </system.applicationHost>
Step 2 : Configure Your Failure Definitions
In this step, you will configure the failure definitions for your URL, including what areas to trace. You will troubleshoot a 404.2 that is returned by IIS for any requests to extensions that have not yet been enabled. This will help you determine which particular extensions you will need to enable. For more information, see The HTTP status code in IIS 7.0, IIS 7.5, and IIS 8.0.
Open a command prompt with administrator user rights.
In the Connections pane, expand the machine name, expand Sites, and then click Default Web Site.
Double-click Failed Request Tracing Rules.
In the Actions pane, click Add....
In the Add Failed Request Tracing Rule wizard, on the Specify Content to Trace page, select All content (*). Click Next.
On the Define Trace Conditions page, select the Status code(s) check box and enter 404.2 as the status code to trace.
On the Select Trace Providers page, under Providers, select the WWW Server check box and clear all other check boxes. Under Areas, select the Security check box and clear all other check boxes. The problem that you are generating causes a security error trace event to be thrown. In general, authentication and authorization (including ISAPI restriction list issues) problems can be diagnosed by using the WWW Server – Security area configuration for tracing. However, because the FREB.xsl style sheet helps highlight errors and warnings, you can still use the default configuration to log all events in all areas and providers.
Under Verbosity, select Verbose.
When you install the Tracing role service, IIS installs the WWW Server, ASP, and ISAPI Extension trace providers by default. For more information on these providers, see IIS Providers and How to Create a Provider File for Request-Based Tracing. If you install ASP.NET 2.0 or above, IIS automatically adds the ASPNET trace provider. Additional providers are installed by the Application Request Routing (ARR) installer package, which also installs the URL Rewrite module, Web Farm Management, and External Cache. You can add more trace providers by using the
<add>element within the
You should see the following definition for the Default Web Site:
IIS Manager writes the configuration to the
%systemdrive%\config inetpub\wwwroot\web.config file by using a
<location> tag. The configuration should look as follows:
<configuration> <system.webServer> <tracing> <traceFailedRequests> <add path="*"> <traceAreas> <add provider="WWW Server" areas="Security" verbosity="Verbose" /> </traceAreas> <failureDefinitions statusCodes="404.2" /> </add> </traceFailedRequests> </tracing> </system.webServer> </configuration>
Test and View the Failure Request Log File
In this task, you will generate a failed request and view the resulting trace log. You already configured IIS to capture trace logs for http://localhost/*.asp` requests that fail with an HTTP response code of 404.2. Now verify that it works.
Step 1: Generate an Error and the Failure Request Log File
- Open a new Internet Explorer window.
- Type in the following address:
- You should see the following:
Step 2: View the Failure Request Log File
Now that you have generated a failed request, open Windows Explorer and navigate to
Notice a few things here: When IIS writes the failed request log file, it writes one file per failed request. A freb.xsl style sheet is also written, one per directory. This helps when you view the resulting failure request log files (such as fr000001.xml above).
Right-click the log file for the 404.2 error, and click Open With -> Internet Explorer. If this is the first time that you are opening a Failed Request Tracing file, you must add about:internet to the list of trusted sites, since Internet Explorer's Enhanced Security Configuration is enabled by default. If this is the case, you will see the following:
In the Internet Explorer dialog box, add about:internet to the list of trusted sites by selecting the Tools menu, selecting Internet Options, clicking the Security tab, selecting Trusted Zone, and then selecting Sites. This allows the XSL to work. You will see the following after adding about:internet to the list of trusted sites:
A summary of the failed request is logged at the top, with the Errors & Warnings table identifying any events that are WARNING, ERROR, or CRITICAL ERROR in severity. In this example, the WARNING severity level is due to ISAPI RESTRICTION. The image that you tried to load was
Open the raw XML file directly by using a text editor, and look at the contents of the event.
You have completed two tasks: configuring failed request tracing to capture traces for any request that IIS returns with a 404.2 status code; and verifying that IIS captured the trace for your request. You also verified that the freb*.xml log file did not contain any requests other than those with a 404.2 return code. When you consulted the failure log file, you determined that the cause of the failure was that the extension was disabled for that request. You can try other non-HTML pages (like gifs or jpgs) and note that the log file does NOT add these traces. You can also easily change this event to be 404, or capture the failure if the request takes longer than 30 seconds by setting the timeTaken field in your failureDefinitions.
Restore Your Backup
Now that you have completed the tasks in this article, you can restore the backup of the configuration. Run the following command with administrator user rights:
%windir%\system32\inetsrv\appcmd restore backup cleanInstall