June 5, 2006 at 2:36 pm
Hi,
We have 2 servers with RS:
1.SQL Server 2000 SP3a + RS SP2
2.SQL RS 2005 SP1
When we try to use client side printing in SQL 2000 RS we getting error "An error occured during printing '0x8007F304' ".
When we try to use client side printing in SQL 2005 RS, it print fine without any problem.
Thank you,
Lenn
June 5, 2006 at 2:50 pm
I had something similar to this for a while. I had to uninstall the print control and then reconnect to the 2005 server and re-install the print control to fix it.
June 5, 2006 at 3:17 pm
Hi,
Thanks for reply.
I'll do it tomorrow.
But I need that reports can be print from RS for both RS2000 and RS2005.
Thanks,
Lenn
June 6, 2006 at 4:52 am
I'm having the same problem, though we have now ditched the SS2000 report manager. Seems you can't have your cake AND eat it.
June 6, 2006 at 5:39 am
I have this problem as well. We've opened a ticket with Microsoft. Aparently it is something with their GDIplus
Once I get a solution, I will post it.
______________________________________________________________________
Personal Motto: Why push the envelope when you can just open it?
If you follow the direction given HERE[/url] you'll likely increase the number and quality of responses you get to your question.
Jason L. SelburgJune 6, 2006 at 7:41 am
Thank you everybody for replies.
I am going to look for solution with the help of Microsoft.
June 6, 2006 at 8:00 am
You can go to your winnt\“Downloaded Program Files” directory and right click update or delete the RSClientPrint active x control. If you delete it then the next time you click the print button on the RS toolbar it will download. This can help if you have an old or corrupted control.
June 6, 2006 at 8:37 am
I have tried this solution to remove "RSClientPrint Class" from the C:\WINDOWS\Downloaded Program Files\.
And, you are right, it installed ActiveX on the next print attempt. But it did not fix the problem.
June 10, 2006 at 6:08 pm
Microsoft had requested that I remove the display driver on my server. My first question, was how would the display driver affect printing. Apparently, the printing feature utilizes the GDIplus.dll which the Display driver changes settings in. I know this is a basic answer but it worked.
So, uninstall your display driver, reboot the machine and cancel the install of the driver and you should be able to print.
______________________________________________________________________
Personal Motto: Why push the envelope when you can just open it?
If you follow the direction given HERE[/url] you'll likely increase the number and quality of responses you get to your question.
Jason L. SelburgJanuary 9, 2007 at 1:29 pm
I know this is a little old, but maybe you still remember, my question is WHICH server did you uninstall the video driver on, SQL Server or the Web Server?
Thanks,
Robert
January 9, 2007 at 1:51 pm
Well, actually the server we have was both the SQL and the Web server. I would think it is the Web Server though, since it's the webserver/aspx files generating the file for printing.
______________________________________________________________________
Personal Motto: Why push the envelope when you can just open it?
If you follow the direction given HERE[/url] you'll likely increase the number and quality of responses you get to your question.
Jason L. SelburgViewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply