I have found a bug in SSRS 2008. I need this resolved. Thanks in advancefor your time. I can recreate this issue at will. I have a reporton the Home page for all users of SSRS 2008. When 2 users (user A, user B)access the report at the same time, and user A clicks the single page advance button of the web report view. User B will get the following error message if he attempts to click the single page advance button immediatly after. Server Error in '/Reports' Application. Execution '2wpoherjsischv45m2dxb0rt' cannot be found (rsExecutionNotFound) Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: Microsoft.Reporting.WebForms.ReportServerException: Execution '2wpoherjsischv45m2dxb0rt' cannot be found (rsExecutionNotFound)Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [ReportServerException: Execution '2wpoherjsischv45m2dxb0rt' cannot be found (rsExecutionNotFound)] Microsoft.Reporting.WebForms.ServerReport.GetExecutionInfo() +444 Microsoft.Reporting.WebForms.ServerReport.SetExecutionId(String executionId, Boolean fullReportLoad) +191 Microsoft.Reporting.WebForms.ServerReport.LoadFromUrlQuery(NameValueCollection requestParameters, Boolean fullReportLoad) +112 Microsoft.Reporting.WebForms.ReportDataOperation..ctor() +385 Microsoft.Reporting.WebForms.HttpHandler.GetHandler(String operationType) +462 Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) +67 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +599 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +171 Version Information:Microsoft .NET Framework Version:2.0.50727.3053; ASP.NET Version:2.0.50727.3053

Anyone have any idea about this issue?

Hi baaron, I cannot reproduce this issue. Can you be more specific in your repro? http or https? Parameters used in the report? None default settings on the server? Any other details you might think relevant.

Sure, 1. http or https? [http] 2. Parameters used in the report? [no] 3. None default settings on the server? [default settings] This is the first time I have used SSRS. Surely SSRS is designed so that more than one user may access a report at the same time. Right? It is almost behaving like it is designed for one at a time access. Thanks for the reply.

Baaron - I cannot reproduce your issue. I havemachines configured and running as different users. Product is working fine without that error. However, in the past I have seen a similar issue when your session expires. John Gallardo talks a bit about this on his blog: http://blogs.msdn.com/jgalla/archive/2006/10/11/session-timeout-during-execution.aspx If youcannot figure out what iscausing the problem,you can contact CSS or file an issue at http://connect.microsoft.com.

In order to produce the problem. You must logon as userA as an administrator, and userB as a user. The problem does not appear to be soley on the paging button. If you both browse to a report at the same time, the user that got there last can use the paging buttons, but the user that got there first will be given the error.

Did anyone found a solution to this problem? I have the same issue, having the exact same conditions as baaron.

Are you guys using basic authentication?

Yes,Ido.

Ok, you may be experiencing a bug in basic authentication when different users make concurrent requests. The workaround is to set <EnableAuthPersistence> in rsreportserver.config to False. Or if you installed SSRS2008 latest service pack it should take care of this issue.

Thanks James, settingEnableAuthPersistence to false fixed the problem.Not sure what "SSRS2008 latest service pack" means, I installed cumulative update package 3 (http://support.microsoft.com/default.aspx/kb/960484) 2 weeks ago, that obviously didn't fix this one :-) I'm not aware of any other service packs for 2008 at this moment.

SSRS2008 SP1 should contain the fix. I am actually not sure if it is available right now, but once you apply SP1 the problem should go away.

You can encrease the limit in "Reporting Services Server Default" if you run SSRS in SharePoint integrated mode. Central Administration > Configure Reporting Services Integration Reporting Services Server Defaults Use this page to view or modify the default server settings for Reporting Services. Report History Default Select the default number of snapshots to keep in report history. Do not limit the number of snapshots Limit number of snapshots to: Please enter a valuePlease enter a whole number greater than 0. Report Processing Timeout You can limit the amount of time that a report will execute before being stopped. Do not time out report processing Limit report processing (in seconds): Please enter a valuePlease enter a whole number greater than 0. Report Processing Log The report processing log keeps a record of when every report is processed as well as information about when it was run and by which user. Enable report processing log Remove log entries older than this many days Please enter a whole number greater than 0.Please enter a value Enable Windows Integrated Security Determines whether integrated security is supported for report data source connections. Enable Windows integrated security for report data sources Enable Ad Hoc Reporting The Report Builder Launch URL property allows you to specify the launch URL for the Report Builder ships with SQL Server 2008 or ReportBuilder 2.0. Enable ad hoc report executions Custom Report Builder launch URL Specify a custom URL for this property when the report server does not use the default Report Builder URL.

Well, I still have this problem when accessing any report from inside my portal. When accessing them directly thru the webservice using http://<reportservername>/ReportServerI have no problems. I just applied SP1 with CU2 released just a couple of days ago.Ideas?

I get this too. but heres the thing - i have multi tenancy and one organisation works fine, the other throws up this error. Anyone any thoughts - need this fixing asap.CheersDavid

Hi, In my case, this error ocurred only in the Browsers Internet Explorer 8 and Internet Explorer 9 with reports that takes more than 20 minutes for execute. I solved this problem optimizing the sql query procedure ( before optimize took 30 minutes to execute ) and now takes 3 minutes. I tried to configure increasing the session timeout in ReportManager configuration but anything solve the problem. This error is weird because in Google Chrome and Firefox works fine! Ricardo PrattiRicardo G. Pratti