Our environment is: Windows Server 2008. SQL 2008 R2.I create some report using BI and deploy them. Now anyone in the AD who does not have administrative right to download and install any software, they are getting error when they try to print SSRS report after render. I saw some ppl said, for the first time, it would ask to download & install. But how its possible to go to every PC in the organization to install first time manually and then carry on working ? Any alternative to this ? Another problem, even I install it for the first time, it is keep asking every time I try to print any report. What should I do ? I tried this: http://support.microsoft.com/kb/2295244 No luck. I tried manually register the rsclientprint like this site: http://www.kodyaz.com/articles/client-side-printing-silent-deployment-of-rsclientPrint.aspx No luck :( Any help please....monir

Hi Monir, please start by looking at this thread. http://social.technet.microsoft.com/Forums/en-US/sqlreportingservices/thread/2cf969ca-c627-4e79-ab12-46593c37cda4 if that doesnt work this blog entry describes various scenarios and the possible solutions. http://blogs.msdn.com/b/mariae/archive/2010/04/13/error-unable-to-load-client-print-control-when-printing-reports-in-reporting-services-summary-of-all-possible-causes-at-april-2010.aspx Thanks Hello, We are using Windows 7 (32 bit and 64 bits) in client machines. And our server is Windows 2008 and database = SQL 2008 R2. (Not SP1), SSRS = 2008. I went through both the above link before I mentioned it in this forum as I did tried from google to find a solution. Any other help please ? It seems nobody is using Windows 7 with Windows 2008, SQL 2008 R2... :( Thanks for your time to reply..monir

I'm getting the same issue, the above doesn't seem to work either. Any ideas? Thanks

I set up both settings in the following link which worked (might not actually have had to do both...) http://technet.microsoft.com/en-us/library/dd631688%28v=ws.10%29 Hello After long try, this has failed as well. It is still asking for administrator user and password :(monir

Here's what worked for me with exactly the same symptoms... I took a snapshot of a development server then upgraded it to SQL Server 2008 R2 SP2 CU3, and grabbed the three RSClientPrint ActiveX CAB files from the SQL Server Reporting Services folder: C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer\bin I then (on a test server) renamed the stock SQL Server 2008 R2 CAB files, and copied the ones taken from the upgraded dev server in their place. With this step complete, you have to elevate via UAC once, the controls are installed, and subsequent clicks on the print icon do not require elevation. From viewing the HTML source of one of my reports, it appears that SQL Server Reporting Services is embedding a CAB version into the ActiveX <object> tag which matches the SQL Server revision: CabUrl":"/ReportServer/Reserved.ReportViewerWebControl.axd?ExecutionID=zx5ym145zr003q55qlbflpvc&Culture=1033&CultureOverrides=False&UICulture=9&UICultureOverrides=False&ReportStack=1&ControlID=2b4bacd05d57409ebee3365be85aa9cd&OpType=PrintCab&Arch=X86#Version=2009,100,1617,00" This version string is higher than the version which is stamped into the actual CAB file, which in my case (stock SQL Server 2008 R2, no SPs or CUs) was as follows: [rsclientprint.dll] file=thiscab clsid={5554DCB0-700B-498D-9B58-4E40E5814405} RegisterServer=yes FileVersion=2009,100,1600,1 [rsclientprint64.dll] file=thiscab clsid={60677965-AB8B-464f-9B04-4BA871A2F17F} RegisterServer=yes FileVersion=2009,100,1600,1 I believe that this version mismatch (requesting 2009,100,1617,00 and only having 2009,100,1600,1 installed) is causing IE to attempt to re-download and install the control on every request. This same thing appears to have happened on at least a couple previous versions; see this thread: http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/799e7c86-1d2d-445f-9b18-687c1474e0a7 My hypothesis is that either this is something that was added back when MS had to Killbit the print control, and by default they're outputting the version of SQL Server rather than the version of the control, or that there's a defect in the control's build process so that it isn't getting properly stamped with the current SQL Server build number. Either way, it was pretty painful figuring out what's actually going on here. I don't know if MS has addressed this in SQL Server 2012, but I sure hope so. There are a lot of Windows 7 machines out there running UAC. Jason