Wednesday, September 22, 2010 6:52 PM
I am doing performance analysis for SSRS 2008 report server and running various reports that return different no. of records. When I run reports ranging from 25 K records to 1 million records, I am getting the reports successfully.
BUT when I am running a huge SSRS 2008 report (that returns 2 million records) and it gets rendered few times and sometimes it gives me an error,
"The report execution <some string> has expired or cannot be found. (rsExecutionNotFound)”.
After reading many forums I tried setting CleanupCycleMinutes to 30 in the report server config file but it didn't help either.
When I see SQL Server log after this issue comes I see following message there;
"A significant part of sql server memory has been paged out. This may result in performance degradation. Duration: 300 seconds. Working set(KB): 97672, memory utilization 42%"
I have also enabled the lock pages in memory option but it is also not resolving the issue and page out is still happening.
I am using SSRS 2008 64 bit, Win Server 2003 64 bit. RAM is 8GB.
Please help me to know what are these issue, are these two issues related and how to fix it?
Tuesday, September 28, 2010 10:06 PM
I figured out that the above two issues are different.
Probably, the execution not found error comes when the session is cleaned up from the sessiondata table of rs tempdb database while the report is still in execution phase.
Following links provide this information which I could relate to my issue.
However, as mentioned in the second link, the value of cleanupcycleminutes property of the rs config file can be increased to avoid frequent session cleanup (by default it is set up to 10 minutes), I see that the sessions still persist in the sessiondata table in rs tempdb database for much more time and I do not have any control on this session data even after adjusting the value of cleanupcycle minutes in the config file.
More comments on this are welcome.
- Marked As Answer by Challen FuModerator Monday, October 11, 2010 2:21 AM
Monday, May 16, 2011 8:46 PM
Changing the following Report Server (SSRS 2008) setting will fix the issue:
1. On the server, edit C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer\rsreportserver.config
2. Set <EnableAuthPersistence> in rsreportserver.config to False: