SQL Server Reporting Services is not compatible with Internet Explorer 11

By: Ghanesh Prasad | Updated: 2015-09-22 | Comments (20) | Related: > Reporting Services Configuration

Problem

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?

Solution

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

Be sure to test your browser based SSRS applications with each new release of Internet Explorer to ensure the applications work as expected.
Check out other tips on SQL Server Reporting Services Parameters.
Check out all of the SQL Server Reporting Services tips
Check out all of my tips here.

SQL Server Reporting Services Configuration Tool

How To Enable Caching in SQL Server Reporting Services

SQL Server Reporting Services Report Manager Tips and Tricks

Making Adjustments to SQL Server Reporting Services Configuration Files

SQL Server Video Reporting Services (SSRS) RS.EXE Utility

Modify SQL Server Reporting Services Rendering Format In SharePoint-Integrated Mode

Customize SQL Server Reporting Services Reports Manager Portal

SQL Server 2016 Reporting Services Custom Branding Example

Comments For This Article

Tuesday, March 1, 2022 - 5:08:56 PM - Chaviero

Even if I am using new Edge or Chrome (latest update) there is still problem as stated below:
"Browser not supported
Report Viewer requires a standards compliant browser. Users of Internet Explorer 8 and earlier should switch to a modern browser, or if already using a modern browser target standards mode by adding the <meta http-equiv="X-UA-Compatible" content="IE=edge" > header tag to the host page."

Tuesday, May 18, 2021 - 12:53:19 PM - Jorge Raigoza	Back To Top (88700)
This works for me, browser compatibility work meanwhile F12 (dev mode) is active, thanks a lot

Tuesday, July 9, 2019 - 4:30:03 PM - carl

Late to the party, but adding this entry to where Ghanesh mentioned AND to the Report.aspx fixed our issue.

Glad I found this in 2019!!

Monday, March 18, 2019 - 11:00:30 AM - James Lester

RAJIV SINGH's solution on Wednesday, July 26, 2017 - 6:33:24 AM worked for me, other solutions did not.

see below in the comments

Friday, December 14, 2018 - 5:43:04 AM - Sindhu

The below link helped,

I change the RSReportserver.config

<AuthenticationTypes>  
	<RSWindowsNTLM />  
</AuthenticationTypes>

From

<Authentication>  
	<AuthenticationTypes>  
		<RSWindowsNegotiate />  
	</AuthenticationTypes>  
	<EnableAuthPersistence>
		true
	</EnableAuthPersistence>  
</Authentication>

It worked

https://docs.microsoft.com/en-us/sql/reporting-services/security/configure-windows-authentication-on-the-report-server?view=sql-server-2017

Tuesday, November 21, 2017 - 1:09:23 PM - rafausoc

Este cambio lo realice y no me permite ver las imagenes que traigo desde base de datos; saben de pronto porque puede ser?

Wednesday, July 26, 2017 - 6:33:24 AM - RAJIV SINGH

For me I have to update Report.aspx page

MSRS10_50.MSSQLSERVER\Reporting Services\ReportManager\Pages

Report.aspx

Wednesday, May 3, 2017 - 1:04:18 PM - David DeLong

The same idea can be applied to report.aspx by adding the code below. You cannot edit the original X-UA-Compatible tag because it is compiled into the DLL, but you can add a 2nd tag to the aspx file.

Wednesday, April 12, 2017 - 8:56:51 AM - Ajay

This incompatibility behaviour started March third week as part of Microsft security updates.

If I navigate to the actual rdl file it works fine. But on the aspx page with the web parts the parameters all disappear in the parameter pane after selecting any parameter as mentioned by Rick Fitch. Has anyone found a solution. We are still in SharePoint 2010, will installing the latest CU and service pack fix this issue or is it a SSRS issue. We are in SSRS 2008 R2.

Has anyone found any solution, please share.

Wednesday, April 12, 2017 - 5:03:09 AM - Supriya

Thanks for your post and it helped me out to resolve my issue but on the other hand my issue is not fixed completely and now the problem is that the configuration we have to do at the client end (1. Fix at client browser level.), if I do have 2000 clients in this case how I can do it one by one in all so kindly write if you have any group policy or something like that.

Thanks in advance

Supriya

Thursday, April 6, 2017 - 4:41:22 PM - Kip

Hi,

We are trying

Fix the SSRS Compatibility Issue at the Server Level.

I changed the reportviewer file but it does not recompile the reportviews.aspx file.

We tried restarting the report services and running a report.

How can I get this file to recompile on the server?

Thank you!

Thursday, April 6, 2017 - 4:28:32 PM - Kip

We made the change but the file did not recompile even after restarting report services?

Tuesday, March 28, 2017 - 11:58:30 AM - Rick Fitch

we run ssrs in sharepoint using web part pages and the report viewer web part to view the rdl. This allows us to put a section above the report with descriptive text and the report runs below.

This incompatibility behaviour started last week for some users who let updatds throught (they aren't supposed to be able but that is another story).

If I navigate to the actual rdl file it works fine. But on the aspx page with the web parts the parameters all disappear in the parameter pane after selecting a date parameter. Changing the emulation mode seems to help most of the time but it doesn't stick (emulation goes back to a default of 8) Anyway it feels like this is not the root cause solution. Is there an ssrs update to fix this?

In Sharepoint I'm not sure where to find any configuration file with the meta tags. There doesnt seem to be a reportviewer.aspx file that I can locate.

Friday, January 6, 2017 - 3:59:16 PM - Doug

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?

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

</head>

Tuesday, September 20, 2016 - 3:55:46 AM - Johnb	Back To Top (43363)
Doesn't work. Please post appropriate solutin.

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

Hi,

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 (38766)
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

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

~Tony

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

Hi Kris,

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

-Greg

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

"Change the meta tag from to ,"

Change what to what?