SSRS 2008R2 - go back to parent report does not work sharepoint integrated mode (Network Steve Forum)

SSRS 2008R2 - go back to parent report does not work sharepoint integrated mode

I'm currently using SharePoint Foundation 2010 with SQL Server 2008R2 with the SharePoint RS add-in. I have a report with a drilldown to another report. I can drill down correctly to the other report. But when I do the "go back to parent report" it will take me back to the parent report, but when I try to drilldown again to another report, I get the following error. "Message: Sys.WebForms.PageRequestManagerParserErrorException: The message received from the server could not be parsed. Common causes for this error are when the response is modified by calls to Response.Write(), response filters, HttpModules, or server trace is enabled. Details: Error parsing near ' <!DOCTYPE html PUB'. Line: 5 Char: 62099" When I run this report in VS 2008 or Report Builder 3, I have no problems drilling down and back and forth. I only have an issue when I deploy the report to SharePoint. I have also accessed the RDL directly outside of a webpart page, but still get the same error. Wondering if anyone else is experiencing this issue?

August 12th, 2010 6:34am

Hi bh56, I have tried to reproduce the issue with the AdventureWorks Report Samples that are deployed to a SharePoint library. I drilled through the reports as same as you mentioned, however every thing works fine. Based on my searching, the issue should be related to AJAX. You may have a look at these thread: http://social.msdn.microsoft.com/forums/en-US/vbgeneral/thread/8ac5a5d6-3812-4bd5-bd90-53f4d671152a http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/9eaab93c-37c9-4343-889e-66ee29465d28 Alternatively, please try to update the SharePoint server to date, and check if the issue is solved. If you have any more questions, please feel free to ask. Thanks, Jin ChenJin Chen - MSFT

Free Windows Admin Tool Kit Click here and download it now

August 13th, 2010 9:21am

Jin, Thanks for your reply and suggestions. I have a little more information to provide. I'm running SSRS with SharePoint in integrated mode. I get the error when calling from a Web Part Page or even directly from calling the RDL. I've come across 2 different reports, where one works with the same drilldowns and the other does not. I actually have a number of reports that are broken. One works. I cannot determine what is different with the one report. If I change the one report to be similar to my other one, it stops working as well. I also came across the following error in the Event Log I will also make sure that the SharePoint and SSRS is on the latest patches. Just using a basic Image Properties with Action of Go to Report, passing a parameter. Can't understand why it would work for one report and not the other. Any insight would be appreciated. Below is the Event Log. Event code: 3005 Event message: An unhandled exception has occurred. Event time: 8/13/2010 4:53:21 PM Event time (UTC): 8/13/2010 9:53:21 PM Event ID: 106b3fa5a05b414095608016af288ef1 Event sequence: 1991 Event occurrence: 3 Event detail code: 0 Application information: Application domain: /LM/W3SVC/2105304215/ROOT-1-129261558292345041 Trust level: WSS_Minimal Application Virtual Path: / Application Path: C:\inetpub\wwwroot\wss\VirtualDirectories\80\ Machine name: sp-server Process information: Process ID: 6148 Process name: w3wp.exe Account name: NT AUTHORITY\NETWORK SERVICE Exception information: Exception type: HttpException Exception message: Failed to load viewstate. The control tree into which viewstate is being loaded must match the control tree that was used to save viewstate during the previous request. For example, when adding controls dynamically, the controls added during a post-back must match the type and position of the controls added during the initial request. Request information: Request URL: https://sp-server:443/Financial and Transactions/Transaction Inquiry.aspx Request path: /Financial and Transactions/Transaction Inquiry.aspx User host address: ::1 User: domain\username Is authenticated: True Authentication Type: Negotiate Thread account name: NT AUTHORITY\NETWORK SERVICE Thread information: Thread ID: 12 Thread account name: NT AUTHORITY\NETWORK SERVICE Is impersonating: False Stack trace: at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByID(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Page.LoadAllState() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) Custom event details:

Free Windows Admin Tool Kit Click here and download it now

August 14th, 2010 1:28am

I've narrowed down this issue to be related to parameters. If I have a Parameter that has available values versus one that has none, I get my issue. If I add a parameter ahead of the one with available/LOV, then my issue goes away. Wondering if anyone has seen this behavior before.

September 8th, 2010 9:07pm

We are having the same problem. The sub report parameters are kept on the report when we go back to the parent report. I have found that if the reporting site is accessed through the IIS on the report server. we do not have the back to parent on the report form, but we can click back in the browser and the Parent Report is maintained. I know this is not very useful because most users are accessing the site through SharePoint and security might be on the sharepoint lists and not on the data source. Another, and for us, more useful workaround I found was if parameters on the sub report are hidden no 'wrong' parms are shown with the parent report when going back and it is possible to issue another sub from the same parent. Only problem is that now we don't have any parms on the parent. But the idea is that if you are going to change the parameters on the parent anyway it is not that much extra work for user to refresh the parent report. The 3rd option as i see it is to have the exact same parameters on the parent and sub (even if they are not used). But that means more redesigning to get around this annoying BUG /Dvinge

Free Windows Admin Tool Kit Click here and download it now

November 2nd, 2010 4:57am

Sorry, I had not had a chance to circle back and update this posting. I ended up figuring out this issue with Microsoft. It is a bug that was just identified shortly before I contacted them. It was to be resolved in the next Cumulative Release or Service pack. ETA was October or November of 2010. A short term workaround was to hide the parameters on the child report. Hope this helps others.

November 3rd, 2010 10:58am

is the bug solved in this Cumulative Update? http://support.microsoft.com/kb/2507770/en-us

Free Windows Admin Tool Kit Click here and download it now

June 7th, 2011 4:51am

This topic is archived. No further replies will be accepted.