My question is in regards to how timeouts work in SSRS 2008 R2. The question led me to discover a good number of timeouts in SSRS, which in turn led me to researching blogs, MSDN, forums, etc. I fount John Gallardo's blog post very helpful (http://blogs.msdn.com/b/jgalla/archive/2006/10/11/session-timeout-during-execution.aspx).
My question really comes down to, do the same principles apply in SSRS 2008 R2? This is my perceived perception of how things work and need some guidance and/or correction on my assumptions:
My understanding is when a user clicks to execute a report, this is point the "session timeout" timer starts, but the ping from report viewer is blocked as the session is locked during report execution. Being that there is a "report execution timeout" I would assume that this timer begins at the same time as the session timeout. What's interesting is that by default the session timeout is 10 minutes, where as the report execution timeout is 30 minutes. It would appear that even if your report executes within the 30 minutes (say in 15 minutes) the session would have timed out and you would be left with a wonderful "Execution '<some GUID>' cannot be found (rsExecutionNotFound)" error.
To me it would appear that the real timeout in which the report will render or not is controlled by the session timeout. Is that correct?
I was also under the impression that should you need to adjust the session timeout it could now be done by navigating to SSMS > Right-Click the SSRS Instance > select Properties > click Advanced (from the list on the left) and adjusting the Session Timeout (Found under the “Other” section).
John's blog post suggests another way to do this, but my question would be does this still apply with SSRS 2008 R2?