{"id":1159,"date":"2026-11-17T22:38:58","date_gmt":"2026-11-17T22:38:58","guid":{"rendered":"https:\/\/windows-vps.org\/blog\/?p=1159"},"modified":"2026-11-17T22:38:58","modified_gmt":"2026-11-17T22:38:58","slug":"iis-failed-request-tracing-module-provider-troubleshooting","status":"publish","type":"post","link":"https:\/\/windows-vps.org\/blog\/iis-failed-request-tracing-module-provider-troubleshooting\/","title":{"rendered":"Reading IIS Failed Request Tracing: Modules, Providers, and Timing Gaps"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Failed Request Tracing (FREB) is the only diagnostic in IIS that shows you what each module did in sequence and how long it took. When an ASP.NET Core request returns 500.30, a rewrite rule loops, or a request spends four seconds somewhere between authentication and the managed pipeline, FREB is what tells you which stage owns the time. The problem is that FREB fails silently in several common ways: the rule matches no requests, the log directory has no write permission, or the trace ends at a module that stopped emitting events.<\/p>\n\n\n<p class=\"wp-block-paragraph\">This article covers enabling FREB correctly on a Windows Server VPS, the provider names you will actually see in the XML, how to read the timing fields, and the specific failure patterns that produce empty or truncated traces. It assumes IIS 10 on Windows Server 2016 or later.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Enable It at the Site Level, Not Just Globally<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Installing the feature (<code>Install-WindowsFeature Web-Http-Tracing<\/code>) adds the Tracing module, but it does nothing until a rule is configured. Rules live in <code>system.webServer\/tracing<\/code> and can be defined at the server, site, or application level. The common mistake is creating the rule in the global configuration and forgetting that the site has its own <code>web.config<\/code> which overrides the section.<\/p>\n\n\n<p class=\"wp-block-paragraph\">A minimal rule set that captures every slow and every failing request:<\/p>\n\n\n<p class=\"wp-block-paragraph\"><code>%windir%\\system32\\inetsrv\\appcmd.exe set config \"Default Web Site\" -section:system.webServer\/tracing\/traceFailedRequests \/+\"[path='*']\" \/commit:apphost<\/code><\/p>\n\n\n<p class=\"wp-block-paragraph\">Then add the status codes you care about: <code>appcmd set config \"Default Web Site\" -section:system.webServer\/tracing\/traceFailedRequests.[path='*'].traceFailedRequests.[path='*'] \/+[statusCodes='[statusCodeRange='500-599']']<\/code> for server errors, and a second entry for <code>timeTaken='[timeTaken='00:00:03']<\/code> if you want to catch slow successes as well. A time threshold of three seconds is a reasonable starting point; lower it to one second while investigating a specific complaint.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Set the Log Path and Permissions Correctly<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">FREB writes XML files named <code>fr000001.xml<\/code> and so on, into a directory specified per-provider in the rule. The default is <code>%SystemDrive%\\inetpub\\logs\\FailedReqLogFiles<\/code>. Two things break here. First, the application pool identity needs write access to the directory \u2014 grant it with <code>icacls C:\\inetpub\\logs\\FailedReqLogFiles \/grant \"IIS AppPool\\MyAppPool:(OI)(CI)M\" \/T<\/code>. Second, if you specify a path on a different drive, you must use the full physical path in the rule, not a virtual path; relative paths are resolved against the site root and the files end up somewhere unexpected.<\/p>\n\n\n<p class=\"wp-block-paragraph\">Also set <code>maxLogFiles<\/code> and <code>maxLogFileSizeKB<\/code> in the tracing section. The defaults are 50 files and 1024 KB respectively, which a request-heavy site will consume in minutes during an incident. On a small VPS volume, 20 files at 512 KB is a better balance: enough to capture a reproduction, small enough that nobody fills the system disk.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Reading the Trace: Modules, Events, and Timings<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Each FREB XML file contains a <code>requestFailedRequests<\/code> root with a <code>failedRequest<\/code> element and two child sections: <code>requestFailedRequests<\/code> metadata (URL, verb, status, trigger reason) and <code>EventList<\/code>. Inside EventList, every entry has <code>EventName<\/code>, <code>ProviderName<\/code>, <code>ClassName<\/code>, <code>Time<\/code>, and <code>Duration<\/code> in milliseconds. The <code>Time<\/code> field is relative to the start of the request, so the module with the largest <code>Duration<\/code> is usually the culprit.<\/p>\n\n\n<p class=\"wp-block-paragraph\">The provider names that matter most:<\/p>\n\n\n<ul class=\"wp-block-list\">\n<li><code>WWW Server<\/code> \u2014 request parsing, authentication phase boundaries, and the final response.<\/li>\n<li><code>ASP.NET<\/code> and <code>ISAPI Filter<\/code> \u2014 managed pipeline entry, where a long gap before the first ASP.NET event means the delay is upstream.<\/li>\n<li><code>MODULE_SET_RESPONSE_ERROR_STATUS<\/code> \u2014 the single most useful event: it names the module, the notification, and the HRESULT that produced the status code.<\/li>\n<li><code>URL Rewrite Module 2<\/code> \u2014 each rule evaluation with match\/no-match, which is how you prove a rewrite loop.<\/li>\n<li><code>AspNetCoreModule<\/code> \u2014 the handoff point to Kestrel, with the duration of the proxied request.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Look for <code>MODULE_SET_RESPONSE_ERROR_STATUS<\/code> first. If it fires at the <code>AUTHENTICATE_REQUEST<\/code> notification with HRESULT 0x80070005, the problem is authorisation, not application code. If it fires at <code>EXECUTE_REQUEST_HANDLER<\/code> with 0x8007007e, the handler DLL is missing \u2014 usually a wrong bitness for the application pool.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Common Failure: The Trace Is Empty<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A rule that is configured but produces no files almost always fails on one of four points. The site is not running under the configuration you edited, because the rule was set at server level and the site&#8217;s <code>web.config<\/code> has <code>&lt;clear \/&gt;<\/code> in the tracing section. The status code range does not cover the response, which is common when the application returns 200 with an error page. The path filter uses <code>*<\/code> but with a trailing slash. Or the URL Rewrite module changed the path before tracing evaluated it, so the path in the rule no longer matches.<\/p>\n\n\n<p class=\"wp-block-paragraph\">Verify the effective configuration rather than the stored configuration: <code>appcmd list config \"Default Web Site\" -section:system.webServer\/tracing<\/code> shows what IIS will actually apply, including inherited sections. If the traceFailedRequests collection is empty there, the rule is not in scope no matter what the GUI showed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Common Failure: The Trace Stops Mid-Pipeline<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A trace that ends abruptly after <code>AspNetCoreModule<\/code> with no corresponding completion event usually means the application crashed the worker process. FREB writes from within the pipeline, so a process exit produces a truncated file. Correlate the timestamp with the Windows Application log \u2014 an <code>Application Error<\/code> event with the same second gives you the exception and faulting module.<\/p>\n\n\n<p class=\"wp-block-paragraph\">A trace that ends after <code>ISAPI Filter<\/code> but before any managed event points at a native filter or a request-filtering rule rejecting the request. Check <code>system.webServer\/security\/requestFiltering<\/code> for <code>denyQueryStringSequences<\/code> and <code>hiddenSegments<\/code>; a rejected request produces a 404.19 that appears in the trace as a MODULE_SET_RESPONSE_ERROR_STATUS from <code>RequestFilteringModule<\/code>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Overhead: What FREB Costs in Production<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">FREB is not free. Enabling a rule that matches every path adds measurable latency \u2014 on the order of a few hundred microseconds per request per provider, but the number rises with the size of the EventList and the speed of the log volume. On a 4 vCPU VPS serving static content, a broad rule can push throughput down by 5\u201310 percent.<\/p>\n\n\n<p class=\"wp-block-paragraph\">The practical approach is to make rules as narrow as possible: filter on the specific path or a query-string parameter that identifies the problem request, keep the status-code trigger tight, and disable the rule once the reproduction is captured. Leaving a global trace rule enabled &#8220;just in case&#8221; is how a VPS ends up with a full system disk and unexplained latency, the same class of problem described in our article on <a href=\"https:\/\/windows-vps.org\/blog\/iis-logging-analysis-slow-requests-errors\/\">IIS logging analysis for slow requests<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Correlating With the ASP.NET Core Logs<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When <code>AspNetCoreModule<\/code> shows a long duration, the request has left IIS and is inside the managed host. FREB cannot see further. Enable <code>stdout<\/code> logging in <code>web.config<\/code> to capture the application&#8217;s own output, and correlate by timestamp and by the <code>X-Forwarded-For<\/code> \/ request path. In .NET 8, <code>W3CLogger<\/code> writes the same fields FREB does but from the application side, which makes the two logs alignable on request start time.<\/p>\n\n\n<p class=\"wp-block-paragraph\">If the gap is before the hosted application receives the request, it is usually a Kestrel readiness problem \u2014 the app started slowly after a recycle and IIS timed out. Preloading with the Application Initialization module eliminates that specific class of trace, as covered in our <a href=\"https:\/\/windows-vps.org\/\">Windows VPS hosting notes<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A Repeatable Diagnostic Sequence<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Enable FREB with a narrow rule matching the exact failing path and the observed status code.<\/li>\n<li>Reproduce once, then immediately disable the rule to stop log growth.<\/li>\n<li>Open the newest XML in the log directory and read <code>MODULE_SET_RESPONSE_ERROR_STATUS<\/code> first.<\/li>\n<li>Sort events by <code>Duration<\/code> descending to find the dominant phase.<\/li>\n<li>Map the last event&#8217;s provider back to the pipeline stage, then look at the component that owns that stage.<\/li>\n<li>Delete the log files after analysis \u2014 they contain query strings and headers, sometimes including tokens.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">One configuration note specific to hosted VPS environments: if the trace directory is on the system volume and disk usage is already high, the trace files themselves can cause an outage. Our <a href=\"https:\/\/windows-vps.org\/blog\/kvm-windows-vps-disk-resize-extend-volume-windows-server\/\">KVM disk resize guide<\/a> covers how to move that directory to a data volume without restarting IIS.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">FREB is the highest-signal, lowest-cost diagnostic available on IIS, provided the rule is scoped. If you are debugging a specific failure and want a second pair of eyes on the trace, <a href=\"https:\/\/windows-vps.org\/contact.html\">get in touch<\/a> with the XML attached and the reproduction steps.<\/p>\n\n","protected":false},"excerpt":{"rendered":"<p>Turn IIS Failed Request Tracing into a real diagnostic: narrow trace rules, log permissions, MODULE_SET_RESPONSE_ERROR_STATUS interpretation, and the four reasons traces come back empty or truncated.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":3,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1159","post","type-post","status-publish","format-standard","hentry","category-reviews"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.1 (Yoast SEO v26.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Reading IIS Failed Request Tracing: Modules, Providers, and Timing Gaps - Windows VPS Blog<\/title>\n<meta name=\"description\" content=\"Turn IIS Failed Request Tracing into a real diagnostic: narrow trace rules, log permissions, MODULE_SET_RESPONSE_ERROR_STATUS interpretation, and the four reasons traces come back empty or truncated.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/windows-vps.org\/blog\/iis-failed-request-tracing-module-provider-troubleshooting\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Reading IIS Failed Request Tracing: Modules, Providers, and Timing Gaps\" \/>\n<meta property=\"og:description\" content=\"Reading IIS Failed Request Tracing: Modules, Providers, and Timing Gaps\" \/>\n<meta property=\"og:url\" content=\"https:\/\/windows-vps.org\/blog\/iis-failed-request-tracing-module-provider-troubleshooting\/\" \/>\n<meta property=\"og:site_name\" content=\"Windows VPS Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-17T22:38:58+00:00\" \/>\n<meta name=\"author\" content=\"windows-vps\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@myxiechengxuan\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"windows-vps\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/windows-vps.org\/blog\/iis-failed-request-tracing-module-provider-troubleshooting\/\",\"url\":\"https:\/\/windows-vps.org\/blog\/iis-failed-request-tracing-module-provider-troubleshooting\/\",\"name\":\"Reading IIS Failed Request Tracing: Modules, Providers, and Timing Gaps - Windows VPS Blog\",\"isPartOf\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/#website\"},\"datePublished\":\"2026-11-17T22:38:58+00:00\",\"author\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58\"},\"description\":\"Turn IIS Failed Request Tracing into a real diagnostic: narrow trace rules, log permissions, MODULE_SET_RESPONSE_ERROR_STATUS interpretation, and the four reasons traces come back empty or truncated.\",\"breadcrumb\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/iis-failed-request-tracing-module-provider-troubleshooting\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/windows-vps.org\/blog\/iis-failed-request-tracing-module-provider-troubleshooting\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/windows-vps.org\/blog\/iis-failed-request-tracing-module-provider-troubleshooting\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/windows-vps.org\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Reading IIS Failed Request Tracing: Modules, Providers, and Timing Gaps\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#website\",\"url\":\"https:\/\/windows-vps.org\/blog\/\",\"name\":\"Windows VPS Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/windows-vps.org\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58\",\"name\":\"windows-vps\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g\",\"caption\":\"windows-vps\"},\"sameAs\":[\"https:\/\/windows-vps.org\/blog\",\"https:\/\/x.com\/myxiechengxuan\"],\"url\":\"https:\/\/windows-vps.org\/blog\/author\/myxiechengxuan\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Reading IIS Failed Request Tracing: Modules, Providers, and Timing Gaps - Windows VPS Blog","description":"Turn IIS Failed Request Tracing into a real diagnostic: narrow trace rules, log permissions, MODULE_SET_RESPONSE_ERROR_STATUS interpretation, and the four reasons traces come back empty or truncated.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/windows-vps.org\/blog\/iis-failed-request-tracing-module-provider-troubleshooting\/","og_locale":"en_US","og_type":"article","og_title":"Reading IIS Failed Request Tracing: Modules, Providers, and Timing Gaps","og_description":"Reading IIS Failed Request Tracing: Modules, Providers, and Timing Gaps","og_url":"https:\/\/windows-vps.org\/blog\/iis-failed-request-tracing-module-provider-troubleshooting\/","og_site_name":"Windows VPS Blog","article_published_time":"2026-11-17T22:38:58+00:00","author":"windows-vps","twitter_card":"summary_large_image","twitter_creator":"@myxiechengxuan","twitter_misc":{"Written by":"windows-vps","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/windows-vps.org\/blog\/iis-failed-request-tracing-module-provider-troubleshooting\/","url":"https:\/\/windows-vps.org\/blog\/iis-failed-request-tracing-module-provider-troubleshooting\/","name":"Reading IIS Failed Request Tracing: Modules, Providers, and Timing Gaps - Windows VPS Blog","isPartOf":{"@id":"https:\/\/windows-vps.org\/blog\/#website"},"datePublished":"2026-11-17T22:38:58+00:00","author":{"@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58"},"description":"Turn IIS Failed Request Tracing into a real diagnostic: narrow trace rules, log permissions, MODULE_SET_RESPONSE_ERROR_STATUS interpretation, and the four reasons traces come back empty or truncated.","breadcrumb":{"@id":"https:\/\/windows-vps.org\/blog\/iis-failed-request-tracing-module-provider-troubleshooting\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/windows-vps.org\/blog\/iis-failed-request-tracing-module-provider-troubleshooting\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/windows-vps.org\/blog\/iis-failed-request-tracing-module-provider-troubleshooting\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/windows-vps.org\/blog\/"},{"@type":"ListItem","position":2,"name":"Reading IIS Failed Request Tracing: Modules, Providers, and Timing Gaps"}]},{"@type":"WebSite","@id":"https:\/\/windows-vps.org\/blog\/#website","url":"https:\/\/windows-vps.org\/blog\/","name":"Windows VPS Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/windows-vps.org\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58","name":"windows-vps","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g","caption":"windows-vps"},"sameAs":["https:\/\/windows-vps.org\/blog","https:\/\/x.com\/myxiechengxuan"],"url":"https:\/\/windows-vps.org\/blog\/author\/myxiechengxuan\/"}]}},"_links":{"self":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/1159","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/comments?post=1159"}],"version-history":[{"count":1,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/1159\/revisions"}],"predecessor-version":[{"id":1160,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/1159\/revisions\/1160"}],"wp:attachment":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/media?parent=1159"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/categories?post=1159"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/tags?post=1159"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}