Press "Enter" to skip to content

Month: February 2018

SQL Server Reporting Services Timeout

The other day we ran in to an issue where the report was running 30 minutes, this may be the only report that we have that runs this long, but then it fails. The only error message was “Report processing has been canceled by the user. (rsProcessingAborted), but after checking, no one canceled the report processing. What just happened?

It was determined that the Report timeout option was set to “Use the default setting” like most of our reports are.


Well, where is this default setting and what is it set to? The default settings timeout is set in the site settings page of your SQL Services Reporting Services and it was set to 1800 seconds or as you guessed, 30 minutes.


You have two options to fix the the timeout issue.

1. Change the default settings timeout for the whole site in the site settings page.

2. Change the Report timeout setting just for that report. This is done by going to the report, clicking the … and choosing manage.

You then scroll down to Advanced and either choose “Allow the report to run for (add amount of seconds here) seconds before timing out” and changing the seconds to a higher value that will allow the report to run or choose the “Allow the report to run indefinitely (no timeout)” option.


Click Apply and your report should not complete.




Leave a Comment

FindTime for meetings

I received an email today from FindTime Notifications. If you haven’t heard of this Outlook add-in, it’s a pretty cool addition from Microsoft, that allows you to ask people outside of your company to vote on times that they would be available to meet. You can mark a time slot as preferred, yes, or no. You can also suggest other time slots. Next time you need to schedule a meeting, take a look at







Leave a Comment

Using alias to upgrade old servers

One trick that I have used numerous times and really like is to use a server alias when moving to new servers. For instance, we were moving numerous databases from a 2000 server named serversql0001. Since this server was so old, we had no real idea how many places or connections people may have used the alias, so we decided during the downtime to remove this alias and point it to the new server that we were moving the databases to. After we brought the new server up, we checked some of the software that was connecting to the databases, and as expected, everything was fine, with no need for connection changes.

Leave a Comment