Monday, March 26, 2012

ReportViewer - Drill through reports not displaying completely

Hi,
I am developing a web page that used the ReportViewer Control for displaying
reports from our report Server. The Initial Report Displays just fine but
when there is a link on a report that drillsthrough to another report the new
report does not completely display correctly. Tables of Text appear find but
the graph images don't appear. If I look at the source for the report with
the broken images I notice that the ReportSession is different. Not sure if
it should be or if all reports in the report viewer should use the same
Reportsession' If I Click on the View Report button I receive an error
referencing yet another ReportSession. These reports all work just fine in
Report Manager so I'm thinking I need to set a parameter in the control'
I have tried setting the executionID but this seems to make no difference..
Can you help? Is there a Working sample of using the Control available'
Thanks
JasonHello Jason,
It seems to be a known issue caused by that combination of the Report
server and viewer default settings conflicting with rendering drill-through
reports. You may try the following methods to see if it helps:
1. Change the configuration information in the ReportServer database to not
use session cookies (Set the UseSessionCookies record value to false in
ReportServer.dbo.ConfigurationInfo).
2. Set the AsyncRendering property of the ReportViewer control to false (on
ReportViewer.aspx.cs).
If you have any further updates or comments, please feel free to let's
know. Thank you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks Peter,
Is there a fix in the works? or is this something to look for in SQL 08
Reporting Server'
""Peter Yang[MSFT]"" wrote:
> Hello Jason,
> It seems to be a known issue caused by that combination of the Report
> server and viewer default settings conflicting with rendering drill-through
> reports. You may try the following methods to see if it helps:
> 1. Change the configuration information in the ReportServer database to not
> use session cookies (Set the UseSessionCookies record value to false in
> ReportServer.dbo.ConfigurationInfo).
> 2. Set the AsyncRendering property of the ReportViewer control to false (on
> ReportViewer.aspx.cs).
> If you have any further updates or comments, please feel free to let's
> know. Thank you.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscriptions/support/default.aspx>.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>|||Hello Jason,
Since the issue is actually a reportviewer related issue you may want to
check if the workarounds I mentioned might work.
I have forwarded your feedback to the proper channel but product team may
evaluate the impact and consider fix this issue on client or server side.
Also, I encourage you submit via the link below and our product team would
like to hear your voice directly:
http://lab.msdn.microsoft.com/productfeedback/default.aspx
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
======================================================PLEASE NOTE:
This newsgroup service currently provides a one business day response time,
Monday through Friday, excluding holidays.
======================================================When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

No comments:

Post a Comment