RS 2008R2 , randomly users getting this error after some retry all run ok again when using verbose loggings can see 09:24:05:: v VERBOSE: writting session cookie: ekkrjbubp00t5wzc3rzspvzb 09:24:05:: v VERBOSE: Saved report snapshot to session in a background thread <for same session id> .. 09:34:49:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: , An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.; 09:34:49:: e ERROR: Error in getting session data: Expired Session: ekkrjbubp00t5wzc3rzspvzb 09:34:49:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ExecutionNotFoundException: , Microsoft.ReportingServices.Diagnostics.Utilities.ExecutionNotFoundException: The report execution ekkrjbubp00t5wzc3rzspvzb has expired or cannot be found so was looking in the 10min between this errors and saw 09:28:53:: i INFO: Cleaned 0 batch records, 0 policies, 3 sessions, 0 cache entries, 4 snapshots, 43 chunks, 0 running jobs, 0 persisted streams, 32 segments, 32 segment mappings, 0 edit sessions. so im suspecting the cleanupcycle removed the session in RSReportServer.config we have this parameter : CleanupCycleMinutes Specifies the number of minutes after which old sessions and expired snapshots are removed from the report server databases. Valid values range from 0 to maximum integer. The default is 10. Setting the value to 0 disables the database clean up the process. so now was looking into why the session considered as expired , due to the fact it said it is saving it as cookie was looking up if there is timout on this . On RSReportDesigner.config I found SessionTimeoutMinutes Specifies the period for which a session cookie is valid. The default is 3 minutes. any here had similer issue ? cant find info about this on the web SessionTimeoutMinutes param is on RSReportDesigner that means we need to do the changes on it and then redploy the report into the report server for any changes to take effect ? -

Hi nadavh, Thanks for the question. Based on my research, I would suggest you check the problem from below two approaches. >>1. The database and report server specified in different time zone. Please refer to this similar thread: http://social.technet.microsoft.com/Forums/en-US/sqlreportingservices/thread/03ae7250-0c93-41c8-8392-39e8dbc25f2f >>2. The session is cleaned up from the sessionedata table of rs tempdb database. Two similar threads: http://social.technet.microsoft.com/Forums/en-US/sqlreportingservices/thread/a7239ad9-1209-4af3-912d-e69a406663a8 http://social.technet.microsoft.com/Forums/en-US/sqlreportingservices/thread/4412ef63-1a46-4ee4-9aed-cdc722d2179c Thanks, Sharp Wang TechNet Subscriber Support in forum If you have any feedback on our support, please contact us. Please remember to mark the replies as answers if they help you and unmark them if they provide no help.

tnx for feedback RS and SQL are on same time zone (running on same server ) . regarding <EnableAuthPersistence>False</EnableAuthPersistence> saw on http://connect.microsoft.com/SQLServer/feedback/details/525649/ssrs-2008-execution-session-id-cannot-be-found-rsexecutionnotfound that peaple reported this worked as workaround , for now im trying to change SessionTimeoutMinutes and checkup if it helps will try EnableAuthPersistence=False if that will not help . coudnt figur out if the report is taking the RSReportDesigner.config parameters on render time or all the parameters there are inserted into the report on deploy time only. -