Back call without drillthrough report

ASP.Net 2.0 Web app with ReportViewer Control.
I have a basic report that has a link to another report.
The first report loads OK then I click the link then the second report loads
OK.
But when I then hit the back button (the back arrow in the Reportviewer
Control) I get Back call without drillthrough report?
My control in aspx page:
<rsweb:ReportViewer ID="ReportViewer1" runat="server"
Font-Names="Verdana" Font-Size="9pt"
ProcessingMode="Remote"
Height="96%" Width="100%"
BorderColor="#ECE9D8" BorderStyle="Solid" BorderWidth="1px"
ShowBackButton="True">
</rsweb:ReportViewer>
my code behind:
string url = Request.QueryString["url"];
string path = Request.QueryString["path"];
if (!Page.IsPostBack)
{
ReportViewer1.ServerReport.ReportServerUrl = new System.Uri(url);
ReportViewer1.ServerReport.ReportPath = path;
}
Any ideas appretiated!The problem I have here only happens on some servers and not others. I
determind the diffrence between working and not workin servers is:
c:\windows\assembly\Microsoft.ReportViewer.WebForms
working servers have version 8.0.50727.42
servers with the problem have version 8.0.50727.762
Is there a way to downgrade Microsoft.ReportViewer.* assemblies? I try to
uninstall but not allowed. Maybe if I uninstall VS2005 and SP1 and
reinstall?
Thank you for any ideas!
"dev648237923" <dev648237923@.noemail.noemail> wrote in message
news:e8LjwTJeHHA.3996@.TK2MSFTNGP06.phx.gbl...
> ASP.Net 2.0 Web app with ReportViewer Control.
> I have a basic report that has a link to another report.
> The first report loads OK then I click the link then the second report
> loads OK.
> But when I then hit the back button (the back arrow in the Reportviewer
> Control) I get Back call without drillthrough report?
> My control in aspx page:
> <rsweb:ReportViewer ID="ReportViewer1" runat="server"
> Font-Names="Verdana" Font-Size="9pt"
> ProcessingMode="Remote"
> Height="96%" Width="100%"
> BorderColor="#ECE9D8" BorderStyle="Solid" BorderWidth="1px"
> ShowBackButton="True">
> </rsweb:ReportViewer>
> my code behind:
> string url = Request.QueryString["url"];
> string path = Request.QueryString["path"];
> if (!Page.IsPostBack)
> {
> ReportViewer1.ServerReport.ReportServerUrl = new System.Uri(url);
> ReportViewer1.ServerReport.ReportPath = path;
> }
> Any ideas appretiated!
>|||Hello Dev,
Based on my research, this is a known issue in ReportViewer Web control
after install the VS SP1.
The problem is the way the session keep alive ping happens. We ping each
session in the drillthrough stack to keep each one alive independently. But
the viewer http handler has logic to detect the following scenario:
1. User views main report
2. User clicks to a drillthrough report
3. User presses the *browser* back button
4. User performs an export/page navigation/another drillthrough/etc.
In the case of a browser back button click, the server doesn't know that
the user has moved back to the main report. So we have some information on
the url that tells the http handler that this request is for the parent
report (this is the reportstack=1 url parameter). As a result, the http
handler will unwind the drillthrough stack to the appropriate parent report
and continue processing.
The problem is that this reportstack parameter is also on the ping to keep
session alive. So immediately on rendering the page, the browser will now
ping all of the sessions. One of these is the root report, which eventually
unwinds the entire stack.
The only workaround is to not use ASP.Net session. The viewer can be
configured to not use session in server mode
(http://msdn2.microsoft.com/en-us/library/aa983458(VS.80).aspx). This
problem does not happen in local mode because there is only one session
regardless of how many drillthrough occur - the ASP.Net session.
If you want to downgrade to the early version of the controls, please use
the gacutility to remove the dlls from GAC and then install the earlier
redistribute package.
http://msdn2.microsoft.com/en-us/library/ex0ss12c(vs.80).aspx
And you could download the redistribute package here:
http://www.microsoft.com/downloads/details.aspx?familyid=8a166cac-758d-45c8-
b637-dd7726e61367&displaylang=en
Hope this will be helpful!
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
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.)|||Hi --
Is there a hotfix scheduled or do you think SP2 will have an updated viewer.
Thank you!
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:nOjNZpoeHHA.5016@.TK2MSFTNGHUB02.phx.gbl...
> Hello Dev,
> Based on my research, this is a known issue in ReportViewer Web control
> after install the VS SP1.
> The problem is the way the session keep alive ping happens. We ping each
> session in the drillthrough stack to keep each one alive independently.
> But
> the viewer http handler has logic to detect the following scenario:
> 1. User views main report
> 2. User clicks to a drillthrough report
> 3. User presses the *browser* back button
> 4. User performs an export/page navigation/another drillthrough/etc.
> In the case of a browser back button click, the server doesn't know that
> the user has moved back to the main report. So we have some information on
> the url that tells the http handler that this request is for the parent
> report (this is the reportstack=1 url parameter). As a result, the http
> handler will unwind the drillthrough stack to the appropriate parent
> report
> and continue processing.
> The problem is that this reportstack parameter is also on the ping to keep
> session alive. So immediately on rendering the page, the browser will now
> ping all of the sessions. One of these is the root report, which
> eventually
> unwinds the entire stack.
> The only workaround is to not use ASP.Net session. The viewer can be
> configured to not use session in server mode
> (http://msdn2.microsoft.com/en-us/library/aa983458(VS.80).aspx). This
> problem does not happen in local mode because there is only one session
> regardless of how many drillthrough occur - the ASP.Net session.
> If you want to downgrade to the early version of the controls, please use
> the gacutility to remove the dlls from GAC and then install the earlier
> redistribute package.
> http://msdn2.microsoft.com/en-us/library/ex0ss12c(vs.80).aspx
> And you could download the redistribute package here:
> http://www.microsoft.com/downloads/details.aspx?familyid=8a166cac-758d-45c8-
> b637-dd7726e61367&displaylang=en
> Hope this will be helpful!
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
> 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 Dev,
I don't get the information from product team. Currently, there is no
hotfix. I will confirm this with the product team.
For now, if you have any concern with the workaround, you may want to work
with Microsoft Customer Service and Support (CSS) for a faster resolution.
Once you open a Support incident with Microsoft CSS, a dedicated Support
Professional can work with you in a more efficient manner.
To obtain the phone numbers for a specific technology request please take a
look at the web site listed below.
<http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS>
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
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.)|||I meant to say 'It didn't work' Sorry
Andy
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com