Client Side Print - An error occured during printing. (ox80070006)

When trying to print a report using the ActiveX control in Internet
Explorer I get the following error:
An error occured during printing. (ox80070006)
After some experimenting I found I was able to print (same client
computer / same server) to a file using the Generic / Text Only printer
driver and the Microsoft Office Document Image Writer.
So based on that I assumed the problem wasn't with the server.
Next I tried hooking my printer directly to my computer. The same
error occured.
I then tried a separate computer that printed to a separeate computer
and it worked.
Based on this I am assuming there is a issue with my printer / printer
driver and the ActiveX control.
My printer is a Samsung ML-1430.
I wanted to report this to the Reporting Services Team and see if
anyone else had any similar problems with other printers.
Thanks,
Warren Hales
P.S. I am new to Reporting Services and I have to say I am VERY
impressed. The Reporting Services Team has done a great job (IMHO).
It is an excellent example of an application with a SOA.Have you tried making sure you have a recent print driver? There have been
reports about printing problems going away once they updated the print
drivers.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Warren Hales" <warrenhales@.hotmail.com> wrote in message
news:1116604481.414270.179770@.g14g2000cwa.googlegroups.com...
> When trying to print a report using the ActiveX control in Internet
> Explorer I get the following error:
> An error occured during printing. (ox80070006)
> After some experimenting I found I was able to print (same client
> computer / same server) to a file using the Generic / Text Only printer
> driver and the Microsoft Office Document Image Writer.
> So based on that I assumed the problem wasn't with the server.
> Next I tried hooking my printer directly to my computer. The same
> error occured.
> I then tried a separate computer that printed to a separeate computer
> and it worked.
> Based on this I am assuming there is a issue with my printer / printer
> driver and the ActiveX control.
> My printer is a Samsung ML-1430.
> I wanted to report this to the Reporting Services Team and see if
> anyone else had any similar problems with other printers.
> Thanks,
> Warren Hales
> P.S. I am new to Reporting Services and I have to say I am VERY
> impressed. The Reporting Services Team has done a great job (IMHO).
> It is an excellent example of an application with a SOA.
>|||Hey Bruce.
I did download the latest print driver from Samsung and had the same
problem. I even tried a print driver from a compatible Samsung print
driver and that didn't work either.
One weird thing I found. If you click on the "printer" button in the
print dialog box, close it and then click print it gets a bit farther
along in the process. It prints a blank page and then shows the error
message.
Bruce L-C [MVP] wrote:
> Have you tried making sure you have a recent print driver? There have
been
> reports about printing problems going away once they updated the
print
> drivers.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Warren Hales" <warrenhales@.hotmail.com> wrote in message
> news:1116604481.414270.179770@.g14g2000cwa.googlegroups.com...
> > When trying to print a report using the ActiveX control in Internet
> > Explorer I get the following error:
> >
> > An error occured during printing. (ox80070006)
> >
> > After some experimenting I found I was able to print (same client
> > computer / same server) to a file using the Generic / Text Only
printer
> > driver and the Microsoft Office Document Image Writer.
> >
> > So based on that I assumed the problem wasn't with the server.
> >
> > Next I tried hooking my printer directly to my computer. The same
> > error occured.
> >
> > I then tried a separate computer that printed to a separeate
computer
> > and it worked.
> >
> > Based on this I am assuming there is a issue with my printer /
printer
> > driver and the ActiveX control.
> >
> > My printer is a Samsung ML-1430.
> >
> > I wanted to report this to the Reporting Services Team and see if
> > anyone else had any similar problems with other printers.
> >
> > Thanks,
> >
> > Warren Hales
> >
> > P.S. I am new to Reporting Services and I have to say I am VERY
> > impressed. The Reporting Services Team has done a great job
(IMHO).
> > It is an excellent example of an application with a SOA.
> >|||On of the problems might be the size of the print job that we send to the
printer. We are currently using a format called EMF + Dual which is pretty
hefty. We are looking whether we can trim it down in SQL 2005.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"Warren Hales" <warrenhales@.hotmail.com> wrote in message
news:1116688171.637976.68360@.g47g2000cwa.googlegroups.com...
> Hey Bruce.
> I did download the latest print driver from Samsung and had the same
> problem. I even tried a print driver from a compatible Samsung print
> driver and that didn't work either.
> One weird thing I found. If you click on the "printer" button in the
> print dialog box, close it and then click print it gets a bit farther
> along in the process. It prints a blank page and then shows the error
> message.
> Bruce L-C [MVP] wrote:
>> Have you tried making sure you have a recent print driver? There have
> been
>> reports about printing problems going away once they updated the
> print
>> drivers.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Warren Hales" <warrenhales@.hotmail.com> wrote in message
>> news:1116604481.414270.179770@.g14g2000cwa.googlegroups.com...
>> > When trying to print a report using the ActiveX control in Internet
>> > Explorer I get the following error:
>> >
>> > An error occured during printing. (ox80070006)
>> >
>> > After some experimenting I found I was able to print (same client
>> > computer / same server) to a file using the Generic / Text Only
> printer
>> > driver and the Microsoft Office Document Image Writer.
>> >
>> > So based on that I assumed the problem wasn't with the server.
>> >
>> > Next I tried hooking my printer directly to my computer. The same
>> > error occured.
>> >
>> > I then tried a separate computer that printed to a separeate
> computer
>> > and it worked.
>> >
>> > Based on this I am assuming there is a issue with my printer /
> printer
>> > driver and the ActiveX control.
>> >
>> > My printer is a Samsung ML-1430.
>> >
>> > I wanted to report this to the Reporting Services Team and see if
>> > anyone else had any similar problems with other printers.
>> >
>> > Thanks,
>> >
>> > Warren Hales
>> >
>> > P.S. I am new to Reporting Services and I have to say I am VERY
>> > impressed. The Reporting Services Team has done a great job
> (IMHO).
>> > It is an excellent example of an application with a SOA.
>> >
>|||FYI - I am seeing the same problem from one of our servers. The strange
thing is that I can print fine on two other servers that have SP2 installed
from the same reports on the same printers. One of the servers where the
printing is working was recently built (with SP2) and the other was upgraded
from SP1 to SP2 recently, so I can't see any pattern of when, where and why
this error is happening. It is failing on most of our reports that span 1
page (small reports as well as large ones). Any help is appreciated,
Brad Peterman
"Brian Welcker [MSFT]" wrote:
> On of the problems might be the size of the print job that we send to the
> printer. We are currently using a format called EMF + Dual which is pretty
> hefty. We are looking whether we can trim it down in SQL 2005.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Warren Hales" <warrenhales@.hotmail.com> wrote in message
> news:1116688171.637976.68360@.g47g2000cwa.googlegroups.com...
> > Hey Bruce.
> >
> > I did download the latest print driver from Samsung and had the same
> > problem. I even tried a print driver from a compatible Samsung print
> > driver and that didn't work either.
> >
> > One weird thing I found. If you click on the "printer" button in the
> > print dialog box, close it and then click print it gets a bit farther
> > along in the process. It prints a blank page and then shows the error
> > message.
> >
> > Bruce L-C [MVP] wrote:
> >> Have you tried making sure you have a recent print driver? There have
> > been
> >> reports about printing problems going away once they updated the
> > print
> >> drivers.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Warren Hales" <warrenhales@.hotmail.com> wrote in message
> >> news:1116604481.414270.179770@.g14g2000cwa.googlegroups.com...
> >> > When trying to print a report using the ActiveX control in Internet
> >> > Explorer I get the following error:
> >> >
> >> > An error occured during printing. (ox80070006)
> >> >
> >> > After some experimenting I found I was able to print (same client
> >> > computer / same server) to a file using the Generic / Text Only
> > printer
> >> > driver and the Microsoft Office Document Image Writer.
> >> >
> >> > So based on that I assumed the problem wasn't with the server.
> >> >
> >> > Next I tried hooking my printer directly to my computer. The same
> >> > error occured.
> >> >
> >> > I then tried a separate computer that printed to a separeate
> > computer
> >> > and it worked.
> >> >
> >> > Based on this I am assuming there is a issue with my printer /
> > printer
> >> > driver and the ActiveX control.
> >> >
> >> > My printer is a Samsung ML-1430.
> >> >
> >> > I wanted to report this to the Reporting Services Team and see if
> >> > anyone else had any similar problems with other printers.
> >> >
> >> > Thanks,
> >> >
> >> > Warren Hales
> >> >
> >> > P.S. I am new to Reporting Services and I have to say I am VERY
> >> > impressed. The Reporting Services Team has done a great job
> > (IMHO).
> >> > It is an excellent example of an application with a SOA.
> >> >
> >
>
>