So, we switched to using Microsoft Reporting Services instead of Local reporting. However we had one issue with our configuration. We have our web site running in a farm with two servers with NLB implemented. Also, we have one server where we have our Reporting Services running. Since reports not that critical for our application, we decided just to have one server for that.
What we found though, is very often we got this message: ReportServerException: Execution 'uj2yx4bxgzfvwsvegkwuex45' cannot be found (rsExecutionNotFound)
While first googling suggested problems with timeout, I was pretty sure it's not the issue, and started to google specifically for this error and load balancing.
What we found out is that Reporting Services create some session to handle subsequent requests. Since we have cluster, those requests come from different servers. The problem though is that in our configuration requests came from different users, particulary
Our solution was simple, we configured our web site to run under dedicated user, the same for both instances.
Here are links that helped me:
http://social.technet.microsoft.com/Forums/en-US/sqlreportingservices/thread/1eb12568-bfea-4e4e-bd09-1f09b055c595
http://www.andypotts.com/Blog/2009/03/30/rsExecutionNotFoundWithReportViewerInALoadBalancedReportingServicesEnvironment.aspx
Here I will post problems I and my colleagues met and solutions we found.
Tuesday, June 29, 2010
Reporting Services and Web farm
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment