SQL Reporting 10 Minute Timeout

We recently ran into a situation where a long-running SQL report in a web application was timing out after 10 minutes.

It turns out there are A LOT of places that this timeout could be coming from:

- Your own .net web application session state

- Your application's explicit report timeout if specified in your code

- SQL Reporting Services's webservice session state

- SQL Reporting Services system properties has a default timeout (which happened to be the culprit in our case)

Thanks to John Gallardo, the solution was found here:

http://blogs.msdn.com/jgalla/archive/2006/10/11/session-timeout-during-execution.aspx

The following is copied from John's blog...

We replaced the
timeout with 3600 to ensure long running reports could execute for an hour.

Copy the following and save it as
sessionTimeout.rss

Public
Sub Main()
Dim props() as [Property] 
props = new [Property] () { new [Property](), new [Property]() }

props(0).Name = "SessionTimeout"
props(0).Value = timeout 

props(1).Name = "SessionAccessTimeout"
props(1).Value = timeout 

rs.SetSystemProperties(props)
End Sub

Then, you can run this script with the following command:

rs -i sessionTimeout.rss -s http://localhost/reportserver -v timeout="6000"

IMPORTANT: RESTART SQL REPORTING SERVICES AFTER YOU RUN THIS SCRIPT TO HAVE THE SETTING TAKE EFFECT.

SQL Reporting Services - 401 Error & rsLogonFailed

We've been using SQL Reporting for awhile now.
Accessing the reports was done by going to http://localhost/ReportServer/

I recently wanted to delete an existing report and to do that needed to access the report server management at http://localhost/Reports/
At this point I was getting a 401 error and could not access the control panel.

This was resolved by adding a registry key to disable a loopback security check that had been implement by a Windows Server Service Pack.
Step by step instructions to fix this issue are available here:
http://aspadvice.com/blogs/ssmith/archive/2007/02/09/SQL-Reporting-Services-401-Error.aspx

One of my earlier troubleshooting steps had been to use Reporting Configuration Manager to update the Unattended Execution Account.
I entered a user with a high level access.  That didn't do anything to fix by 401 issue (eventually solved using the instructions above).  But I never went back to remove the service execution account.

Going back to run the reports that had previously been running fine, I was now getting this error...

Logon failed. (rsLogonFailed) Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)

Other solutions offered that the username / account I was using to run the reports was wrong.  However, these reports had been working fine prior to me fiddling that unattended execution account.

I got my rsLogonFailed issue resolved by completely disabling the Execution Account.  This was fine for the reports that we need to run.

Blogged with the Flock Browser