January 9, 2014 at 8:32 am
Our end users on their XP machines who are using IE 8 are not having this issue. However anyone on Windows 7 and using IE 10 or IE 11 have the browser stop working when trying to use the Print icon in Report Builder. I have both Active X controls downloaded RS ClientPrint 64 & 2008.
Our Report Viewer on the Report server is version 2008 Sp1. I have tried everything else on the enduser side. Such as upgrading the endusers machine to .NET 4.5, adding the Report server as a trusted site, compatability mode all with the same result.
Any suggestions?
Should we upgrade to Report Viewer 2012?
***SQL born on date Spring 2013:-)
January 9, 2014 at 10:14 am
We've run into a lot of browser compatibility issues lately with the newest browsers -- it's almost like the bad old days of the Mozillia Netscape / Microsoft IE wars. You could try changing the compatibility settings in your IE 10 or IE 11 (hit F12 to bring those up).
Good luck,
Rob
January 10, 2014 at 4:20 am
SSRS ReportViewer relies on ActiveX for client-side printing which only works in IE. However, in IE10 or greater with default rendering mode, ActiveX is not supported. That's why print button is not available or not working. The only way to get it back is by using the following meta tag to force IE 10 or greater to render as v9 at least:
<meta http-equiv="x-ua-compatible" content="IE=9" >
If you are using SSRS Report Manager website, then try to find the ReportViewer.aspx physical file on your server disk and edit it with notepad by adding that meta tag under the <head> section
If you are using ASP.NET ReportViewer control instead, then edit your aspx page doing the same. If you do not want this approach, then you can take a look at this article that allows cross-browser (IE, Chrome, Firefox, etc) RDL printing by adding a custom Print button to ReportViewer toolbar and use that one or implement something similar by yourself.
January 10, 2014 at 7:33 am
We actually fixed it. It now runs just fine on IE 10 and 11.
I made the mistake of thinking our Sys Admin had SQL Server 2008 r2 up to date.
Simply adding the correct Service Packs fixed the issue!
***SQL born on date Spring 2013:-)
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply