Wednesday, August 03, 2011 7:55 PM
I spent all day struggling with the above error that poped up on report generation. In the end I found the problem and since I haven't seen this specific issue documented anywhere I figured I share it. This is a new envoronment setup with seperate servers for SSRS and MS SQL. The SSRS logfile complained about "Expired Session" each time. The problem was when the servers were setup they were set to different time zones! The report server (set to Pacific) saw all of the session in the MS SQL Server (Eastern) as expired.
I hope this info saves somebody a great deal of time.
Friday, August 05, 2011 7:54 AMModerator
Thanks for your post and generous sharing.
A report execution time-out value is the maximum number of seconds that report processing can continue before it is stopped. This value is defined at the system level. The report server evaluates the executing time involves both the time caching data into Reportserver database and expression calculating, so you should assure both your database and report server specified in the same time zone, otherwise once the time contrast between them exceeds the execution time-out value, the report execution expired error will always occurs.
More information about Setting Time-out Values for Report Execution, please refer to the blow link:
If you have anything unclear, please feel free to let me know.
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
- Marked As Answer by Eileen ZhaoMicrosoft Contingent Staff, Moderator Friday, August 12, 2011 10:03 AM
Friday, August 24, 2012 1:06 PMThanks to both of you I found the referenced link helpful.
Monday, November 19, 2012 10:03 PM
Interesting, I had the error on one of my SSRS reports, even after checking that the server and workstation clocks were in the same time zone. I eventually found that the report worked with no problem when I reverted back to 32-bit IE9. The error was happening with 64-bit IE9, 9.0.8112.16421CO.