12

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?

Kiquenet
  • 143
pilau
  • 291
  • 1
  • 3
  • 8

6 Answers6

20

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

Daz
  • 301
6

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. :)

pilau
  • 291
  • 1
  • 3
  • 8
6

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:

http://blogs.iis.net/davcox/archive/2007/10/05/recovering-freb-xsl-after-deleting-it.aspx

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.

Wesley Smith
  • 161
2

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.

sebix
  • 4,432
BraveNewMath
  • 121
0

For me the solution was to disable the Enhanced Protected Mode of Internet Explorer.

To do so go to...
IE menu → Tools → Internet Options → Advanced → Scroll down to section "Security" → Disable Checkbox "Enable Enhanced Protected Mode"

Make sure that you fully restart IE for this change to take effect.

Jpsy
  • 141
0

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

expirat001
  • 101