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.
> >> >
> >
>
>

Client Components Fail to Install - UPDATE

Me as well can not install the client components on boxes that have CLR 2.0/Office 2007 already installed. Notice that the failures have occured on boxes that doesn't have any SQL Server 2005 components installed. I do not know if it is CLR 2.0 or Office that causes the failures.

The error I'm getting initially is the same as Bogey1 and willgart: "

Upgrade failed due to the following error. The error code is:

-2147467259. Message: Unspecified error"

I have narrowed the failure down somewhat further; it occurs during installation of Business Intelligence Development Studio and it seems to happen during a process when it tries to upgrade the Microsoft Report Server (I have not installed Reporting Services - and it does not make any difference if Reporting Services is installed or not).

The workaround is obviously to choose an advanced setup and de-select BI Dev Studio from the Client Components installation node.

So far this has happened on following boxes:
1. LongHorn Server Beta 3 (LH) with CLR 3.0 and Office 2007 installed
2. A complete new install of LH Server, i.e nothing on the box that is not part of a normal LH installation (notice that CLR 2.0 is part of a LH installation).
3. Win 2K3 sp2 with CLR 3.0 and Office 2007 installed

In the installations above I have no Visual Studio bits installed what-so-ever

The installation succeeded on a complete new Win 2K3 sp2 installation; i.e. no CLR 2.0 bits and no Office 2007 bits.

Hope someone can shed some light on this.

Niels

OK, so I have now done a successful installation on a W2K3 sp2 box with Office 2007 installed - but no CLR 2.0/3.0. Remember from the initial post in this thread that the installation fails on W2K3 sp2 with CLR 2.0 and Office 2007.

It seems that the failures some of us have seen are due to having CLR 2.0/3.0 installed.

After the successful installation I installed the CLR 2.0 SDK, CLR 3.0 and Orcas and everything works just fine.

Niels
|||

Are you sure you do not have Microsoft Visual Studio installed by some application?

This error is usually due to VS installed in a non-default location.

Please confirm if you have VS installed in a non-default location, and if so, make sure that you have devenv.exe.config installed in its default location. For VS8:

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe.config

|||Hi,

Thanks for coming back to me on this. The only thing that I have installed, when the installation has failed is CLR 2.0 and the CLR 2.0 SDK. I don't know if the SDK installation installs the VS bits (but I doubt it).

Niels
|||Please double-check if you have this file installed in a non-default location. VS installs as a pre-req for some components, and you might not notice that it is installed.|||Will do. However I'm on the road for another week, and won't be able to do it until I'm back.

Thanks again!

Niels

Client Components Fail to Install - UPDATE

Me as well can not install the client components on boxes that have CLR 2.0/Office 2007 already installed. Notice that the failures have occured on boxes that doesn't have any SQL Server 2005 components installed. I do not know if it is CLR 2.0 or Office that causes the failures.

The error I'm getting initially is the same as Bogey1 and willgart: "

Upgrade failed due to the following error. The error code is:

-2147467259. Message: Unspecified error"

I have narrowed the failure down somewhat further; it occurs during installation of Business Intelligence Development Studio and it seems to happen during a process when it tries to upgrade the Microsoft Report Server (I have not installed Reporting Services - and it does not make any difference if Reporting Services is installed or not).

The workaround is obviously to choose an advanced setup and de-select BI Dev Studio from the Client Components installation node.

So far this has happened on following boxes:
1. LongHorn Server Beta 3 (LH) with CLR 3.0 and Office 2007 installed
2. A complete new install of LH Server, i.e nothing on the box that is not part of a normal LH installation (notice that CLR 2.0 is part of a LH installation).
3. Win 2K3 sp2 with CLR 3.0 and Office 2007 installed

In the installations above I have no Visual Studio bits installed what-so-ever

The installation succeeded on a complete new Win 2K3 sp2 installation; i.e. no CLR 2.0 bits and no Office 2007 bits.

Hope someone can shed some light on this.

Niels

OK, so I have now done a successful installation on a W2K3 sp2 box with Office 2007 installed - but no CLR 2.0/3.0. Remember from the initial post in this thread that the installation fails on W2K3 sp2 with CLR 2.0 and Office 2007.

It seems that the failures some of us have seen are due to having CLR 2.0/3.0 installed.

After the successful installation I installed the CLR 2.0 SDK, CLR 3.0 and Orcas and everything works just fine.

Niels
|||

Are you sure you do not have Microsoft Visual Studio installed by some application?

This error is usually due to VS installed in a non-default location.

Please confirm if you have VS installed in a non-default location, and if so, make sure that you have devenv.exe.config installed in its default location. For VS8:

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe.config

|||Hi,

Thanks for coming back to me on this. The only thing that I have installed, when the installation has failed is CLR 2.0 and the CLR 2.0 SDK. I don't know if the SDK installation installs the VS bits (but I doubt it).

Niels
|||Please double-check if you have this file installed in a non-default location. VS installs as a pre-req for some components, and you might not notice that it is installed.|||Will do. However I'm on the road for another week, and won't be able to do it until I'm back.

Thanks again!

Niels

Client Components Fail to Install

Me as well can not install the client components on boxes that have CLR 2.0/Office 2007 already installed. Notice that the failures have occured on boxes that doesn't have any SQL Server 2005 components installed. I do not know if it is CLR 2.0 or Office that causes the failures.

The error I'm getting initially is the same as Bogey1 and willgart: "

Upgrade failed due to the following error. The error code is:

-2147467259. Message: Unspecified error"

I have narrowed the failure down somewhat further; it occurs during installation of Business Intelligence Development Studio and it seems to happen during a process when it tries to upgrade the Microsoft Report Server (I have not installed Reporting Services - and it does not make any difference if Reporting Services is installed or not).

The workaround is obviously to choose an advanced setup and de-select BI Dev Studio from the Client Components installation node.

So far this has happened on following boxes:
1. LongHorn Server Beta 3 (LH) with CLR 3.0 and Office 2007 installed
2. A complete new install of LH Server, i.e nothing on the box that is not part of a normal LH installation (notice that CLR 2.0 is part of a LH installation).
3. Win 2K3 sp2 with CLR 3.0 and Office 2007 installed

In the installations above I have no Visual Studio bits installed what-so-ever

The installation succeeded on a complete new Win 2K3 sp2 installation; i.e. no CLR 2.0 bits and no Office 2007 bits.

Hope someone can shed some light on this.

Niels

OK, so I have now done a successful installation on a W2K3 sp2 box with Office 2007 installed - but no CLR 2.0/3.0. Remember from the initial post in this thread that the installation fails on W2K3 sp2 with CLR 2.0 and Office 2007.

It seems that the failures some of us have seen are due to having CLR 2.0/3.0 installed.

After the successful installation I installed the CLR 2.0 SDK, CLR 3.0 and Orcas and everything works just fine.

Niels
|||

Are you sure you do not have Microsoft Visual Studio installed by some application?

This error is usually due to VS installed in a non-default location.

Please confirm if you have VS installed in a non-default location, and if so, make sure that you have devenv.exe.config installed in its default location. For VS8:

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe.config

|||Hi,

Thanks for coming back to me on this. The only thing that I have installed, when the installation has failed is CLR 2.0 and the CLR 2.0 SDK. I don't know if the SDK installation installs the VS bits (but I doubt it).

Niels
|||Please double-check if you have this file installed in a non-default location. VS installs as a pre-req for some components, and you might not notice that it is installed.|||Will do. However I'm on the road for another week, and won't be able to do it until I'm back.

Thanks again!

Niels