August 7, 2012 at 2:05 pm
So we are in the process of converting over from Crystal to SSRS. Things seem to be going fine; however, we realize an issue today. Whenever the users try to print the first time, it tells them that you need to install SQL Server Reporting Services, which when you do, allows you to print just fine. The problem is, it's a pain because we have to log in as administrator, install this, log out and then let the user attempt to print the report again. I want to be able to just push this out to the whole network, as we continue to grow our SSRS, all users will need to print reports. I've done some research, but haven't really found a good solution to pushing this out. Please help, as I have converted a few departments over to the new reports, prior to realizing this was an issue.
Thanks,
Jordon
August 8, 2012 at 1:57 am
Could you not use something like group policy to install the client at logon time to the machine if its not already installed?
Do you not have any remote software depolyment tools like Altiris etc where you can package it up and ship it out to all your users without them knowing?
August 8, 2012 at 6:35 am
anthony.green (8/8/2012)
Could you not use something like group policy to install the client at logon time to the machine if its not already installed?Do you not have any remote software depolyment tools like Altiris etc where you can package it up and ship it out to all your users without them knowing?
Yes, I have several ways of deploying the software. The problem is, I don't have the software to deploy. I can't find it online to download. The only time it comes up is when a compuer tries to print a report for the first time, it gives them the option to Install or Don't Install. There is no way to download that installion package.
I've read online where people say you can extract the reclientprint.cab file, copy those .dll files into the system32 folder and then run a regsvr32 to register the reclientprint.dll; however, this doesn't work for me. It says it's successful when you register the dll, but when you go to print the report again, it still prompts you to install the reporting services.
August 8, 2012 at 6:49 am
You can find the RSClientPrint........cab file in the SSRS installation location.
Something like C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer\bin
Where you should find RSClientPrint-ia64.cab, RSClientPrint-x64.cab and RSClientPrint-x86.cab
Then you should be able to install that cab using pkgmgr.
August 8, 2012 at 7:03 am
anthony.green (8/8/2012)
You can find the RSClientPrint........cab file in the SSRS installation location.Something like C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer\bin
Where you should find RSClientPrint-ia64.cab, RSClientPrint-x64.cab and RSClientPrint-x86.cab
Then you should be able to install that cab using pkgmgr.
I've never used pkgmgr. Let me do some testing with this. Thanks for the information.
August 8, 2012 at 12:52 pm
anthony.green (8/8/2012)
You can find the RSClientPrint........cab file in the SSRS installation location.Something like C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer\bin
Where you should find RSClientPrint-ia64.cab, RSClientPrint-x64.cab and RSClientPrint-x86.cab
Then you should be able to install that cab using pkgmgr.
Okay, I've never used the pkgmgr before, so I did a little research. Based on the research that I did, I created the following batch file:
md c:\sandbox
copy "\\server\ssrs_install\RSClientPrint-x86.cab" c:\sandbox
start /w pkgmgr /ip /m:"c:\sandbox\RSClientPrint-x86.cab" /s:C:\sandbox /L:C:\install.log
rd c:\sandbox /s /q
I'm continuing to get an error with this script, saying the file can't be found; however, I know for a fact that the .cab file is there and I can open it in Windows Explorer and see all the .dll and .rll files inside it.
Any suggestions?
August 9, 2012 at 2:56 am
If you run the copy manually then run the pkgmgr on its own does it still error?
August 10, 2012 at 6:21 am
anthony.green (8/9/2012)
If you run the copy manually then run the pkgmgr on its own does it still error?
I'm afraid so. I can do a dir command and verify that the file is sitting there and still the same error.
August 13, 2012 at 12:26 pm
We run into this issue almost every time our SQL Servers have a major update (currently running SQL 2008 R2 SP2). The RS print control (rsclientprint.dll ) gets updated and our users can't install it as they are not admins. To work around this I find the required files by installing it on my computer and then look at the files that were installed in "C:\WINDOWS\Downloaded Program Files". The files could be hidden so you may need to open a command prompt and use the attrib command to remove the Hidden attribute. The files you are looking for are rsclientprint.dll, RSClientPrint-x86.inf and *.rll. We created a Visual Studio Installer project, added all these files to it, have it install to "C:\WINDOWS\Downloaded Program Files" and then compile it to a MSI. We use a separate deploment software product to push out all our installations and so we use it to push out this MSI file.
August 14, 2012 at 5:04 pm
Everybody out here (including me) obviously feels your pain, and I don't want to minimize this... but would it be possible to do an end-run around the problem by telling them to use the "Export to PDF" feature and print from the PDF?
You may run into other issues here if your report developers haven't consistently tested their layouts against the PDF renderer (it tends to require more exact attention to your margins or you're going to get interspersed blank pages - this is probably an SSRS FAQ someplace). However, at least most people already have a PDF reader available to them without administrative intervention.
>L<
April 30, 2013 at 10:15 am
DOH please disregard prev. post.
I fixed this by:
1) installing SP2 on my local PC to get the latest RSPrintClient cab files
2) deleted the RSPrintClient files from C:\Windows\DowloadedProgramFiles
3) renamed the existing R2 RSPrintClientxxx cab files on the server
4) copied over the SP2 cab files to the same folder on the server
this seemed to work, even with IE10 on Win7 Ultimate 64.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply