Learn more about SQL Server tools


Tutorials          DBA          Dev          BI          Career          Categories          Videos          Whitepapers          Today's Tip          Join

Tutorials      DBA      Dev      BI      Categories      Events

DBA    Dev    BI    Categories


SQL Server Reporting Services (SSRS) is not compatible with Internet Explorer 11

By:   |   Read Comments (7)   |   Related Tips: > Reporting Services Configuration


You upgraded to Internet Explorer 11, now when you preview a SQL Server Reporting Services (SSRS) report you find the print command is not visible in the report viewer. Also, sometimes when you change parameter values IE11 stops responding or it takes a long time to load the report. You may also find that the toolbar that displays the report controls and export features, appears on multiple lines when viewed with IE11. When you preview the same SSRS report in Chrome or Mozilla Firefox, it works fine without any issue, which means it is a browser compatibility issue. How can you make SQL Server Reporting Services (SSRS) compatible with IE11?


This tip assumes that your SSRS report is developed and working fine with Chrome or the Mozilla Firefox browser, but when you preview the report in IE11 you are facing one or more of the issues stated in the problem statement.

There are two ways to resolve this problem.

1. Fix at client browser level.

2. Fix at report server level.

In this tip I will be explaining both methods, let's start with fixing the issue in the client browser.

Fix the SSRS Compatibility Issue in IE 11

This has to be applied to all users' browsers.

  • Open the IE11 browser
  • Press F12 which would open a developer tool at the bottom of the browser
  • Click "Emulation" tab
  • Change the "Document mode" to "Edge", you can refer to the below image.


  • Try to access the report. You should now be able to access the report in IE11 without any issues.

Fix the SSRS Compatibility Issue at the Server Level

This change will reflect in all users' browsers, you don't need to make any changes for the client browser settings.

  • It is recommended to take a backup of the reportviewer.aspx file located at \Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer\Pages.
  • Open the reportviewer.aspx file located in \Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer\Pages in notepad.
  • Change the meta tag from <meta http-equiv="X-UA-Compatible" content="IE=5"> to <meta http-equiv="X-UA-Compatible" content="IE=Edge">, you can refer to the below image:

  • Save the file and try to access the report in IE11, you should now be able to access the report without any issues.
Next Steps

Last Update:

About the author
MSSQLTips author Ghanesh Prasad Ghanesh Prasad leads a team in Microsoft Business Intelligence and has over 5 years of experience working with SQL Server.

View all my tips


Post a comment or let the author know this tip helped.

All comments are reviewed, so stay on subject or we may delete your comment. Note: your email address is not published. Required fields are marked with an asterisk (*).

*Name    *Email    Notify for updates 

Get free SQL tips:

*Enter Code refresh code     

Friday, January 06, 2017 - 3:59:16 PM - Doug Back To Top



What if your reportviewer file does not have a meta tag?  Ours has an "asp:literal" line instead. see below.....  Should I add a line like your example or do something else?

 <head id="headID" runat="server">

  <asp:literal runat="server" id="httpEquiv"></asp:literal>

  <title><%= GetPageTitle() %></title>



Tuesday, September 20, 2016 - 3:55:46 AM - Johnb Back To Top

Doesn't work.  Please post appropriate solutin.

Monday, January 25, 2016 - 12:01:30 PM - Surya Back To Top



We have implimented SSRS in SharePoint integrated Mode and users have to scroll right & down to click on Apply for filters. Could you please let me know the location to chage the settings for SharePoint. Thanks.


Monday, September 28, 2015 - 5:21:22 AM - Robber Back To Top

Change the meta tag from <meta http-equiv="X-UA-Compatible" content="IE=5"> to <meta http-equiv="X-UA-Compatible" content="IE=Edge">

Tuesday, September 22, 2015 - 6:23:59 PM - Tony Back To Top

I've not seen this issue with SharePoint integration mode. Have you?



Tuesday, September 22, 2015 - 9:02:47 AM - Greg Robidoux Back To Top

Hi Kris,

thanks for pointing out the issue.  The HTML code has been fixed to show the before and after values.


Tuesday, September 22, 2015 - 8:36:09 AM - Kris Back To Top

"Change the meta tag from to ,"

Change what to what?

Learn more about SQL Server tools