I have installed the Tracing feature and enabled failed request tracing for a website, to debug a Classic ASP website. The XML logs are created upon occurring errors, however when I open them in IE, instead of getting the nice blue interface I get a massive amount of code/text.

Why doesn't the interface load and how can I fix it?


I had the same problem on a fresh install of Windows 2012. However, the freb.xsl file was present in the same folder as the event XML file.

To get it to show the 'nice interface' I had to add "about:internet" to the IE11 trusted sites list, as discussed here: http://forums.iis.net/p/1147605/1862016.aspx

  • 2
    adding about:internet to trusted sites worked – Bozojoe Oct 20 '14 at 21:52
  • 2
    adding about:internet to trusted sites did not work for me. I have ie version 11.0.9600.17728 – BraveNewMath Jun 17 '15 at 22:11
  • This worked for me in IE but not in Edge – demoncodemonkey Sep 6 '18 at 10:52

I found out I was missing the freb.xsl file, so I downloaded one from here (link at the bottom of the page): http://blogs.iis.net/bills/archive/2006/10/19/Making-Failed-Request-Tracing-More-Approachable.aspx

Hope someone will find this helpful. :)


If the freb.xsl file is missing from the directory that contains the log files, then the nice interface won't show. Rather than trying to find a website with the latest freb.xsl, I found on this page:


that if you just delete the directory that the xml files are being written to (likely something like C:\inetpub\logs\FailedReqLogFiles\W3SVC1), then IIS will automatically recreate the directory and write the freb.xsl file when it next creates the next log file.


I got the failed request trace to display in IE (and it doesn't work on chrome) by pointing an IIS website at the folder and open it in IE - version 11 - from there.

Other things I tried before this was

  1. add about:internet to trusted sites
  2. to run in compatibility mode.

I am certain this has to do with security settings and there is probably an easier way of getting this to work without IIS. I go with the path of least resistance on this one.


Old post but this solution worked for me (thanks Pilau) I downloaded this file and copied to C:\inetpub\logs\FailedReqLogFiles\W3SVC2

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.