IIS 7 and Above
Failed Request Tracing - XSLT Error
Last post Apr 22, 2009 10:04 AM by rabid lemming
Jan 17, 2008 05:44 AM|Padraic24|LINK
I have setup a failed event trace to capture any 500 errors. I am having a problem on a page with a dll not being loaded (but thats another issue).
Anyway when I try an open the resulting XML file in Internet Explorer I get the following error:
Security settings do not allow the execution of script code within this stylesheet
Anyone have any ideas?
Jan 17, 2008 12:26 PM|rlucero|LINK
I'm guessing that Internet Explorer gives you a pop-up stating CONTENT BLOCKED right? I just tried out your same steps and ran into the same problem. Here are some steps that got it working for me:
1. Open your Failed Request XML
2. Click Add.. in the Internet Explorer Content Blocked dialog
3. The "Add this website to the zone:" should contain about:internet.
4. Click Add... for about:internet
5. Click Close
The Failed Request log should display correcty now. Let me know if you need additional help.
Jan 17, 2008 01:01 PM|Padraic24|LINK
I appreciate the response. But the problem does not lie with the website (i am actually using IE to display an xml file on my c: drive) being blocked by Internet Explorer. It appears to me that the XSLT stylesheet that is produced along with the XML has
some script in it. Something is blocking this script from running.
I have looked for solutions on the Internet regarding this and they told me to add this to the XSLT file.
If this is the case the XSLT file produced by IIS is corrupt. Could you tell me if your file has this line in it.
Jan 17, 2008 01:12 PM|Padraic24|LINK
Jan 18, 2008 10:41 AM|OWScott|LINK
I'm running into the same issue but would like to find out how to view it in Windows Explorer. The issue is only with UAC. If I log in as the real administrator, or disable UAC, then it's not an issue.
Do I need to add something to the local intranet zone? I tried different combinations of
file:///c:/inetpub/logs/FailedReqLogFiles/* but I couldn't get it to work. Also, the "Custom Level" button in IE security is grayed out. That also occurs only with UAC.
Jan 18, 2008 11:12 AM|rlucero|LINK
Are you running into a problem with opening the file when you try to access through the file system or are you getting the
Content Blocked dialog in Internet Explorer?
If you are just trying to view the XML log locally it is best to view it through IE. To get the style sheet to display correctly add
http://localhost or, as in the case above, about:internet to the list of trusted sites and domains.
Hope this helps.
Jan 18, 2008 11:41 AM|OWScott|LINK
Oh I see. That was it! Because of UAC, my Content Blocked dialog doesn't have the option to add about:internet so I didn't fully understand your instructions earlier. I had to manually go into the Intranet zone and add it. I think I see now why about:internet
is needed. Both the xml and xsl files reference url=(0014)about:internet.
Apr 29, 2008 03:44 AM|looc|LINK
How did you get to work?
I´m trying to view Failed request tracing xml file ona win 2008 with IE7 and is getting
Security settings do not allow the execution of script code within this stylesheet.
I´m trying to open the xml file by clicking on the xml-file in filesystem.
How to fix this?
Mar 30, 2009 04:15 PM|Madness80|LINK
Wow, talk about obscure fixes. I too had this problem trying to browse C:\inetpub\logs\FailedReqLogFiles\W3SVC693542776\fr000013.xml
Adding "about:internet" as suggested to the list of trusted sites in IE fixed it.
Words cannot describe my frustration. Why not a simple "Allow script code to execute in stylesheet" checkbox along with all of the other advanced security settings?
Apr 22, 2009 10:04 AM|rabid lemming|LINK
it took me ages to work out how to set this in vb 6 code rather than jscipt
'// Load the XSL Dom with the XSL Stylesheet
Set objXSL = New MSXML2.DOMDocument60
objXSL.resolveExternals = True
objXSL.async = False
objXSL.setProperty "AllowDocumentFunction", True
objXSL.setProperty "AllowXsltScript", True
i hopes this helpes prevent someone else spending as long as it took me to
work this out