I posted before w/ no reply from someone from MS... trying again...
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:
1) Run the report
2) Click the print button
3) Select a printer and press ok
4) "Printing Now..." dialog box appears
5) "Print Error" dialog appears showing "An error occured during printing.
(0x80004005). The misspelling of "occured" is how it is displayed in the
message.
6) 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.
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.
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.Can you turn on the print logging. This might help us figure out the issue.
To turn on logging set the following registry key:
[HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Reporting
Services]
"LogRSClientPrintInfo"=dword:00000001
This will create a log file in the %temp% directory. The log file is called
Log#.tmp
You can send this to me (remove the online from my email address) and I can
try and take a look.
Thanks.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
<msmolarek@.community.nospam> wrote in message
news:08631FA3-B3E6-4FBB-A361-FB41952EB96D@.microsoft.com...
>I posted before w/ no reply from someone from MS... trying again...
> 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:
> 1) Run the report
> 2) Click the print button
> 3) Select a printer and press ok
> 4) "Printing Now..." dialog box appears
> 5) "Print Error" dialog appears showing "An error occured during printing.
> (0x80004005). The misspelling of "occured" is how it is displayed in the
> message.
> 6) 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.
> 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.
> 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.
>|||I am currently having the same problem. We have been fighting this for
about a month. It was working fine and then just started getting
errors. Any information you find please let me know.
Daniel Reib [MSFT] wrote:
> Can you turn on the print logging. This might help us figure out the issue.
> To turn on logging set the following registry key:
>
> [HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Reporting
> Services]
> "LogRSClientPrintInfo"=dword:00000001
> This will create a log file in the %temp% directory. The log file is called
> Log#.tmp
> You can send this to me (remove the online from my email address) and I can
> try and take a look.
> Thanks.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> <msmolarek@.community.nospam> wrote in message
> news:08631FA3-B3E6-4FBB-A361-FB41952EB96D@.microsoft.com...
> >I posted before w/ no reply from someone from MS... trying again...
> >
> > 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:
> >
> > 1) Run the report
> > 2) Click the print button
> > 3) Select a printer and press ok
> > 4) "Printing Now..." dialog box appears
> > 5) "Print Error" dialog appears showing "An error occured during printing.
> > (0x80004005). The misspelling of "occured" is how it is displayed in the
> > message.
> > 6) 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.
> >
> > 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.
> >
> > 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.
> >|||We are having the same printing error when using the printer icon from
reporting services. We are on version Microsoft SQL Server Reporting
Services Version 8.00.1042.00 .
--
myperotbot
"scootah" wrote:
> I am currently having the same problem. We have been fighting this for
> about a month. It was working fine and then just started getting
> errors. Any information you find please let me know.
> Daniel Reib [MSFT] wrote:
> > Can you turn on the print logging. This might help us figure out the issue.
> > To turn on logging set the following registry key:
> >
> >
> > [HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Reporting
> > Services]
> > "LogRSClientPrintInfo"=dword:00000001
> >
> > This will create a log file in the %temp% directory. The log file is called
> > Log#.tmp
> >
> > You can send this to me (remove the online from my email address) and I can
> > try and take a look.
> >
> > Thanks.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
> > <msmolarek@.community.nospam> wrote in message
> > news:08631FA3-B3E6-4FBB-A361-FB41952EB96D@.microsoft.com...
> > >I posted before w/ no reply from someone from MS... trying again...
> > >
> > > 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:
> > >
> > > 1) Run the report
> > > 2) Click the print button
> > > 3) Select a printer and press ok
> > > 4) "Printing Now..." dialog box appears
> > > 5) "Print Error" dialog appears showing "An error occured during printing.
> > > (0x80004005). The misspelling of "occured" is how it is displayed in the
> > > message.
> > > 6) 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.
> > >
> > > 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.
> > >
> > > 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.
> > >
>|||Hi,
Thanks for your posting.
Would you please paste detailed Reporting Services logs here?
1. Have you tried print the Report locally?
Please ensure EnableClientPrinting is set to True
2. Do you have SPS installed?
3. If you create a simple report or use the sample report, is it possible
for you to print them correctly?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||First to answer your questions:
1) Yes I have tried printing locally. Printing locally will get the first
page of the report to print but then it will produce the same error.
2) SPS? Share point services? I don't believe it is installed anywhere
3) All reports, even simple ones, fail in the same manner.
I will past in the log files from both the client and server when trying to
print:
CLINET
CResourceManager::ResetCulture - Ending Function: 0x00000000.
Url =http://reportersql/ReportServer?%2fRevenueSummaryReports%2fRevenueSummaryReport&ai_JobIndex=1795&ad_Date%3aisnull=True&rs:Command=Render&rs:format=IMAGE&rc:OutputFormat=emf&rc:StartPage=2&rc:EndPage=2&rc:PageWidth=11.0in&rc:PageHeight=8.500in&rc:MarginTop=6.350mm&rc:MarginBottom=6.350mm&rc:MarginLeft=6.350mm&rc:MarginRight=6.350mm&rs:GetNextStream=True
CPrintDlg::DrawFile - Starting Function.
CPrintDlg::DrawFile - Ending Function: 0x00000000.
Status from request was not 200, was (500)
SERVER (ReportServer__Timestamp.log)
w3wp!library!2948!12/15/2005-08:51:47:: i INFO: Cleaned 0 batch records, 0
policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs
w3wp!library!237c!12/15/2005-09:01:47:: i INFO: Cleaned 0 batch records, 0
policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs
w3wp!library!237c!12/15/2005-09:11:47:: i INFO: Cleaned 0 batch records, 0
policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs
w3wp!library!2d0c!12/15/2005-09:17:39:: i INFO: Call to
GetPermissions:/RevenueSummaryReports
w3wp!library!2948!12/15/2005-09:17:39:: i INFO: Call to GetSystemPermissions
w3wp!library!2d0c!12/15/2005-09:17:52:: i INFO: Call to
GetPermissions:/RevenueSummaryReports/RevenueSummaryReport
w3wp!library!2d0c!12/15/2005-09:17:52:: i INFO: Call to GetSystemPermissions
w3wp!library!2d0c!12/15/2005-09:17:55:: i INFO: Call to RenderFirst(
'/RevenueSummaryReports/RevenueSummaryReport' )
w3wp!library!2d0c!12/15/2005-09:17:57:: i INFO: Initializing
EnableExecutionLogging to 'True' as specified in Server system properties.
w3wp!webserver!2d0c!12/15/2005-09:17:57:: i INFO: Processed report.
Report='/RevenueSummaryReports/RevenueSummaryReport', Stream=''
w3wp!library!237c!12/15/2005-09:17:57:: i INFO: Call to RenderNext(
'/RevenueSummaryReports/RevenueSummaryReport' )
w3wp!chunks!237c!12/15/2005-09:17:57:: i INFO: ###
GetReportChunk('RenderingInfo_HTML4.0', 2), chunk was not found!
this=978e3a1b-85a2-4d77-aa23-05a90eebc8c9
w3wp!cache!237c!12/15/2005-09:17:57:: i INFO: Session live:
/RevenueSummaryReports/RevenueSummaryReport
w3wp!webserver!237c!12/15/2005-09:17:57:: i INFO: Processed report.
Report='/RevenueSummaryReports/RevenueSummaryReport', Stream=''
w3wp!library!237c!12/15/2005-09:18:03:: i INFO: Call to RenderFirst(
'/RevenueSummaryReports/RevenueSummaryReport' )
w3wp!library!237c!12/15/2005-09:18:04:: i INFO: Initializing
EnableExecutionLogging to 'True' as specified in Server system properties.
w3wp!webserver!2d0c!12/15/2005-09:18:04:: i INFO: Processed report.
Report='/RevenueSummaryReports/RevenueSummaryReport', Stream=''
w3wp!library!2c64!12/15/2005-09:18:04:: i INFO: Call to RenderNext(
'/RevenueSummaryReports/RevenueSummaryReport' )
w3wp!cache!2c64!12/15/2005-09:18:04:: i INFO: Item not cacheable: -
PersistStreams /RevenueSummaryReports/RevenueSummaryReport
w3wp!chunks!2c64!12/15/2005-09:18:04:: i INFO: ###
GetReportChunk('RenderingInfo_IMAGE', 2), chunk was not found!
this=75916a5c-0f80-4487-aa49-c88b5f2b6e5f
w3wp!webserver!237c!12/15/2005-09:18:05:: i INFO: Processed report.
Report='/RevenueSummaryReports/RevenueSummaryReport', Stream=''
w3wp!library!237c!12/15/2005-09:18:06:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.StreamNotFoundException:
The stream cannot be found. The stream identifier that is provided to an
operation cannot be located in the report server database., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.StreamNotFoundException:
The stream cannot be found. The stream identifier that is provided to an
operation cannot be located in the report server database.
w3wp!webserver!237c!12/15/2005-09:18:09:: e ERROR: Reporting Services error
Microsoft.ReportingServices.Diagnostics.Utilities.StreamNotFoundException:
The stream cannot be found. The stream identifier that is provided to an
operation cannot be located in the report server database.
w3wp!cache!2c64!12/15/2005-09:18:13:: i INFO: Session live:
/RevenueSummaryReports/RevenueSummaryReport
"Michael Cheng [MSFT]" wrote:
> Hi,
> Thanks for your posting.
> Would you please paste detailed Reporting Services logs here?
> 1. Have you tried print the Report locally?
> Please ensure EnableClientPrinting is set to True
> 2. Do you have SPS installed?
> 3. If you create a simple report or use the sample report, is it possible
> for you to print them correctly?
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Michael,
What is the best way to set the EnableClientPrinting property on my report
server?
--
myperotbot
"Michael Cheng [MSFT]" wrote:
> Hi,
> Thanks for your posting.
> Would you please paste detailed Reporting Services logs here?
> 1. Have you tried print the Report locally?
> Please ensure EnableClientPrinting is set to True
> 2. Do you have SPS installed?
> 3. If you create a simple report or use the sample report, is it possible
> for you to print them correctly?
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi,
Thanks for the update.
As Daniel Reib said, I am afraid we have to use print verbose logging to
check reporting services internla. Would you please
1) activate print logging by setting the reg key below
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Reporting
Services
If you don't have "Reporting Services" key and then just create one
2) Right click on the "Reporting Services" key and create a new dword
valued called "LogRSClientPrintInfo". set it's value data to 1.
3) Close and reopen the report manager and reproduce the error message.
4) log files should be in C:\Documents and Settings\<username>\Local
Settings\Temp
Search for "LogD**.tmp". Please email all of them from today.
I understand the information may be sensitive to you, my direct email
address is v-mingqc@.online.microsoft.com (please make sure you have removed
ONLINE before you click SEND), you may send the file to me directly and I
will keep secure.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment