I deployed reports to a new server running Server 2003 and RS SP2. I can view
my reports in IE, and export them as PDF's. But when I put them on a shared
schedule, the PDF's throw a ReportRenderingException. The Excel reports are
running fine.
I need to run several hundred reports tomorrow, so any help would be
appreciated.
I can't find where this might be in the log files, searching for the report
name or the
string ReportRenderingException yields nothing.Hello,
From the post, it seems that you can view the report, and manually export
it to a pdf file successfully; however, when exporting the report via
Subscription as pdf file, you received the ReportRenderingException error.
You can export the report via Subscription as Excel reports successfully.
If I'm off base, please feel free to let me know.
Please note that the newsgroups are staffed weekdays by Microsoft Support
professionals to answer your non-urgent, break/fix systems and applications
questions. Since this issue is urgent, please contact Customer Service and
Support (CSS) for more immediate assistance. For more information on
available CSS services, please click here:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
.
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
If you'd like to work with newsgroup, please help me collect some
information to troubleshoot the issue or perform troubleshooting steps:
1. Please check if the issue is report related. If possible, test a simple
report to check the issue.
For example, if the issue occurs on a matrix report which has a several
matrix columns, check other report which isn't matrix report.
2. Please check if the issue is account related.
If possible, log on as a domain\administrative user account to test the
issue.
3. Please check if the issue is machine related.
4. Use FileMon and RegMon to check if there is any registry permission
issue or file permission issue.
You can download them from the following web site:
FileMon:
http://www.sysinternals.com/ntw2k/source/filemon.shtml
RegMon:
http://www.sysinternals.com/ntw2k/source/regmon.shtml
Check the FileMon log file and RegMon log file to see if there is any
"Access Denied" error. If so, grant full control on the related registry
key or files.
5. Check the reporting services log files. By default, the log files are
located in the C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles folder.
6. Post here the exact error message.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================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.|||Thanks, Sophie!
I resolved this particular problem with at "shot in the dark", makeing sure
that "Do not timeout report execution" was checked on Site Settings. This got
most of my reports to run properly.
I'm still getting occasional "Error: Subreport could not be shown" for
reports that I can run manually, and which can be run with the same
parameters on the same schedule! Reports running on that schedule after that
report run fine. Sometimes the error shows with the first subreport,
sometimes with only some (but once it shows up, all the subreports in that
report fail until the last one which has no external data connection.)
Perhaps there's another setting, not in the web-gui that I can set?
Thanks,
Avery.
"Sophie Guo [MSFT]" wrote:
> Hello,
> From the post, it seems that you can view the report, and manually export
> it to a pdf file successfully; however, when exporting the report via
> Subscription as pdf file, you received the ReportRenderingException error.
> You can export the report via Subscription as Excel reports successfully.
>|||Hello,
Based on my research, similar issue was resolved by recreating main report
or Subreport which has problems.
I suggest that you perform the following steps to narrow down the issue:
1. Check if the Subreport is able to render by itself as a stand-alone
report.
2. Check if the Main report is able to render by itself as a stand-alone
report.
3. Create a test report with a test subreport. Make sure it works fine.
4. Add the failing subreport to the test project and the test main report.
If it works fine, the original main report may have problems. If so,
recreate the original main report and add the subreport to it to test.
Also, you can configure the Report Server for Tracing. You may need to set
the Tracing Levels to 4 (Verbose mode). Then reproduce the issue. After
that, check the Reporting Services Trace Logs to find the cause.
For more information to configure a Report Server for Tracing, please
access the following web site:
Configuring a Report Server for Tracing
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm
/arp_configserver_v1_273t.asp
If the issue still exists, please post here the trace logs for research.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================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.
No comments:
Post a Comment