Sunday, May 20, 2012

SharePoint 2010, SSRS 2012 and Internet Explorer 9 Issues

In SharePoint 2010, when using the RSViewerPage.aspx to view SSRS reports in Internet Explorer 9, you may experience the following problems:
  • Increasing the Zoom percentage to more than 100% on the page’s toolbar results in the top of the report not being visible. Decreasing the Zoom percentage below 100% results in extra whitespace at the top of the report.
  • The Actions->Export flyout menu does not appear.
I have additionally experienced a problem with a PerformancePoint Reporting Services web part that is displayed in a modal dialog called using SharePoint’s SP.UI.ModalDialog.showModalDialog method. When I click a button on the page that calls the method and displays the dialog, the report will update itself based on connections to filters on the page. Works great in IE7, IE8, Chrome and FireFox, however in IE9, the update to the report is only triggered in compatibility mode.

Adding your site to IE9’s Compatibility View settings list (Tools->Compatibility View settings) should fix the functionality. After discovering this workaround on my own, I stumbled across the following Microsoft Knowledge Base article which addresses the Export menu issue:
FIX: SSRS 2008 R2 report or SSRS 2012 report has no Export menu in Internet Explorer 9.0 if you use the out-of-box viewer page in the SharePoint Report Viewer Web Part (http://support.microsoft.com/kb/2616481).
I’m hoping the Zoom problem and my modal dialog report update problem would be addressed by the fix mentioned in the KB article as well. I’ll update this post eventually when we apply the CU.

UPDATE 7/16/12: I installed SQL Server 2012 CU2 (11.0.2325), which is supposed to include the fixes from CU1 (mentioned in the kb article above), and it has not, unfortunately, fixed any of the issues mentioned in this post.

UPDATE 11/14/12: I installed SQL Server 2012 SP1 (11.0.3000) with the same results: none of the issues mentioned in this post have been addressed.

6 comments:

  1. As a workaound, I have created a copy of the ReportViewer.dwp web part in SharePoint and added this line of code right above the Title tag: < meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" /> I named the new web part with a custom name, uploaded it to the SharePoint site, and added it to a page in SharePoint. It seems to render the reports with a working export menu and addresses the zoom issue. I am thinking of modifying the OOTB ReportViewer.dwp web part. But I am not a SharePoint developer and am a little nervous about whether this is the best practice. Any input? (We are SQL Server 2008R2 SP2)

    ReplyDelete
  2. Depending on your development environment, I would stick with your solution as it stands now and not modify the OOTB web part. But it depends on if there is a need to have others not have to think about which web part to use when placing a report on a page. My only "best practice" concern would be that it would get clobbered with a future update. Completely going back on that advice, however, you may want to make a similar edit to the RSViewerPage.aspx and DynamicReportView.aspx pages which may end up displaying your reports as well (e.g. web part menu->Open in New Window).

    Hope that helps,

    Ken

    ReplyDelete
  3. I decided not to modify the ReportViewer.dwp web part after a consultant told me that there was an update to the web part as a part of the SQL Server SP. However, it is a separate install. So, in addition to the SQL Server 2008R2 SP2 service pack on the database server, an msi had to be applied to the SharePoint farm. I am not a SharePoint admin, but I asked my farm administrator to install this for 2008R2 and it fixed the issues:

    http://www.microsoft.com/en-us/download/details.aspx?id=622

    ReplyDelete
    Replies
    1. Hi Laura,

      Thanks for sharing the information!

      The environment that I am currently working in is hosted on a single server that is acting as both the WFE and database server, so that the add-in was installed with the SQL Server 2012 SP1 installation (which I was able to verify). I continue to experience the issue using Internet Explorer 10 as well.

      I am happy to hear that the add-in worked in your environment... one less headache for your users to deal with!

      Ken

      Delete
  4. Had tried so many solutions but none worked for me. So decided to write my own solution and rendered the Export SubMenu for IE9 manually.

    Just add the script on your aspx page (which contains the SSRSReportViewer Webpart) directly or add a content editor webpart (chrome type none) and add the script.

    http://s000.tinyupload.com/index.php?file_id=59894628717375479951

    ReplyDelete
    Replies
    1. Updated code to consider IE10 and Export sub-menu position.

      http://s000.tinyupload.com/index.php?file_id=52844566386378052825

      Delete