CINXE.COM

<!DOCTYPE HTML>   <html lang="en"> <head><script type="text/javascript" src="/_static/js/bundle-playback.js?v=HxkREWBo" charset="utf-8"></script> <script type="text/javascript" src="/_static/js/wombat.js?v=txqj7nKC" charset="utf-8"></script> <script>window.RufflePlayer=window.RufflePlayer||{};window.RufflePlayer.config={"autoplay":"on","unmuteOverlay":"hidden"};</script> <script type="text/javascript" src="/_static/js/ruffle/ruffle.js"></script> <script type="text/javascript"> __wm.init("https://web.archive.org/web"); __wm.wombat("http://www.iis.net:80/learn/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis","20130520180154","https://web.archive.org/","web","/_static/", "1369072914"); </script> <link rel="stylesheet" type="text/css" href="/_static/css/banner-styles.css?v=S1zqJCYt" /> <link rel="stylesheet" type="text/css" href="/_static/css/iconochive.css?v=3PDvdIFv" />  <meta charset="UTF-8"> <title>Troubleshooting Failed Requests Using Tracing in IIS 7 : The Official Microsoft IIS Site</title>  <meta name="keywords" content="troubleshooting; failed requests; tracing; log-file; log file; failed request tracing"/> <meta name="description" content="Request-based tracing provides a way to determine what exactly is happening with your requests and why, provided that you can reproduce the problem that you are experiencing. Problems like poor per..."/> <link rel="shortcut icon" type="image/ico" href="/web/20130520180154im_/http://www.iis.net/favicon.ico"> <link rel="apple-touch-icon-precomposed" href="/web/20130520180154im_/http://www.iis.net/touch-icon-iphone-precomposed.png"/> <link rel="apple-touch-icon-precomposed" sizes="72x72" href="/web/20130520180154im_/http://www.iis.net/touch-icon-ipad-precomposed.png"/> <link rel="apple-touch-icon-precomposed" sizes="114x114" href="/web/20130520180154im_/http://www.iis.net/touch-icon-iphone4-precomposed.png"/> <link rel="apple-touch-icon-precomposed" sizes="144x144" href="/web/20130520180154im_/http://www.iis.net/touch-icon-ipad3-precomposed.png"/> <meta name="application-name" content="The Official Microsoft IIS Site"/> <meta name="msapplication-TileColor" content="#474747"/> <meta name="msapplication-TileImage" content="http://i2.iis.net/images/iis_tile.png?cdn_id=2013-05-01-001"/> <link href="https://web.archive.org/web/20130520180154cs_/http://i1.iis.net/umbraco-beta-css/learn.min.css?cdn_id=2013-05-01-001" rel="stylesheet" type="text/css" media="all"/> </head> <body class=""> <header id="header-site" class="full-width "> <script type="text/javascript">var currentUsername = '';</script><ul id="nav-user"><li><a href="https://web.archive.org/web/20130520180154/http://login.iis.net/login/signin.aspx?ReturnUrl=http://www.iis.net/learn/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis">Sign In</a></li><li><a href="https://web.archive.org/web/20130520180154/http://login.iis.net/login/createuser.aspx?ReturnUrl=http://www.iis.net/learn/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis">Join</a></li></ul> <p id="search-site"><input type="text" name="search" id="txt-search" placeholder="Search all of IIS.NET"/><button type="submit" id="btn-search-submit"><span class="icon icon-search">Search</span></button></p><nav id="nav-primary"><a id="logo" href="https://web.archive.org/web/20130520180154/http://www.iis.net/home">IIS</a><ul><li><a href="https://web.archive.org/web/20130520180154/http://www.iis.net/home">Home</a></li><li><a href="https://web.archive.org/web/20130520180154/http://www.iis.net/downloads"> Downloads </a></li><li><a href="https://web.archive.org/web/20130520180154/http://www.iis.net/learn" class="current"> Learn </a><ul><li><a href="/web/20130520180154/http://www.iis.net/learn/get-started">Get Started</a></li> <li><a href="/web/20130520180154/http://www.iis.net/learn/install">Install</a></li> <li><a href="/web/20130520180154/http://www.iis.net/learn/manage">Manage</a></li> <li><a href="/web/20130520180154/http://www.iis.net/learn/develop">Develop</a></li> <li><a href="/web/20130520180154/http://www.iis.net/learn/publish">Publish</a></li> <li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot" class="current">Troubleshoot</a></li> <li><a href="/web/20130520180154/http://www.iis.net/learn/extensions">Extensions</a></li> <li><a href="/web/20130520180154/http://www.iis.net/learn/media">Media</a></li> <li><a href="/web/20130520180154/http://www.iis.net/learn/application-frameworks">Application Frameworks</a></li> <li><a href="/web/20130520180154/http://www.iis.net/learn/web-hosting">Web Hosting</a></li> </ul></li><li><a href="https://web.archive.org/web/20130520180154/http://www.iis.net/configreference"> Reference </a></li> <li id="solutions-menu"><a href="javascript:;">Solutions</a> <div> <ul> <li>Technologies</li> <li><a href="https://web.archive.org/web/20130520180154/http://msdn.microsoft.com/en-us/netframework/default.aspx">.NET Framework</a></li> <li><a href="https://web.archive.org/web/20130520180154/http://www.asp.net/">ASP.NET</a></li> <li><a href="https://web.archive.org/web/20130520180154/http://php.iis.net/">PHP</a></li> <li><a href="https://web.archive.org/web/20130520180154/http://www.iis.net/media">Media</a></li> <li><a href="https://web.archive.org/web/20130520180154/http://www.microsoft.com/windowsserver2008/en/us/default.aspx">Windows Server</a></li> <li><a href="https://web.archive.org/web/20130520180154/http://www.microsoft.com/SQL/default.mspx">SQL Server</a></li> <li><a href="https://web.archive.org/web/20130520180154/http://www.microsoft.com/web/gallery">Web App Gallery</a></li> <li><a href="https://web.archive.org/web/20130520180154/http://www.windowsazure.com/">Windows Azure</a></li> </ul> <ul> <li>Tools</li> <li><a href="https://web.archive.org/web/20130520180154/http://www.microsoft.com/visualstudio">Visual Studio</a></li> <li><a href="https://web.archive.org/web/20130520180154/http://www.microsoft.com/expression/">Expression Studio</a></li> <li><a href="https://web.archive.org/web/20130520180154/http://www.microsoft.com/ie/">Windows Internet Explorer</a></li> <li><a href="https://web.archive.org/web/20130520180154/http://www.microsoft.com/web/webmatrix/">WebMatrix</a></li> <li><a href="https://web.archive.org/web/20130520180154/http://www.microsoft.com/web/downloads/platform.aspx">Web Platform Installer</a></li> </ul> <ul> <li>Get Help:</li> <li><a href="https://web.archive.org/web/20130520180154/http://forums.iis.net/">Ask a Question in our Forums</a></li> <li><a href="https://web.archive.org/web/20130520180154/http://www.iis.net/feedback">More Help Resources</a></li> </ul> </div> </li> <li><a href="https://web.archive.org/web/20130520180154/http://blogs.iis.net/">Blogs</a></li><li class="last-child"><a href="https://web.archive.org/web/20130520180154/http://forums.iis.net/">Forums</a></li></ul></nav> </header> <div class="full-width"> <nav id="breadcrumb"><p><a href="/web/20130520180154/http://www.iis.net/home">Home</a><a href="/web/20130520180154/http://www.iis.net/learn">Learn</a><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot">Troubleshoot</a><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/using-failed-request-tracing">Chapter 5. Using Failed Request Tracing</a><span>Troubleshooting Failed Requests Using Tracing in IIS 7</span></p></nav> <div class="page two-right"> <input type="hidden" id="loggedIn" value="False"/> <section class="col-article"> <article><header><h1>Troubleshooting Failed Requests Using Tracing in IIS 7 <span></span></h1><p>By <a href="#author-info">IIS Team</a></p><p>December 12, 2007</p></header><h2>Introduction </h2> <p>Request-based tracing provides a way to determine what exactly is happening with your requests and why, 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. </p> <p>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 you're getting 404.2 error messages or request start hanging, use failed-request tracing. </p> <p>The tasks that are illustrated in this article include: </p> <ul> <li>Enabling the failed-request tracing module </li> <li>Configuring failed-request tracing log-file semantics </li> <li>Defining the URL for which to keep failed request traces, including failure definitions and areas to trace </li> <li>Generating the failure condition and viewing the resulting trace </li></ul> <h2>Prerequisites </h2> <h3>Install IIS </h3> <p>You must install IIS 7 or above before you can perform the tasks in this article. Browse to <a href="https://web.archive.org/web/20130520180154/http://localhost/" mce_href="http://localhost/">http://localhost/</a> to see if IIS is installed. If IIS is not installed, see <a href="/web/20130520180154/http://www.iis.net/learn/install/installing-iis-7/installing-iis-7-and-above-on-windows-server-2008-or-windows-server-2008-r2" mce_href="/learn/install/installing-iis-7/installing-iis-7-and-above-on-windows-server-2008-or-windows-server-2008-r2">Installing IIS on Windows Server 2008</a> for installation instructions. When installing IIS, make sure that you also install the following: </p> <ul> <li>ASP.NET (under World Wide Web Services - Application Development Features - ASP.NET) </li> <li>Tracing (under World Wide Web Services - Health and Diagnostics - Tracing) </li></ul> <h3>Log In as Administrator </h3> <p>Ensure that the account that you use to log in is the administrator account or is in the Administrators group. </p> <p><strong>Note: </strong>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 <strong>Run as administrator</strong>. </p> <h3>Make a Backup </h3> <p>You must make a backup of the configuration before doing the following tasks. </p> <p><strong>To make a backup of the configuration:</strong> </p> <ol> <li>Click <strong>Start</strong> -> <strong>All Programs</strong> -> <strong>Accessories</strong>. </li> <li>Right-click <strong>Command Prompt</strong>, and then click <strong>Run as administrator</strong>.</li></ol> <p><a href="https://web.archive.org/web/20130520180154/http://i1.iis.net/media/7191879/troubleshooting-failed-requests-using-tracing-in-iis-266-file1.jpg?cdn_id=2013-05-01-001"><img border="0" alt="" src="https://web.archive.org/web/20130520180154im_/http://i1.iis.net/media/7191879/troubleshooting-failed-requests-using-tracing-in-iis-266-file1.jpg?cdn_id=2013-05-01-001"></a> </p> <p>3. In a command prompt, run the following command: </p><pre>%windir%\system32\inetsrv\appcmd add backup cleanInstall</pre> <h3>Create Sample Content </h3> <ol> <li>Delete everything in the %<em>systemdrive</em>%\inetpub\wwwroot folder. </li> <li>In the command prompt, navigate to the test.asp file in inetpub\wwwroot.</li> <li>In the test.asp file, enter the following code: </li></ol><pre><h2>Failed Request Tracing Lab</h2><br> <br>Today's date is <% response.write(Date()) %></pre> <p> </p> <h3>Disable ASP </h3> <p>ASP must be disabled for this task. ASP is disabled only as an example and for the purposes of the tasks in this article. </p> <p><strong>To disable ASP:</strong></p> <ol> <li>Open IIS Manager.</li> <li>Double-click <strong>ISAPI and CGI Restrictions</strong>. </li></ol> <p><a href="https://web.archive.org/web/20130520180154/http://i1.iis.net/media/7191873/troubleshooting-failed-requests-using-tracing-in-iis-266-file2.jpg?cdn_id=2013-05-01-001"><img border="0" alt="" src="https://web.archive.org/web/20130520180154im_/http://i1.iis.net/media/7191873/troubleshooting-failed-requests-using-tracing-in-iis-266-file2.jpg?cdn_id=2013-05-01-001"></a> </p> <p>3. Select <strong>Active Server Pages</strong>. In the <strong>Actions</strong> pane, click <strong>Deny</strong> to disable ASP<strong><em>.</em></strong> </p> <p><a href="https://web.archive.org/web/20130520180154/http://i3.iis.net/media/7191867/troubleshooting-failed-requests-using-tracing-in-iis-266-file3.jpg?cdn_id=2013-05-01-001"><img border="0" alt="" src="https://web.archive.org/web/20130520180154im_/http://i3.iis.net/media/7191867/troubleshooting-failed-requests-using-tracing-in-iis-266-file3.jpg?cdn_id=2013-05-01-001"></a> </p> <h2>Enable Failed-Request Tracing </h2> <p>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. </p> <h3>Step 1 : Enable Failed-Request Tracing for the Site and Configure the Log File Directory </h3> <ol> <li> Open a command prompt with administrator user rights.</li> <li> Launch <strong>inetmgr</strong>.</li> <li> In the <strong>Connections </strong>pane, expand the machine name, expand <strong>Sites</strong>, and then click <strong>Default Web Site</strong>. </li> <li> In the <strong>Actions</strong> pane, under <strong>Configure</strong>, click <strong>Failed Request Tracing…</strong>.</li></ol> <p><a href="https://web.archive.org/web/20130520180154/http://i1.iis.net/media/7191861/troubleshooting-failed-requests-using-tracing-in-iis-266-file4.jpg?cdn_id=2013-05-01-001"><img border="0" alt="" src="https://web.archive.org/web/20130520180154im_/http://i1.iis.net/media/7191861/troubleshooting-failed-requests-using-tracing-in-iis-266-file4.jpg?cdn_id=2013-05-01-001"></a> </p> <p>5. In the <strong>Edit Web Site Failed Request Tracing Settings</strong> dialog box, configure the following: </p> <ul> <li> Select the <strong>Enable</strong> check box.</li> <li> Keep the defaults for the other settings.</li></ul> <p><a href="https://web.archive.org/web/20130520180154/http://i3.iis.net/media/7191855/troubleshooting-failed-requests-using-tracing-in-iis-266-file5.jpg?cdn_id=2013-05-01-001"></a> <a href="https://web.archive.org/web/20130520180154/http://i2.iis.net/media/7191795/troubleshooting-failed-requests-using-tracing-in-iis-266-troubleshooting-failed-requests-using-tracing-in-iis7-1.jpg?cdn_id=2013-05-01-001"><img border="0" alt="" src="https://web.archive.org/web/20130520180154im_/http://i2.iis.net/media/7191795/troubleshooting-failed-requests-using-tracing-in-iis-266-troubleshooting-failed-requests-using-tracing-in-iis7-1.jpg?cdn_id=2013-05-01-001"></a> </p> <p>6. Click <strong>OK</strong>. </p> <p>Failed-request tracing logging is now enabled for the Default Web Site. Check the %<em>windir</em>%\system32\inetsrv\config\applicationHost.config file to confirm that the configuration looks as follows: </p><samp><system.applicationHost><br> <sites> <br>  <br> <site name="Default Web Site" id="1"> <br>  <br> <traceFailedRequestsLogging enabled="true" /> <br> </site> <br> </sites> <br></system.applicationHost> </samp> <h3>Step 2 : Configure Your Failure Definitions </h3> <p>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. </p> <ol> <li>Open a command prompt with administrator user rights.</li> <li>Launch <strong>inetmgr</strong>.</li> <li>In the <strong>Connections </strong>pane, expand the machine name, expand <strong>Sites</strong>, and then click <strong>Default Web Site</strong>. </li> <li>Double-click <strong>Failed Request Tracing Rules</strong>.</li></ol> <p><a href="https://web.archive.org/web/20130520180154/http://i1.iis.net/media/7191849/troubleshooting-failed-requests-using-tracing-in-iis-266-file6.jpg?cdn_id=2013-05-01-001"><img border="0" alt="" src="https://web.archive.org/web/20130520180154im_/http://i1.iis.net/media/7191849/troubleshooting-failed-requests-using-tracing-in-iis-266-file6.jpg?cdn_id=2013-05-01-001"></a> </p> <p>5. Click <strong>Finish</strong>. </p> <p>6. In the <strong>Actions</strong> pane, click <strong>Add...</strong>. </p> <p>7. In the <strong>Add Failed Request Tracing Rule </strong>wizard, on the <strong>Specify Content to Trace </strong>page, select <strong>All content (*)</strong>. Click <strong>Next</strong>. </p> <p><a href="https://web.archive.org/web/20130520180154/http://i3.iis.net/media/7191843/troubleshooting-failed-requests-using-tracing-in-iis-266-file7.jpg?cdn_id=2013-05-01-001"></a><a href="https://web.archive.org/web/20130520180154/http://i3.iis.net/media/7191789/troubleshooting-failed-requests-using-tracing-in-iis-266-troubleshooting-failed-requests-using-tracing-in-iis7-2.jpg?cdn_id=2013-05-01-001"><img border="0" alt="" src="https://web.archive.org/web/20130520180154im_/http://i3.iis.net/media/7191789/troubleshooting-failed-requests-using-tracing-in-iis-266-troubleshooting-failed-requests-using-tracing-in-iis7-2.jpg?cdn_id=2013-05-01-001"></a> </p> <p>8. On the <strong>Define Trace Conditions</strong> page, select the <strong>Status code(s)</strong> check box and enter <strong>404.2</strong> as the status code to trace. </p> <p><a href="https://web.archive.org/web/20130520180154/http://i2.iis.net/media/7191837/troubleshooting-failed-requests-using-tracing-in-iis-266-file8.jpg?cdn_id=2013-05-01-001"></a><a href="https://web.archive.org/web/20130520180154/http://i1.iis.net/media/7191783/troubleshooting-failed-requests-using-tracing-in-iis-266-troubleshooting-failed-requests-using-tracing-in-iis7-3.jpg?cdn_id=2013-05-01-001"><img border="0" alt="" src="https://web.archive.org/web/20130520180154im_/http://i1.iis.net/media/7191783/troubleshooting-failed-requests-using-tracing-in-iis-266-troubleshooting-failed-requests-using-tracing-in-iis7-3.jpg?cdn_id=2013-05-01-001"></a> </p> <p> </p> <p>9. Click <strong>Next</strong>. </p> <p>10. On the <strong>Select Trace Providers</strong> page, under <strong>Providers</strong>, select the <strong>WWW Server</strong> check box. Under <strong>Areas</strong>, select the <strong>Security</strong> 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. </p> <p>Under <strong>Verbosity</strong>, select <strong>Verbose</strong>. </p> <p><a href="https://web.archive.org/web/20130520180154/http://i2.iis.net/media/7191831/troubleshooting-failed-requests-using-tracing-in-iis-266-file9.jpg?cdn_id=2013-05-01-001"></a><a href="https://web.archive.org/web/20130520180154/http://i1.iis.net/media/7191777/troubleshooting-failed-requests-using-tracing-in-iis-266-troubleshooting-failed-requests-using-tracing-in-iis7-4.jpg?cdn_id=2013-05-01-001"><img border="0" alt="" src="https://web.archive.org/web/20130520180154im_/http://i1.iis.net/media/7191777/troubleshooting-failed-requests-using-tracing-in-iis-266-troubleshooting-failed-requests-using-tracing-in-iis7-4.jpg?cdn_id=2013-05-01-001"></a> </p> <p>11. Click <strong>Finish</strong>. You should see the following definition for the <strong>Default Web Site</strong>: </p> <p><a href="https://web.archive.org/web/20130520180154/http://i2.iis.net/media/7191825/troubleshooting-failed-requests-using-tracing-in-iis-266-file10.jpg?cdn_id=2013-05-01-001"><img border="0" alt="" src="https://web.archive.org/web/20130520180154im_/http://i2.iis.net/media/7191825/troubleshooting-failed-requests-using-tracing-in-iis-266-file10.jpg?cdn_id=2013-05-01-001"></a> </p> <p>IIS Manager writes the configuration to the %windir%\system32\inetsrv\config\applicationHost.config<em> </em>file by using a <location> tag. The configuration should look as follows: </p><samp> <location path="Default Web Site"> <br> <system.webServer> <br> <tracing> <br> <traceFailedRequests> <br> <add path="*"> <br> <traceAreas> <br> <add provider="WWW Server" areas="Security" verbosity="Verbose" /> <br> </traceAreas> <br> <failureDefinitions statusCodes="404.2" /> <br> </add> <br> </traceFailedRequests> <br> </tracing> <br> </system.webServer> <br> </location></samp> <h2>Test and View the Failure Request Log File </h2> <p>In this task, you will generate a failed request and view the resulting trace log. You already configured IIS to capture trace logs for <a href="https://web.archive.org/web/20130520180154/http://localhost/*.asp">http://localhost/*.asp</a> requests that fail with an HTTP response code of 404.2. Now verify that it works. </p> <h3>Step 1 : Generate an Error and the Failure Request Log File </h3> <ol> <li>Open a new Internet Explorer window. </li> <li>Type in the following address: <a href="https://web.archive.org/web/20130520180154/http://localhost/test.asp">http://localhost/test.asp</a>. </li> <li>You should see the following: </li></ol> <p><a href="https://web.archive.org/web/20130520180154/http://i3.iis.net/media/7191819/troubleshooting-failed-requests-using-tracing-in-iis-266-file11.png?cdn_id=2013-05-01-001"><img border="0" alt="" src="https://web.archive.org/web/20130520180154im_/http://i3.iis.net/media/7191819/troubleshooting-failed-requests-using-tracing-in-iis-266-file11.png?cdn_id=2013-05-01-001"></a> </p> <h3>Step 2 : View the Failure Request Log File </h3> <ol> <li>Now that you have generated a failed request, open a command prompt with administrator user rights and navigate to %systemdrive%\inetpub\logs\FailedReqLogFiles\W3SVC1. </li> <li>Run <strong>start</strong> to start an Internet Explorer window from the directory. </li></ol> <p><a href="https://web.archive.org/web/20130520180154/http://i1.iis.net/media/7191813/troubleshooting-failed-requests-using-tracing-in-iis-266-file12.jpg?cdn_id=2013-05-01-001"><img border="0" alt="" src="https://web.archive.org/web/20130520180154im_/http://i1.iis.net/media/7191813/troubleshooting-failed-requests-using-tracing-in-iis-266-file12.jpg?cdn_id=2013-05-01-001"></a> </p> <p> </p> <p>3. Notice a few things here: When IIS writes the failed request log file, it writes one file <em>per failed request</em>. A <em>freb.xsl</em> style sheet is also written, one per directory. This helps when you view the resulting failure request log files (such as <em>fr000001.xml</em> above). </p> <p>4. Right-click the log file for the 404.2 error, and click <strong>Open With -> Internet Explorer</strong>. If this is the first time that you are opening a Failed Request Tracing file, you must add <strong>about:internet</strong> 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: </p> <p><a href="https://web.archive.org/web/20130520180154/http://i3.iis.net/media/7191807/troubleshooting-failed-requests-using-tracing-in-iis-266-file13.png?cdn_id=2013-05-01-001"><img border="0" alt="" src="https://web.archive.org/web/20130520180154im_/http://i3.iis.net/media/7191807/troubleshooting-failed-requests-using-tracing-in-iis-266-file13.png?cdn_id=2013-05-01-001"></a> </p> <p>5. In the <strong>Internet Explorer</strong> dialog box, click <strong>Add…</strong> to add <strong>about:internet</strong> to the list of trusted sites. This allows the XSL to work. You will see the following after adding <strong>about:internet</strong> to the list of trusted sites:</p> <p><a href="https://web.archive.org/web/20130520180154/http://i2.iis.net/media/7191801/troubleshooting-failed-requests-using-tracing-in-iis-266-file14.png?cdn_id=2013-05-01-001"><img border="0" alt="" src="https://web.archive.org/web/20130520180154im_/http://i2.iis.net/media/7191801/troubleshooting-failed-requests-using-tracing-in-iis-266-file14.png?cdn_id=2013-05-01-001"></a> </p> <p>A summary of the failed request is logged at the top, with the <strong>Errors & Warnings</strong> 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 %windir%\system32\inetsrv\asp.dll. </p> <p>6. Open the raw XML file directly by using a text editor, and look at the contents of each event. </p> <h2>Summary </h2> <p>You have completed two tasks: configured failed request tracing to capture traces for <em>*</em> if IIS returns it with a 404.2 status code; and verified that IIS captured the trace for your request. You also verified that the freb*.xml log file did not contain any other requests for the requests that you made because the requests did not have a 404.2 return code. When you consult 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 to be 404, or capture the failure if the request takes longer than 30 seconds by setting the <em>timeTaken</em> field in your failureDefinitions. </p> <h2>Restore Your Backup </h2> <p>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: </p><pre>%<em>windir</em>%\system32\inetsrv\appcmd restore backup cleanInstall</pre> <br><br><a href="https://web.archive.org/web/20130520180154/http://forums.iis.net/1052.aspx" class="btn">Discuss in IIS Forums</a><aside id="author-info" class="about-author"><h1>By IIS Team</h1><p><img src="https://web.archive.org/web/20130520180154im_/http://i1.iis.net/avatar/IISTeam.jpg?cdn_id=2013-05-01-001" alt="IIS Team"/>The IIS team is a close-knit group of passionate individuals who are enthusiastic about web technology. Our diverse team represents all corners of the globe with members from Canada, China, Germany, India, Ireland, Korea, Mexico, Russia, Vietnam, and all over the United States.</p></aside></article> </section> <section class="col-right"> <div id="FeaturedAd" data-adzoneid="12693" data-adtypeid="5" class="ad-300x250 " data-adwidth="300px" data-adheight="250px" style="width:300px;height:250px;"></div> <nav class="nav-base nav-iconed"><h1>Table of Contents</h1><h2>Installation Issues</h2><ul><li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/installation-issues/troubleshooting-iis-7x-installation-issues"><span><span class="icon icon-article">Article</span></span>Troubleshooting IIS 7.x Installation Issues</a></li></ul><h2>Security Issues</h2><ul><li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/security-issues/troubleshooting-ssl-related-issues-server-certificate"><span><span class="icon icon-article">Article</span></span>Troubleshooting SSL related issues (Server Certificate)</a></li><li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/security-issues/troubleshooting-forms-authentication"><span><span class="icon icon-article">Article</span></span>Troubleshooting Forms Authentication</a></li></ul><h2>ASP.NET Issues</h2><ul><li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/aspnet-issues/troubleshooting-invalid-viewstate-issues"><span><span class="icon icon-article">Article</span></span>Troubleshooting Invalid viewstate issues</a></li></ul><h2>Diagnosing HTTP Errors</h2><ul><li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/diagnosing-http-errors/how-to-use-http-detailed-errors-in-iis"><span><span class="icon icon-article">Article</span></span>How to Use HTTP Detailed Errors in IIS 7.0</a></li><li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/diagnosing-http-errors/troubleshooting-http-5022-bad-gateway-error-in-cgi-applications"><span><span class="icon icon-article">Article</span></span>Troubleshooting HTTP 502.2 Bad Gateway error in CGI applications</a></li><li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/diagnosing-http-errors/troubleshooting-unexpected-issues"><span><span class="icon icon-video">Video</span></span>Troubleshooting Unexpected Issues</a></li><li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/diagnosing-http-errors/troubleshooting-http-400-errors-in-iis"><span><span class="icon icon-article">Article</span></span>Troubleshooting HTTP 400 Errors in IIS</a></li></ul><h2>Using Failed Request Tracing</h2><ul><li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/using-failed-request-tracing/how-to-enable-failed-request-tracing-for-unc-hosting"><span><span class="icon icon-article">Article</span></span>How to Enable Failed Request Tracing for UNC Hosting</a></li><li class="current"><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis"><span><span class="icon icon-article">Article</span></span>Troubleshooting Failed Requests Using Tracing in IIS 7</a></li><li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/using-failed-request-tracing/using-failed-request-tracing-rules-to-troubleshoot-application-request-routing-arr"><span><span class="icon icon-article">Article</span></span>Using Failed Request Tracing Rules to Troubleshoot Application Request Routing (ARR)</a></li><li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/using-failed-request-tracing/troubleshoot-with-failed-request-tracing"><span><span class="icon icon-article">Article</span></span>Troubleshoot with Failed Request Tracing</a></li></ul><h2>Performance Issues</h2><ul><li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/performance-issues/troubleshooting-smb-netbios-fcn-limit-issues-with-remote-content"><span><span class="icon icon-article">Article</span></span>Troubleshooting SMB NetBIOS/FCN limit issues with Remote Content</a></li><li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/performance-issues/troubleshooting-high-cpu-in-an-iis-7x-application-pool"><span><span class="icon icon-article">Article</span></span>Troubleshooting High CPU in an IIS 7.x Application Pool</a></li><li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/performance-issues/troubleshooting-native-memory-leak-in-an-iis-7x-application-pool"><span><span class="icon icon-article">Article</span></span>Troubleshooting native memory leak in an IIS 7.x Application Pool</a></li><li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/performance-issues/troubleshooting-iis-compression-issues-in-iis6-iis7x"><span><span class="icon icon-article">Article</span></span>Troubleshooting IIS Compression issues in IIS6/IIS7.x</a></li><li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/performance-issues/troubleshooting-iis-performance-issues-or-application-errors-using-logparser"><span><span class="icon icon-article">Article</span></span>Troubleshooting IIS Performance Issues or Application Errors using LogParser</a></li></ul><h2>Remote Administration Issues</h2><ul><li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/remote-administration-issues/diagnosing-failures-with-remote-administration"><span><span class="icon icon-article">Article</span></span>Diagnosing Failures with Remote Administration</a></li></ul><h2>Web Platform Installer Issues</h2><ul><li><a href="/web/20130520180154/http://www.iis.net/learn/troubleshoot/web-platform-installer-issues/troubleshooting-problems-with-microsoft-web-platform-installer"><span><span class="icon icon-article">Article</span></span>Troubleshooting Problems with Microsoft Web Platform Installer</a></li></ul></nav> <p id="MicroTextAd" data-adzoneid="0" data-adtypeid="348" class="ad-text " data-adwidth="100%" data-adheight="40px" style="height:40px;"></p> <div id="MicrosoftTranslatorWidget"><noscript><a href="https://web.archive.org/web/20130520180154/http://www.microsofttranslator.com/bv.aspx?a=http%3a%2f%2fwww.iis.net%2f">Translate this page</a><br/>Powered by <a href="https://web.archive.org/web/20130520180154/http://www.microsofttranslator.com/">Microsoft® Translator</a></noscript></div> <script type="text/javascript"> /* <![CDATA[ */ setTimeout(function() { var s = document.createElement("script"); s.type = "text/javascript"; s.charset = "UTF-8"; s.src = ((location && location.href && location.href.indexOf('https') == 0) ? "https://web.archive.org/web/20130520180154/https://ssl.microsofttranslator.com" : "https://web.archive.org/web/20130520180154/http://www.microsofttranslator.com" ) + "/ajax/v2/widget.aspx?mode=manual&from=en&layout=ts"; var p = document.getElementsByTagName('head')[0] || document.documentElement; p.insertBefore(s, p.firstChild); }, 0); /* ]]> */ </script> </section> </div> <div id="BottomAd" data-adzoneid="0" data-adtypeid="4" class="ad centered-ad-728" data-adwidth="728px" data-adheight="90px" style="width:728px;height:90px;"></div> <footer id="footer-site"> <ul> <li class="text-links">This site is managed for Microsoft by Neudesic, LLC. | © 2013 Microsoft. All rights reserved.</li> <li><a href="https://web.archive.org/web/20130520180154/http://www.iis.net/privacy">Privacy Statement</a></li> <li><a href="https://web.archive.org/web/20130520180154/http://www.iis.net/terms-of-use">Terms of Use</a></li> <li><a href="https://web.archive.org/web/20130520180154/http://www.iis.net/contact">Contact Us</a></li> <li><a href="https://web.archive.org/web/20130520180154/http://www.neudesicmediagroup.com/Advertising.aspx?site=iis">Advertise With Us</a></li> </ul> <ul> <li>Follow us on:</li> <li><a href="https://web.archive.org/web/20130520180154/http://www.twitter.com/inetsrv/">Twitter</a></li> <li><a href="https://web.archive.org/web/20130520180154/http://facebook.com/inetsrv/">Facebook</a></li> </ul> <ul class="no-title"> <li><a href="https://web.archive.org/web/20130520180154/http://forums.iis.net/1080.aspx">Feedback on IIS</a></li> <li><a href="https://web.archive.org/web/20130520180154/http://www.iis.net/learn">Powered by IIS8</a></li> </ul> <a href="https://web.archive.org/web/20130520180154/http://microsoft.com/" class="logo-footer">Microsoft</a> </footer> </div> <input type="hidden" id="meta-contentType" value="ArticleContentPicker"/> <input type="hidden" id="meta-contentLiveDate" value="2007-12-12"/> <input type="hidden" id="meta-articleContentType" value="Tutorial"/> <input type="hidden" id="meta-articleContentTypeValue" value="32"/> <script src="https://web.archive.org/web/20130520180154js_/http://i1.iis.net/umbraco-beta-scripts/jquery-1.8.2.min.js?cdn_id=2013-05-01-001" type="text/javascript"></script> <script type="text/javascript">$.ajaxSetup({ cache: false });var omni_guid="77434952-1fc4-4047-a97b-fd6a76f91e86";var searchDomain='https://web.archive.org/web/20130520180154/http://www.iis.net';</script> <script type="text/javascript">var s=document.createElement('script');s.type='text/javascript';s.src='https://web.archive.org/web/20130520180154/http://i1.iis.net/umbraco-beta-scripts/prod-article.min.js?cdn_id=2013-05-01-001';document.body.appendChild(s);</script> <noscript><a href="https://web.archive.org/web/20130520180154/http://www.omniture.com/" title="Web Analytics"><img src="https://web.archive.org/web/20130520180154im_/http://msstonojstemp.112.2o7.net/b/ss/msstonojstemp/1/H.20.2--NS/0" height="1" width="1" alt=""/></a></noscript> </body> </html>