If that works, I can put the new control next to the old one, and gradually migrate my users to a modern browser.I first encountered this issue today, where the client had packaged two versions of the SQL Server Reporting Services Client Printing ActiveX. This suggests that ActiveX printing is also possible with the new server, probably through the old Report viewer control. If you upgrade your report server to SQL Server 2016, the print control is not removed from the report server or client computers.' ' Previous versions of Reporting Services used an ActiveX control that required downloading to the client computer from the report server.

(If 100+ users print 50+ reports a day, having to download a pdf and print that is a BIG difference.) Printing with the new control DOESN'T work with IE. Printing with the old control only works on Internet Explorer, so all users use IE. However, I'd like to prevent a big bang implementation. I know there is a new reporting control, making the ActiveX print control obsolete. ProcessRequest(HttpContext context) +304 WritePrintCab(ClientArchitecture arch, Stream stream) +75 WritePrintCab(ClientArchitecture arch, Stream stream) +797 On my server, an exception is thrown: The report server could not find the internal resource '2015.'. ( version 11.0.0.0) However, when I try to print, the client displays a dialog box 'Unable to load client print control' In my test environment, reports from SSRS 2016 are rendered correctly by the old reporting control. If the client uses Internet Explorer, I serve the old one. So my test web server has both the new and the old reporting component. So I want to migrate to the new report server, yet show the reports through the old viewer for IE-users. Viewer: The ActiveX print control only works in Internet Explorer. I cannot migrate away from Internet Explorer because of the old report.If you click print, you can download a pdf and THEN print it.ĭue to the large amount of reports we print, this is no feasable option. The new report viewer cannot print nicely on Internet Explorer: I cannot move to the new reportviewer because I still have users on.

I have a chicken-egg-problem when upgrading from SSRS2014 to SSRS2016.

Where can i download rsclientprint.cab