November 23, 2012 at 12:34 am
Hi,
Different scenario..please its urgent..
please explain me briefly..
STARTING
Application on window Server 2003 64bit and report server on window sever 2003 with sql server 2005
We upgraded report server 2005 to sql server 2008 R2 SP2
Now from users end we faced issue with unable to load client print control
then we send new rsclient cab files to end users to paste in windows\system32
and allowed activex control to downlaod.
Problem fixed and things are going cool...
For some other reasons we placed the application server in the report server system
means now the application and reports server on same machine which is window server 2008R2 with SQL Server 2008 R2
when we are accessed the application and generating the reports same problem persists unable to load Client Print control.
Amazing is that when we access application from old server we are not facing any problem but the application/ report server getting error.
I goggled many things but noting..?
Please do the needful as earliest....
March 11, 2013 at 9:40 pm
I know this thread is old but did you find the fix?
Just so you know, when you change the report server, and sometimes just with a service pack, the dreaded Unable to Load Print Client issue comes up.
Another thing, depending on how you report and application is setup will determine the correct fix. Depending on the configuration, you may need to check the report redistributable that is installed, SQL Server version, and/or patch level of both.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply