I had both the 2000 version and then upgraded to 2005 and didn't do anything
special for the users and printing worked, so, I'm not sure why it isn't
working for you. Are the user local administrators on their machines?

Signature
Bruce Loehle-Conger
MVP SQL Server Reporting Services
> It seems that the RSClientPrint activex control for printing in RS 2005
> has
[quoted text clipped - 9 lines]
> the
> steps of removing the old control.
SteveIrwin - 26 Mar 2006 23:54 GMT
Thanks for the reply. Yes they are administrators on their machines. I just
had a thought: we are using Enterprise edition on 2005, but only Standard on
2000. I wonder if that's our problem.
Steve
> I had both the 2000 version and then upgraded to 2005 and didn't do anything
> special for the users and printing worked, so, I'm not sure why it isn't
[quoted text clipped - 15 lines]
>
> .
Bruce L-C [MVP] - 27 Mar 2006 15:51 GMT
I sure wouldn't think so. The printing ActiveX control should be the same
regardless of being Enterprise or Standard.

Signature
Bruce Loehle-Conger
MVP SQL Server Reporting Services
> Thanks for the reply. Yes they are administrators on their machines. I
> just
[quoted text clipped - 27 lines]
>>
>> .
Randeep - 28 Mar 2006 17:02 GMT
> I sure wouldn't think so. The printing ActiveX control should be the same
> regardless of being Enterprise or Standard.
[quoted text clipped - 38 lines]
> >>
> >> .
We are also having this problem. It appears that you will have no
issues if you access the report from the reports2005 directory but if
you access it from the reportserver2005 directory then the control will
not work or download correctly!
Let me just chime in that I have the same issue.
I need a fix for this! It's a mess. The 2005 version of rsclientprint
won't print a sql2000 based report and a sql2000 won't print a 2005 based
report.
The sql2005 report needs to be backward compatible or
the two rsclientprints needs different names for version 2000 and version
2005.
Help anyone? I deploy my 2005 stuff next week!!
> It seems that the RSClientPrint activex control for printing in RS 2005 has
> the same version as the RS 2000 control. So if users already have the RS 2000
[quoted text clipped - 5 lines]
> machines, and I'd hate to try tell my users that they have to go through the
> steps of removing the old control.
Bruce L-C [MVP] - 24 Apr 2006 19:18 GMT
I'm not really sure how this works but I had people printing with RS 2000,
when I upgraded to RS 2005 they were able to continue printing with no
difficulty. I don't know if the control got downloaded again or not. Note
that I am not mixing versions here. I was either all RS 2000 or all RS 2005.

Signature
Bruce Loehle-Conger
MVP SQL Server Reporting Services
> Let me just chime in that I have the same issue.
> I need a fix for this! It's a mess. The 2005 version of rsclientprint
[quoted text clipped - 20 lines]
>> the
>> steps of removing the old control.
Bava Mani - 11 May 2006 20:13 GMT
Hi,
I didnt see the soltuon for the Steve and Kevin facing.
I want to know the actual solution if some one face the same issue.
I dont know why this session is in the answered list!!!
~Bava
> Let me just chime in that I have the same issue.
> I need a fix for this! It's a mess. The 2005 version of rsclientprint
[quoted text clipped - 16 lines]
> > machines, and I'd hate to try tell my users that they have to go through the
> > steps of removing the old control.
David Brazier - 31 May 2006 17:08 GMT
Hi
I thought I had stumbled across this too, but on further investigation I
found that the 2005 RSClientPrint would successfully print *most* 2000
reports. One exception that produces the "An error occured during printing"
error is in MS CRM 3.0 - in the Neglected Accounts report, drill down to a
detail report - this won't print with the 2005 control. Our CRM uses RS 2000.
I found that if I manually remove the 2005 RSClientPrint and let the CRM
report install the 2000 version, the report would print. But then 2005
reports won't print. Am I right in thinking that you should have to manually
remove the 2000 RSClientPrint to allow the 2005 one to install? Shouldn't it
upgrade automatically?
Anyway, I hope the example from MS CRM will allow MS folks to investigate
this.
David