I have an SSRS 2008 report with hyperlinks to urls that open in a new page. The hyperlinks are formatted using javascript:void(window.open('http://myURL','_blank')). The links work when the report is displayed in Report Manager as well as when the report is opened by itself in the browser. However, I need to display the report in the body of a web page that uses frames. I am running IE 8. When the report is opened inside the frameset the links no longer work. I don't get an error message. I can see the link is formatted correctly in the status line at the bottom of the browser window; but when I click on a link, nothing happens. What gives?Diane Joel

I just tried copying and pasting the javascript link from the report inside my frameset into a new browser window to see if it would successfully open the link. It did, however, first it prompted me with this Security warning shown below. I suspect this could be associated with the problem. How do I get around it? Diane Joel

Hi Diane ! Please make sure your link is added in your Trusted Sites. Please let me know if this helps. Hopefully i have answered you correctly. Thanks, Hasham

Hi There If you are trying to open it inside frame I think you might need to use top.window.open or parent.window.open. Please try and see if that help you Many thanks Syed Qazafi Anjum

Hi There If you are trying to open it inside frame I think you might need to use top.window.open or parent.window.open. Please try and see if that help you Many thanks Syed Qazafi Anjum

Hi Syed, The problem is not getting the report to open in the proper frame. That is working just fine. The problem is that the links in the report no longer work once opened in a frame. And as I stated previously, if I copy/paste the link to the report (i.e., javascript:void(window.open('http://MyURL','_blank')) ), I get the Security Warning; however, if I just enter the link (i.e., http://MyURL), it does not display the security warning.Diane Joel

Hello Diane, Based on my knowledge, if we use Javascript to open the report, it will open a new window and go to the blank page, which is res://ieframe.dll on your machine. Then, it will open the report URL. In this scenario, IE will find that the browser is trying to open a trusted site, and popup the dialog. If we open the link directly, maybe the current link and the target link are both in the trusted zone, so that it will not popup the warning window. If you do not want to see the error, please try to add res://ieframe.dll into the trusted zone in IE browser to see whether it can solve this issue. Since I cannot reproduce this issue on my side, I am not sure it works. If you have further question, please tell us freely. Regards, EdwardEdward Zhu TechNet Community Support

Hello Diane, Based on my knowledge, if we use Javascript to open the report, it will open a new window and go to the blank page, which is res://ieframe.dll on your machine. Then, it will open the report URL. In this scenario, IE will find that the browser is trying to open a trusted site, and popup the dialog. If we open the link directly, maybe the current link and the target link are both in the trusted zone, so that it will not popup the warning window. If you do not want to see the error, please try to add res://ieframe.dll into the trusted zone in IE browser to see whether it can solve this issue. Since I cannot reproduce this issue on my side, I am not sure it works. If you have further question, please tell us freely. Regards, EdwardEdward Zhu TechNet Community Support

Edward, Thank you for your response. As you suggested, I added res://ieframe.dll to my trusted sites and tried the link from the report again. Unfortunately clicking on the link in the report still does not open the page. Interestingly, when I copy and paste the link into a new browser window, it does now open the link without prompting. Although you will not be able to test my actual link because it is behind our firewall, I thought I'd list it here so you can see exactly what I'm working with. This is the link that, when pasted into my browser address line, prompted with the Security warning before I added res://ieframe.dll to my Trusted sites list: javascript:void(window.open('http://PDS.bc.com/default.asp?header=_Header.asp&body_page=toc.asp&fltrID=8095','_blank')) Still nothing happens when I click the link from within the report when it is inside a frame; the link in the report works fine if it is not within a frame.Diane Joel

Edward, Thank you for your response. As you suggested, I added res://ieframe.dll to my trusted sites and tried the link from the report again. Unfortunately clicking on the link in the report still does not open the page. Interestingly, when I copy and paste the link into a new browser window, it does now open the link without prompting. Although you will not be able to test my actual link because it is behind our firewall, I thought I'd list it here so you can see exactly what I'm working with. This is the link that, when pasted into my browser address line, prompted with the Security warning before I added res://ieframe.dll to my Trusted sites list: javascript:void(window.open('http://PDS.bc.com/default.asp?header=_Header.asp&body_page=toc.asp&fltrID=8095','_blank')) Still nothing happens when I click the link from within the report when it is inside a frame; the link in the report works fine if it is not within a frame.Diane Joel

Hello Diane, Thanks for your response. My last reply is to solve your question that you encounter the popup dialog when you access the report from the browser. From your response, I think the problem is solved. Now, the only remaining problem is that the report did not redirect to the destination in the new browser session. I tried to build the web page, and find it works properly if I put the report in the frame. Even when the report is located in the iframe, it also works. I consider that the issue is not due to the web page. If possible, please try to check whether there is a JavaScript error when you click the link. In another word, do you see the warning icon on the left bottom of the IE browser? If yes, please click it and popup the dialog to show us the detail error message. If you have further questions, please tell us freely. Regards, EdwardEdward Zhu TechNet Community Support

Hello Diane, Thanks for your response. My last reply is to solve your question that you encounter the popup dialog when you access the report from the browser. From your response, I think the problem is solved. Now, the only remaining problem is that the report did not redirect to the destination in the new browser session. I tried to build the web page, and find it works properly if I put the report in the frame. Even when the report is located in the iframe, it also works. I consider that the issue is not due to the web page. If possible, please try to check whether there is a JavaScript error when you click the link. In another word, do you see the warning icon on the left bottom of the IE browser? If yes, please click it and popup the dialog to show us the detail error message. If you have further questions, please tell us freely. Regards, EdwardEdward Zhu TechNet Community Support

Hi Edward, To answer your latest question, no there is not a javascript error. I see "javascript:void(window.open('http://PDS.bc.com/default.asp?header=_Header.asp&body_page=toc.asp&fltrID=8095','_blank'))" in the status line at the bottom of the browser, but nothing happens when I click the link. No page opens, no error displays. Regards, DianeDiane Joel

Hi Edward, To answer your latest question, no there is not a javascript error. I see "javascript:void(window.open('http://PDS.bc.com/default.asp?header=_Header.asp&body_page=toc.asp&fltrID=8095','_blank'))" in the status line at the bottom of the browser, but nothing happens when I click the link. No page opens, no error displays. Regards, DianeDiane Joel

Because a picture often speaks louder than words, here is a picture of the report inside my frameset: Diane Joel

Because a picture often speaks louder than words, here is a picture of the report inside my frameset: Diane Joel

Hi Diane, Take a look at this article: http://msdn.microsoft.com/en-us/library/dd565656(v=vs.85) See if there is any difference in behavior with setting the following registry key to 0 or 1: HKEY_LOCAL_MACHINE (or HKEY_CURRENT_USER)\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_SCRIPTURL_MITIGATION\iexplore.exe = 0x00000000 And, take note of the security warnings in the documentation. Thanks, Cathy Miller

Hi Diane, Take a look at this article: http://msdn.microsoft.com/en-us/library/dd565656(v=vs.85) See if there is any difference in behavior with setting the following registry key to 0 or 1: HKEY_LOCAL_MACHINE (or HKEY_CURRENT_USER)\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_SCRIPTURL_MITIGATION\iexplore.exe = 0x00000000 And, take note of the security warnings in the documentation. Thanks, Cathy Miller

Hi Diane, Take a look at this article: http://msdn.microsoft.com/en-us/library/dd565656(v=vs.85) See if there is any difference in behavior with setting the following registry key to 0 or 1: HKEY_LOCAL_MACHINE (or HKEY_CURRENT_USER)\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_SCRIPTURL_MITIGATION\iexplore.exe = 0x00000000 And, take note of the security warnings in the documentation. Thanks, Cathy Miller

Hi Diane, It sounds like you require a more in-depth level of support. Please visit the below link to see the various paid support options that are available to better meet your needs. http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone If Microsoft determines that a problem is the result of a defect in a Microsoft product, you will not be charged for that incident. Thanks, Cathy

Cathy, Thank you for your suggestions. I've reviewed the documentation regarding the " Cross-Domain Barrier " and tried to implement some of the suggestions there; however, I'm not able to get any of them to work for my report. The suggested fixes are not specific to reporting services and I don't konw how to translate them to work in that enviroment. I did not attempt to change the registry key as I'm not comfortable messing with registry keys and I wouldn't be able to change the registry key for all the users in our company that would need to access this report anyway. I think I understand the cross-domain barrier. Our reports are on a different server than the web content, so I presume that is the issue. Both servers are inside our company firewall, however, so I'm not concerned about malicious attacks and wish I could circumvent this issue somehow.Diane Joel