Hi,
Has anyone found a solution to the problem of the reportviewer not printing
the first time you try to print? We found a solution on another newsgroup
but it doesn't fully resolve the problem.
Me.ReportViewer1.SetDisplayMode(Microsoft.Reporting.WinForms.DisplayMode.PrintLayout)Me.ReportViewer1.RefreshReport()
By using the displaymode.printlayout now you have to press the Print button
in the print dialog twice. But at least it prints. It seems that when the
print dialog displays it does not have focus. Clicking the print button or
anything else in the print dialog, then clicking the Print Button again does
actually print the report.there is a fix on msdn.
using a timer
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.comsql
Showing posts with label print. Show all posts
Showing posts with label print. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
ReportViewer control has no print button??
Is this just when you run the reports in local mode?
Yes, the report viewer in local mode has no print button. You will need to move your report to a reporting server to have the print button display.
-AO
Monday, March 26, 2012
ReportViewer
Is it it possible to edit the sample Report Viewer and
remove the scrollbars option and add a print option to
the toolbars.
We want to do so to create a developer standard for our
company.
Thanks!!You can easily edit and customize the sample. A client printing button is a
bit trickier because we do not have built-in support for client printing
currently directly from the HTML viewer. Right now, users are expected to
export to PDF or Image and then print. We are considering adding that
feature for future versions.
Currently, you can write your own printing control using a few of the
techniques in this article:
http://www.csharphelp.com/archives3/archive545.html
Some customers have already been working on solutions using direct rendering
and printing to PDF without user interaction. You can read some blog
comments at the bottom of the article here:
http://blogs.msdn.com/bryanke/articles/71491.aspx
--
Bryan Keller
Developer Documentation
SQL Server Reporting Services
A friendly reminder that this posting is provided "AS IS" with no
warranties, and confers no rights.
"Mark H" <anonymous@.discussions.microsoft.com> wrote in message
news:21ec201c45d1e$edea8bf0$a601280a@.phx.gbl...
> Is it it possible to edit the sample Report Viewer and
> remove the scrollbars option and add a print option to
> the toolbars.
> We want to do so to create a developer standard for our
> company.
> Thanks!!
remove the scrollbars option and add a print option to
the toolbars.
We want to do so to create a developer standard for our
company.
Thanks!!You can easily edit and customize the sample. A client printing button is a
bit trickier because we do not have built-in support for client printing
currently directly from the HTML viewer. Right now, users are expected to
export to PDF or Image and then print. We are considering adding that
feature for future versions.
Currently, you can write your own printing control using a few of the
techniques in this article:
http://www.csharphelp.com/archives3/archive545.html
Some customers have already been working on solutions using direct rendering
and printing to PDF without user interaction. You can read some blog
comments at the bottom of the article here:
http://blogs.msdn.com/bryanke/articles/71491.aspx
--
Bryan Keller
Developer Documentation
SQL Server Reporting Services
A friendly reminder that this posting is provided "AS IS" with no
warranties, and confers no rights.
"Mark H" <anonymous@.discussions.microsoft.com> wrote in message
news:21ec201c45d1e$edea8bf0$a601280a@.phx.gbl...
> Is it it possible to edit the sample Report Viewer and
> remove the scrollbars option and add a print option to
> the toolbars.
> We want to do so to create a developer standard for our
> company.
> Thanks!!
Wednesday, March 21, 2012
ReportServer 2005 print dialog crashes windows...
I'm a developer at a medium-sized installation using ReportServer 2005. There's a problem that occurs for some users and not others. After the ReportServer 2005 report has been generated, the user clicks the Print icon. The print dialog comes up; when they click the OK button on the Print dialog, the screen goes black and their machine reboots.
We've then gone to install the latest Microsoft updates on their machine, to no avail.
After the reboot, they can print from, e.g., Microsoft Word or other applications, but they crash the OS when they print from the ReportServer 2005 report.
I know the first time you print from ReportServer, it installs some software on your machine. I don't know if the problem is related to this.
Any ideas would be appreciated.
Charlie
Hi,
I got the same problem on 1 paticular machine ! Everytime you click the print-button --> os blue screen crash !?
|||Probably you've installed Microsoft Patch KB925902.
Remove it from your system and retry...
I've had the same problem printing with Reporting Service 2000.
Bye
--
|||Fabius...
Thanks for the hint about KB925902. However, this doesn't seem to apply to Report Server 2005. All our users have this patch, but some workstations abort on the Report print and some don't. But it was a good suggestion.
Thanks,
Charlie
|||Are you printing to HP printers that have a PCL6 driver installed?
We have noted the same issue, based on testing the PCL5 driver may work better, as a temporary fix.
|||MLane...
This was a great idea. Most of the printers here are HP. There's one Xerox printer. Report Server always prints correctly to the Xerox, but fails with the HP printers for some users and not others. Still doesn't explain why some users work and some don't, but it's a start and a good workaround.
Charlie
|||I had a number of calls on this problem too. The KB925902 patch seems to be logical, due to the timing of it all, but did you remove it from clients or from the server?
|||Mike...
We never actually removed KB925902 from any machines. ALL of our machines have this patch. Report Server printing crashes only on some client machines and not on others.
There also seems to be a correlation as to which printer driver is used. HP printer drivers seem to crash; Xerox printer drivers seem to be OK.
This problem seems to be client-side since some machines never crash and some always crash. I've opened a problem ticket with Microsoft on this.
Thanks,
Charlie
|||I just received this hotfix information from Microsoft.
WARNING: This fix is not publicly available through the Microsoft website as it has not gone through full Microsoft regression testing.If you would like confirmation that this fix is designed to address your specific problem, or if you would like to confirm whether there are any special compatibility or installation issues associated with this fix, you are encouraged to speak to a Support Professional in Product Support Services.
The package is password protected so be sure to enter the appropriate password for each package.To ensure the right password is provided cut and paste the password from this mail.
NOTE: Passwords expire every 7 days so download the package within that period to insure you can extract the files.If you receive two passwords it means you are receiving the fix during a password change cycle.Use the second password if you download after the indicated password change date.
Package:
--
KB Article Number(s): 935843
Language: English
Platform: i386
Location: (http://hotfixv4.microsoft.com/Windows%202000/sp5/Fix200463/2195/free/307588_ENU_i386_zip.exe)
Password: c3A@.XrLB@.
--
KB Article Number(s): 935843
Language: English
Platform: i386
Location: (http://hotfixv4.microsoft.com/Windows%20XP/sp3/Fix200284/2600/free/307536_ENU_i386_zip.exe)
Password: #m6#s5SJT
Password Changes On: 04/18/2007
Next Password: 7@.^V[*O
NOTE: Be sure to include all text between '(' and')' when navigating to this hot fix location!
|||Did you report this to the SQL Server feedback center? (https://connect.microsoft.com/SQLServer)
What is the ID of the ticket, I'd like to keep track of what MS have to say.
|||Yes, I just reported it. Case number is SRX 070 416 601 142. It's not yet resolved as I write this.
Charlie
|||Mike...
Thanks for this hotfix info. I downloaded the two files. I can't seem to find information about KB935843 at Microsoft or Google. I can't just install these files without more information about what they do. But I'll hold on to them.
Thanks,
Charlie
|||I have a Case number also SRX070416602399.
It seems that the cause was applying Windows Update patch KB925902 and if the client has a HP PCL6 printer driver configured. We were successful in duplicating this error on a VM running XP, applied the XP hotfix and it corrected the stop error from happening.
|||The problem with ReportServer crashing the client box while printing did indeed appear to be associated with the PCL6 printer drivers. When they were uninstalled from the client box and replaced with the PCL5 drivers, all seems OK. Something with PCL6 and ReportServer 2005.
Charlie
|||Check out this for discussion on the problem, hot fixes do work....as well as changing back to PCL5
http://support.microsoft.com/kb/935843
Denver
ReportServer 2005 print dialog crashes windows...
I'm a developer at a medium-sized installation using ReportServer 2005. There's a problem that occurs for some users and not others. After the ReportServer 2005 report has been generated, the user clicks the Print icon. The print dialog comes up; when they click the OK button on the Print dialog, the screen goes black and their machine reboots.
We've then gone to install the latest Microsoft updates on their machine, to no avail.
After the reboot, they can print from, e.g., Microsoft Word or other applications, but they crash the OS when they print from the ReportServer 2005 report.
I know the first time you print from ReportServer, it installs some software on your machine. I don't know if the problem is related to this.
Any ideas would be appreciated.
Charlie
Hi,
I got the same problem on 1 paticular machine ! Everytime you click the print-button --> os blue screen crash !?
|||Probably you've installed Microsoft Patch KB925902.
Remove it from your system and retry...
I've had the same problem printing with Reporting Service 2000.
Bye
--
|||Fabius...
Thanks for the hint about KB925902. However, this doesn't seem to apply to Report Server 2005. All our users have this patch, but some workstations abort on the Report print and some don't. But it was a good suggestion.
Thanks,
Charlie
|||Are you printing to HP printers that have a PCL6 driver installed?
We have noted the same issue, based on testing the PCL5 driver may work better, as a temporary fix.
|||MLane...
This was a great idea. Most of the printers here are HP. There's one Xerox printer. Report Server always prints correctly to the Xerox, but fails with the HP printers for some users and not others. Still doesn't explain why some users work and some don't, but it's a start and a good workaround.
Charlie
|||I had a number of calls on this problem too. The KB925902 patch seems to be logical, due to the timing of it all, but did you remove it from clients or from the server?
|||Mike...
We never actually removed KB925902 from any machines. ALL of our machines have this patch. Report Server printing crashes only on some client machines and not on others.
There also seems to be a correlation as to which printer driver is used. HP printer drivers seem to crash; Xerox printer drivers seem to be OK.
This problem seems to be client-side since some machines never crash and some always crash. I've opened a problem ticket with Microsoft on this.
Thanks,
Charlie
|||I just received this hotfix information from Microsoft.
WARNING: This fix is not publicly available through the Microsoft website as it has not gone through full Microsoft regression testing.If you would like confirmation that this fix is designed to address your specific problem, or if you would like to confirm whether there are any special compatibility or installation issues associated with this fix, you are encouraged to speak to a Support Professional in Product Support Services.
The package is password protected so be sure to enter the appropriate password for each package.To ensure the right password is provided cut and paste the password from this mail.
NOTE: Passwords expire every 7 days so download the package within that period to insure you can extract the files.If you receive two passwords it means you are receiving the fix during a password change cycle.Use the second password if you download after the indicated password change date.
Package:
--
KB Article Number(s): 935843
Language: English
Platform: i386
Location: (http://hotfixv4.microsoft.com/Windows%202000/sp5/Fix200463/2195/free/307588_ENU_i386_zip.exe)
Password: c3A@.XrLB@.
--
KB Article Number(s): 935843
Language: English
Platform: i386
Location: (http://hotfixv4.microsoft.com/Windows%20XP/sp3/Fix200284/2600/free/307536_ENU_i386_zip.exe)
Password: #m6#s5SJT
Password Changes On: 04/18/2007
Next Password: 7@.^V[*O
NOTE: Be sure to include all text between '(' and')' when navigating to this hot fix location!
|||Did you report this to the SQL Server feedback center? (https://connect.microsoft.com/SQLServer)
What is the ID of the ticket, I'd like to keep track of what MS have to say.
|||Yes, I just reported it. Case number is SRX 070 416 601 142. It's not yet resolved as I write this.
Charlie
|||Mike...
Thanks for this hotfix info. I downloaded the two files. I can't seem to find information about KB935843 at Microsoft or Google. I can't just install these files without more information about what they do. But I'll hold on to them.
Thanks,
Charlie
|||I have a Case number also SRX070416602399.
It seems that the cause was applying Windows Update patch KB925902 and if the client has a HP PCL6 printer driver configured. We were successful in duplicating this error on a VM running XP, applied the XP hotfix and it corrected the stop error from happening.
|||The problem with ReportServer crashing the client box while printing did indeed appear to be associated with the PCL6 printer drivers. When they were uninstalled from the client box and replaced with the PCL5 drivers, all seems OK. Something with PCL6 and ReportServer 2005.
Charlie
|||Check out this for discussion on the problem, hot fixes do work....as well as changing back to PCL5
http://support.microsoft.com/kb/935843
Denver
sqlReports Won't Print
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.
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.
Tuesday, March 20, 2012
Reports prints 1 page only
I am getting an error "An error occured during printing (0x80004005)" - when i am trying to print - and the i still am able to print - but only 1 page.
Thre registry key - Reporting services was not there - so i created it at
[HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Reporting Services]
"LogRSClientPrintInfo"=dword:00000001
Please help - what should i do now ?
What is the version of your Reporting Services? If you browse to http://<server>/ReportServer you will see the version number in the bottom right hand corner of the page. There is a KB article (http://support.microsoft.com/kb/907010) regarding a similar seeming problem for Reporting Services 2000 SP2.
Larry
|||Version number is
Microsoft SQL Server Reporting Services Version 9.00.1399.00
I use reporting services 2005
|||All reports, or just a specific one. When you say that it exports fine, have you tried exporting to PDF or TIFF? They are also 'page based' formats and may exibit the same failure. Have you looked in the IIS and SSRS log files? SSRS log files live at:
"C:\Program Files\Microsoft SQL Server\MSSQL.<#>\Reporting Services\LogFiles"
and your IIS log files are in:
"C:\Windows\System32\LogFiles\W3SVC1"
Do you see any errors that are occuring when you attempt to print? Have you looked in the server event logs? Are there any errors there?
Try getting the server to render the emf directly by browsing to the report on http:///ReportServer and appending
Code Snippet
&rs:Format=IMAGE&rc:OutputFormat=emfplus to the url that displays the report. For example:
Code Snippet
http://localhost/ReportServer/Pages/ReportViewer.aspx?%2fMetaDataExperiments%2fFirstReport&rs:Command=Render&rs:Format=IMAGE&rc:OutputFormat=emfplusand save the file locally. Do you get an error when the file downloads?
Thanks,
Larry
|||Hello,
Were you able to try the direct download of the EMF file? This is the file that is sent to the local print plugin. This trial should allow us to determine if the issue is a client or server problem.
Larry
reports print differently on different printers
Has anyone else run into this issue?
Dependingon the printer, the report prints differently. Sometimes it's all messed up on certain printers on others it prints fine. I see the problem mostly with older HP printers..
Any ideas?
Daryl
Hi There, What specifically is messed up? Is the issue you get what appears to be partial wrap around then gaps? So then end of a row wraps to the next line on the paper?
Does it only happen on larger/wider reports? So a simple narrow report thats much smaller than the page size works more consistently?
Assuming yes to all or most of the above, printers and printer dirvers define the printable region on the paper and there can be slight differences when going from 1 printer to another printer (or even 1 printer driver to another). Things are much more consistent these days though there are still some differences. Older printers, drivers, and operating systems exhibited a lot more differeneces.
Short of updating printers or printer drivers, you may try and change your report to make it just slightly smaller, and therefore it might fit on an older printer with perhaps a slightly smaller available printable region.
Hope that helps
|||here is an example
Report group header:
Invoice
Number
above is normal on a users printer it comes out as
Invoice
Number
It cuases all kinds of report problems when printing.
Monday, March 12, 2012
Reports in Lanscape
I am using Reporting services with ASP.NET/C#. How can I change print orientation of my reports to "landscape"?
Thanks,
RohitMake your page size wider than it is tall.
Reports in Landscape
I am using Reporting services with ASP.NET/C#. How can I change print orientation of my reports to "landscape"?
Thanks,
RohitMake your page size wider than it is tall.
Monday, February 20, 2012
Reporting Services: timeout issue
Hi there,
I've just developed this big report in RS SQL 2000 that includes 6 subreports (repeated for each item in the database) and that should print some 800 pages. A light version of the report that only queries part of the data (about 10%, for testing purposes) run with success, including all subreports in about 15 minutes. Once I try to test the report with all the data (all subreports and the main report query directly from the cube in AS), it fails under three different scenarios:
1st: The timeout setting is left as the default 1800 seconds. After half an hour the report gets partially displayed and the subreports that were not processed within the 30 minutes period display only "The subreport data could not be displayed".
2nd: The timeout value is set not to time out. After about 2 hours, the report fails ("The page cannot be displayed"). I checked all log files and the only one I could identify as related to this was the following:
SQL Server Scheduled Job 'ReportScheduler_CreateJobs' (0x4A64EE6822172C478B4DBF1E385699D6) - Status: Failed - Invoked on: 2006-01-09 13:00:00 - Message: The job failed. The Job was invoked by Schedule 1 (DailyRun). The last step to run was step 1 (spc_sched_CreateJobs).
3rd: Tried to export the file to PDF instead of rendering as HTML. I got the message on the page "Action Cancelled" and an IE message box displaying a "Permission Denied" error.
I've tried many things and ran out of ideas. If anyone could give me any suggestions, I'd greatly appreciate it.
Thanks,
érico Maia
Are you generating these reports from a web-service?|||The reason I ask that question is that there is a very obscure 'Flag' that is set by default to ignore any new Timeout value set for the web service timeout. It is located on the generated class interface. I don't remember the exact name of this flag, but maybe this will help you in looking to solve this problem. If I can remember its name I will post on this board. Obviously, there is an issue with this solution, which is, any time you re-generate the web interface class you will have to reset this.|||
Hi,
The report is executed directly from the RS web interface. I'm trying now to generate it via a subscription, but also without success. After increasing the time out settings of all config files I know of, the report fails exactly at the 120 minutes mark.
Thanks,
érico
|||Hi érico
Did you manage to find a solution to your problem? I am experiencing exactly the same behaviour.
-- TINUS
|||I am having similar issues that I am trying to resolve as well, running 2KSP4 1042. It's a new issue for us, as all of our reports worked fine until I started composing some large combination reports which take a significant amount of runtime (an hour or better). Due to the complexities of one of the reports involved, batching it is difficult (though not impossible), but some of the reading I've done lends me to believe that it may not even fix the problem.The report attempts to execute, and the control indicates that it's processing, but eventually results in the "Page cannot be displayed" error, while the RS navigation tools still function normally. Furthermore, I can navigate to other reports and operate them, but if I navigate back to the report in question, the control immediately goes to the "Page cannot be displayed" message. I have to close and reopen IE for the control to attempt to start the report again.
I've seen this in one or two other rare circumstances before, and after reloading the browser, the report would render, but this is the first time I've consistently gotten this error message, and I have to think it's because of the lengthy runtime of the reports in question. One has 34 subreports in it (each of which has a runtime of 2-3 minutes), and the other is just a very in-depth query which (depending on parameters selected) could be run once or upwards of 60 times (with totaling at the end). I've disabled the RS timeout for the affected reports and it doesn't seem to help at all (I believe previously I was just getting rsProcessingAborted).
Reporting Services: timeout issue
Hi there,
I've just developed this big report in RS SQL 2000 that includes 6 subreports (repeated for each item in the database) and that should print some 800 pages. A light version of the report that only queries part of the data (about 10%, for testing purposes) run with success, including all subreports in about 15 minutes. Once I try to test the report with all the data (all subreports and the main report query directly from the cube in AS), it fails under three different scenarios:
1st: The timeout setting is left as the default 1800 seconds. After half an hour the report gets partially displayed and the subreports that were not processed within the 30 minutes period display only "The subreport data could not be displayed".
2nd: The timeout value is set not to time out. After about 2 hours, the report fails ("The page cannot be displayed"). I checked all log files and the only one I could identify as related to this was the following:
SQL Server Scheduled Job 'ReportScheduler_CreateJobs' (0x4A64EE6822172C478B4DBF1E385699D6) - Status: Failed - Invoked on: 2006-01-09 13:00:00 - Message: The job failed. The Job was invoked by Schedule 1 (DailyRun). The last step to run was step 1 (spc_sched_CreateJobs).
3rd: Tried to export the file to PDF instead of rendering as HTML. I got the message on the page "Action Cancelled" and an IE message box displaying a "Permission Denied" error.
I've tried many things and ran out of ideas. If anyone could give me any suggestions, I'd greatly appreciate it.
Thanks,
érico Maia
Are you generating these reports from a web-service?|||The reason I ask that question is that there is a very obscure 'Flag' that is set by default to ignore any new Timeout value set for the web service timeout. It is located on the generated class interface. I don't remember the exact name of this flag, but maybe this will help you in looking to solve this problem. If I can remember its name I will post on this board. Obviously, there is an issue with this solution, which is, any time you re-generate the web interface class you will have to reset this.|||
Hi,
The report is executed directly from the RS web interface. I'm trying now to generate it via a subscription, but also without success. After increasing the time out settings of all config files I know of, the report fails exactly at the 120 minutes mark.
Thanks,
érico
|||Hi érico
Did you manage to find a solution to your problem? I am experiencing exactly the same behaviour.
-- TINUS
|||I am having similar issues that I am trying to resolve as well, running 2KSP4 1042. It's a new issue for us, as all of our reports worked fine until I started composing some large combination reports which take a significant amount of runtime (an hour or better). Due to the complexities of one of the reports involved, batching it is difficult (though not impossible), but some of the reading I've done lends me to believe that it may not even fix the problem.The report attempts to execute, and the control indicates that it's processing, but eventually results in the "Page cannot be displayed" error, while the RS navigation tools still function normally. Furthermore, I can navigate to other reports and operate them, but if I navigate back to the report in question, the control immediately goes to the "Page cannot be displayed" message. I have to close and reopen IE for the control to attempt to start the report again.
I've seen this in one or two other rare circumstances before, and after reloading the browser, the report would render, but this is the first time I've consistently gotten this error message, and I have to think it's because of the lengthy runtime of the reports in question. One has 34 subreports in it (each of which has a runtime of 2-3 minutes), and the other is just a very in-depth query which (depending on parameters selected) could be run once or upwards of 60 times (with totaling at the end). I've disabled the RS timeout for the affected reports and it doesn't seem to help at all (I believe previously I was just getting rsProcessingAborted).
Reporting Services: timeout issue
Hi there,
I've just developed this big report in RS SQL 2000 that includes 6 subreports (repeated for each item in the database) and that should print some 800 pages. A light version of the report that only queries part of the data (about 10%, for testing purposes) run with success, including all subreports in about 15 minutes. Once I try to test the report with all the data (all subreports and the main report query directly from the cube in AS), it fails under three different scenarios:
1st: The timeout setting is left as the default 1800 seconds. After half an hour the report gets partially displayed and the subreports that were not processed within the 30 minutes period display only "The subreport data could not be displayed".
2nd: The timeout value is set not to time out. After about 2 hours, the report fails ("The page cannot be displayed"). I checked all log files and the only one I could identify as related to this was the following:
SQL Server Scheduled Job 'ReportScheduler_CreateJobs' (0x4A64EE6822172C478B4DBF1E385699D6) - Status: Failed - Invoked on: 2006-01-09 13:00:00 - Message: The job failed. The Job was invoked by Schedule 1 (DailyRun). The last step to run was step 1 (spc_sched_CreateJobs).
3rd: Tried to export the file to PDF instead of rendering as HTML. I got the message on the page "Action Cancelled" and an IE message box displaying a "Permission Denied" error.
I've tried many things and ran out of ideas. If anyone could give me any suggestions, I'd greatly appreciate it.
Thanks,
érico Maia
Are you generating these reports from a web-service?|||The reason I ask that question is that there is a very obscure 'Flag' that is set by default to ignore any new Timeout value set for the web service timeout. It is located on the generated class interface. I don't remember the exact name of this flag, but maybe this will help you in looking to solve this problem. If I can remember its name I will post on this board. Obviously, there is an issue with this solution, which is, any time you re-generate the web interface class you will have to reset this.|||
Hi,
The report is executed directly from the RS web interface. I'm trying now to generate it via a subscription, but also without success. After increasing the time out settings of all config files I know of, the report fails exactly at the 120 minutes mark.
Thanks,
érico
|||Hi érico
Did you manage to find a solution to your problem? I am experiencing exactly the same behaviour.
-- TINUS
|||I am having similar issues that I am trying to resolve as well, running 2KSP4 1042. It's a new issue for us, as all of our reports worked fine until I started composing some large combination reports which take a significant amount of runtime (an hour or better). Due to the complexities of one of the reports involved, batching it is difficult (though not impossible), but some of the reading I've done lends me to believe that it may not even fix the problem.The report attempts to execute, and the control indicates that it's processing, but eventually results in the "Page cannot be displayed" error, while the RS navigation tools still function normally. Furthermore, I can navigate to other reports and operate them, but if I navigate back to the report in question, the control immediately goes to the "Page cannot be displayed" message. I have to close and reopen IE for the control to attempt to start the report again.
I've seen this in one or two other rare circumstances before, and after reloading the browser, the report would render, but this is the first time I've consistently gotten this error message, and I have to think it's because of the lengthy runtime of the reports in question. One has 34 subreports in it (each of which has a runtime of 2-3 minutes), and the other is just a very in-depth query which (depending on parameters selected) could be run once or upwards of 60 times (with totaling at the end). I've disabled the RS timeout for the affected reports and it doesn't seem to help at all (I believe previously I was just getting rsProcessingAborted).
Subscribe to:
Posts (Atom)