Can't get reports to print

Hello,
We have never been able to get the printing to work on any of our reports
using SQL Server Reporting Services SP2.
During the time we have been fighting to get this to work we had added on
the SP, so we totally rebuilt the machine from scratch, that didn't help. In
addition a couple of months ago we bought a totally new machine to host our
reports and the fresh install on that machine didn't yeild any results.
At some point I found some posts in the newsgroup about needing to uninstall
an old ActiveX control used for printing, I did this and installed the new
one but that didn't help either.
We can print to things like the "Microsoft Office Document Image Writer"
without problem, only when we try to print to a real printer does it bomb out.
It doesn't matter how big the report is, 100 pages or 1/4 of a page, same
problem.
We do the following:
Run the report
Click the print button
Select a printer and press ok
"Printing Now..." dialog box appears
"Print Error" dialog appears showing "An error occured during printing.
(0x80004005). The misspelling of "occured" is how it is displayed in the
message.
Click OK and you get a JS error dialog "Line: 19. Error: Unspecifiied Error".
This is the result on every computer we have ever used in trying to access
the report server.
Any help?Are you printing to a local or network printer? Printing from IE, Firefox,
<insert other browser here>? I've had the best luck printing from IE to a
local printer.
--
Floyd
"msmolarek@.community.nospam"
<msmolarek@.community.nospam@.discussions.microsoft.com> wrote in message
news:C3830BDC-C2E0-4F82-85B8-101949ED1B5D@.microsoft.com...
> Hello,
> We have never been able to get the printing to work on any of our reports
> using SQL Server Reporting Services SP2.
> During the time we have been fighting to get this to work we had added on
> the SP, so we totally rebuilt the machine from scratch, that didn't help.
> In
> addition a couple of months ago we bought a totally new machine to host
> our
> reports and the fresh install on that machine didn't yeild any results.
> At some point I found some posts in the newsgroup about needing to
> uninstall
> an old ActiveX control used for printing, I did this and installed the new
> one but that didn't help either.
> We can print to things like the "Microsoft Office Document Image Writer"
> without problem, only when we try to print to a real printer does it bomb
> out.
> It doesn't matter how big the report is, 100 pages or 1/4 of a page, same
> problem.
> We do the following:
> Run the report
> Click the print button
> Select a printer and press ok
> "Printing Now..." dialog box appears
> "Print Error" dialog appears showing "An error occured during printing.
> (0x80004005). The misspelling of "occured" is how it is displayed in the
> message.
> Click OK and you get a JS error dialog "Line: 19. Error: Unspecifiied
> Error".
>
> This is the result on every computer we have ever used in trying to access
> the report server.
> Any help?|||We are printing to network printers from IE.
I hooked up a local printer to a computer just to try, and it prints the
first page OK, and then pops up the same error message as usual: "0x80004005"
Even if it worked on a local printer, this is supposed to be an enterprise
solution. 99% of our employees print to network printers.
"Floyd Burger" wrote:
> Are you printing to a local or network printer? Printing from IE, Firefox,
> <insert other browser here>? I've had the best luck printing from IE to a
> local printer.
> --
> Floyd
> "msmolarek@.community.nospam"
> <msmolarek@.community.nospam@.discussions.microsoft.com> wrote in message
> news:C3830BDC-C2E0-4F82-85B8-101949ED1B5D@.microsoft.com...
> > Hello,
> >
> > We have never been able to get the printing to work on any of our reports
> > using SQL Server Reporting Services SP2.
> >
> > During the time we have been fighting to get this to work we had added on
> > the SP, so we totally rebuilt the machine from scratch, that didn't help.
> > In
> > addition a couple of months ago we bought a totally new machine to host
> > our
> > reports and the fresh install on that machine didn't yeild any results.
> >
> > At some point I found some posts in the newsgroup about needing to
> > uninstall
> > an old ActiveX control used for printing, I did this and installed the new
> > one but that didn't help either.
> >
> > We can print to things like the "Microsoft Office Document Image Writer"
> > without problem, only when we try to print to a real printer does it bomb
> > out.
> >
> > It doesn't matter how big the report is, 100 pages or 1/4 of a page, same
> > problem.
> >
> > We do the following:
> >
> > Run the report
> > Click the print button
> > Select a printer and press ok
> > "Printing Now..." dialog box appears
> > "Print Error" dialog appears showing "An error occured during printing.
> > (0x80004005). The misspelling of "occured" is how it is displayed in the
> > message.
> > Click OK and you get a JS error dialog "Line: 19. Error: Unspecifiied
> > Error".
> >
> >
> > This is the result on every computer we have ever used in trying to access
> > the report server.
> >
> > Any help?
>
>|||I print exclusively to network printers. We do not have local printers at
work.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"msmolarek@.community.nospam"
<msmolarekcommunitynospam@.discussions.microsoft.com> wrote in message
news:5378230C-8CCE-43BE-9868-D1BC12940358@.microsoft.com...
> We are printing to network printers from IE.
> I hooked up a local printer to a computer just to try, and it prints the
> first page OK, and then pops up the same error message as usual:
> "0x80004005"
> Even if it worked on a local printer, this is supposed to be an enterprise
> solution. 99% of our employees print to network printers.
>
> "Floyd Burger" wrote:
>> Are you printing to a local or network printer? Printing from IE,
>> Firefox,
>> <insert other browser here>? I've had the best luck printing from IE to
>> a
>> local printer.
>> --
>> Floyd
>> "msmolarek@.community.nospam"
>> <msmolarek@.community.nospam@.discussions.microsoft.com> wrote in message
>> news:C3830BDC-C2E0-4F82-85B8-101949ED1B5D@.microsoft.com...
>> > Hello,
>> >
>> > We have never been able to get the printing to work on any of our
>> > reports
>> > using SQL Server Reporting Services SP2.
>> >
>> > During the time we have been fighting to get this to work we had added
>> > on
>> > the SP, so we totally rebuilt the machine from scratch, that didn't
>> > help.
>> > In
>> > addition a couple of months ago we bought a totally new machine to host
>> > our
>> > reports and the fresh install on that machine didn't yeild any results.
>> >
>> > At some point I found some posts in the newsgroup about needing to
>> > uninstall
>> > an old ActiveX control used for printing, I did this and installed the
>> > new
>> > one but that didn't help either.
>> >
>> > We can print to things like the "Microsoft Office Document Image
>> > Writer"
>> > without problem, only when we try to print to a real printer does it
>> > bomb
>> > out.
>> >
>> > It doesn't matter how big the report is, 100 pages or 1/4 of a page,
>> > same
>> > problem.
>> >
>> > We do the following:
>> >
>> > Run the report
>> > Click the print button
>> > Select a printer and press ok
>> > "Printing Now..." dialog box appears
>> > "Print Error" dialog appears showing "An error occured during printing.
>> > (0x80004005). The misspelling of "occured" is how it is displayed in
>> > the
>> > message.
>> > Click OK and you get a JS error dialog "Line: 19. Error: Unspecifiied
>> > Error".
>> >
>> >
>> > This is the result on every computer we have ever used in trying to
>> > access
>> > the report server.
>> >
>> > Any help?
>>|||How can I find the disconnect here then?
I have read that this error indicates "Access is denied", and others have
mentioned that maybe I don't have printer rights.
I am logged into my machine as a domain admin. I have no printing problems
in any program to any printer, except when using Reporting Services.
"Bruce L-C [MVP]" wrote:
> I print exclusively to network printers. We do not have local printers at
> work.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "msmolarek@.community.nospam"
> <msmolarekcommunitynospam@.discussions.microsoft.com> wrote in message
> news:5378230C-8CCE-43BE-9868-D1BC12940358@.microsoft.com...
> > We are printing to network printers from IE.
> >
> > I hooked up a local printer to a computer just to try, and it prints the
> > first page OK, and then pops up the same error message as usual:
> > "0x80004005"
> >
> > Even if it worked on a local printer, this is supposed to be an enterprise
> > solution. 99% of our employees print to network printers.
> >
> >
> > "Floyd Burger" wrote:
> >
> >> Are you printing to a local or network printer? Printing from IE,
> >> Firefox,
> >> <insert other browser here>? I've had the best luck printing from IE to
> >> a
> >> local printer.
> >>
> >> --
> >> Floyd
> >>
> >> "msmolarek@.community.nospam"
> >> <msmolarek@.community.nospam@.discussions.microsoft.com> wrote in message
> >> news:C3830BDC-C2E0-4F82-85B8-101949ED1B5D@.microsoft.com...
> >> > Hello,
> >> >
> >> > We have never been able to get the printing to work on any of our
> >> > reports
> >> > using SQL Server Reporting Services SP2.
> >> >
> >> > During the time we have been fighting to get this to work we had added
> >> > on
> >> > the SP, so we totally rebuilt the machine from scratch, that didn't
> >> > help.
> >> > In
> >> > addition a couple of months ago we bought a totally new machine to host
> >> > our
> >> > reports and the fresh install on that machine didn't yeild any results.
> >> >
> >> > At some point I found some posts in the newsgroup about needing to
> >> > uninstall
> >> > an old ActiveX control used for printing, I did this and installed the
> >> > new
> >> > one but that didn't help either.
> >> >
> >> > We can print to things like the "Microsoft Office Document Image
> >> > Writer"
> >> > without problem, only when we try to print to a real printer does it
> >> > bomb
> >> > out.
> >> >
> >> > It doesn't matter how big the report is, 100 pages or 1/4 of a page,
> >> > same
> >> > problem.
> >> >
> >> > We do the following:
> >> >
> >> > Run the report
> >> > Click the print button
> >> > Select a printer and press ok
> >> > "Printing Now..." dialog box appears
> >> > "Print Error" dialog appears showing "An error occured during printing.
> >> > (0x80004005). The misspelling of "occured" is how it is displayed in
> >> > the
> >> > message.
> >> > Click OK and you get a JS error dialog "Line: 19. Error: Unspecifiied
> >> > Error".
> >> >
> >> >
> >> > This is the result on every computer we have ever used in trying to
> >> > access
> >> > the report server.
> >> >
> >> > Any help?
> >>
> >>
> >>
>
>|||I have the same error on network printers..Anyone have any more advise on
this issue. I can add that the event log on the machine spits out event error
3, 4,8 in order when you issue the print command.
--
Ron Hatfield
Senior Consultant
I.B.I.S., Inc.
"msmolarek@.community.nospam" wrote:
> How can I find the disconnect here then?
> I have read that this error indicates "Access is denied", and others have
> mentioned that maybe I don't have printer rights.
> I am logged into my machine as a domain admin. I have no printing problems
> in any program to any printer, except when using Reporting Services.
>
> "Bruce L-C [MVP]" wrote:
> > I print exclusively to network printers. We do not have local printers at
> > work.
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "msmolarek@.community.nospam"
> > <msmolarekcommunitynospam@.discussions.microsoft.com> wrote in message
> > news:5378230C-8CCE-43BE-9868-D1BC12940358@.microsoft.com...
> > > We are printing to network printers from IE.
> > >
> > > I hooked up a local printer to a computer just to try, and it prints the
> > > first page OK, and then pops up the same error message as usual:
> > > "0x80004005"
> > >
> > > Even if it worked on a local printer, this is supposed to be an enterprise
> > > solution. 99% of our employees print to network printers.
> > >
> > >
> > > "Floyd Burger" wrote:
> > >
> > >> Are you printing to a local or network printer? Printing from IE,
> > >> Firefox,
> > >> <insert other browser here>? I've had the best luck printing from IE to
> > >> a
> > >> local printer.
> > >>
> > >> --
> > >> Floyd
> > >>
> > >> "msmolarek@.community.nospam"
> > >> <msmolarek@.community.nospam@.discussions.microsoft.com> wrote in message
> > >> news:C3830BDC-C2E0-4F82-85B8-101949ED1B5D@.microsoft.com...
> > >> > Hello,
> > >> >
> > >> > We have never been able to get the printing to work on any of our
> > >> > reports
> > >> > using SQL Server Reporting Services SP2.
> > >> >
> > >> > During the time we have been fighting to get this to work we had added
> > >> > on
> > >> > the SP, so we totally rebuilt the machine from scratch, that didn't
> > >> > help.
> > >> > In
> > >> > addition a couple of months ago we bought a totally new machine to host
> > >> > our
> > >> > reports and the fresh install on that machine didn't yeild any results.
> > >> >
> > >> > At some point I found some posts in the newsgroup about needing to
> > >> > uninstall
> > >> > an old ActiveX control used for printing, I did this and installed the
> > >> > new
> > >> > one but that didn't help either.
> > >> >
> > >> > We can print to things like the "Microsoft Office Document Image
> > >> > Writer"
> > >> > without problem, only when we try to print to a real printer does it
> > >> > bomb
> > >> > out.
> > >> >
> > >> > It doesn't matter how big the report is, 100 pages or 1/4 of a page,
> > >> > same
> > >> > problem.
> > >> >
> > >> > We do the following:
> > >> >
> > >> > Run the report
> > >> > Click the print button
> > >> > Select a printer and press ok
> > >> > "Printing Now..." dialog box appears
> > >> > "Print Error" dialog appears showing "An error occured during printing.
> > >> > (0x80004005). The misspelling of "occured" is how it is displayed in
> > >> > the
> > >> > message.
> > >> > Click OK and you get a JS error dialog "Line: 19. Error: Unspecifiied
> > >> > Error".
> > >> >
> > >> >
> > >> > This is the result on every computer we have ever used in trying to
> > >> > access
> > >> > the report server.
> > >> >
> > >> > Any help?
> > >>
> > >>
> > >>
> >
> >
> >