I’ve recently been battling long running reports and how to make certain they do not timeout on the SharePoint servers.
There are several levels in SharePoint 2010 that a report can time out. I will discuss the top three that I have encountered and what I had to do to fix them.
The first one, and the easiest to fix, is within the SSRS report that is housed on your SharePoint site. This fixed about 75% of my problem with time-out issues.
- Go to the library where the report is stored and click the dropdown menu that appears when you hover of the report.
- Select Manage Processing Options.
- Under the Processing Time-out section, select Do not limit report processing time-out.
The next option is a bit more involved:
- On each Web Front End (WFE) server, you will need to edit the web.config file of the SharePoint web application. To fine the for the default web application, the web.config file is located in C:\inetpub\wwwroot\wss\VirtualDirectories\80. If you are unsure of the port number, check in Central Administration under Manage Web Applications.
- I use Notepad++ to edit the web.config files as it is easy to find what you are looking for with the line numbers it provieds. Find the httpRuntime element and modify the executionTimeout setting. The default value is set to 110 seconds.
<httpRuntime maxRequestLength=”51200″ executionTimeout=”1000″/>
- Save your web.config file. There is no need to perform an iisreset as the ASP.NET process will apply the settings to your changes.
The final option that I use is when I had a timeout problem between the report server and my web front end. Of course, there weren’t any error messages that TOLD me that there was a timeout issue. I had to figure that little tidbit of information out for myself. If the SQL query runs too long on your SQL server, the report server will wait until it completes. Unfortunately, your WFE may not be as patient and time out in the meantime. The indicator for this problem was that we could run the report directly from the RDL report file and it would eventually complete. When teh report was displaying in the web part, it would time out. Here is how to remedy this:
Edit your Master Page:
1. Open the site/sub site where your master page is located in SharePoint Designer.
2. In the left navigation pane, click the Master Pages section.
3. Right-click the master page that site uses and click Edit File in Advanced Mode.
4. Locate the ScriptManager element and add an AsyncPostBackTimeout element, as you will find below:
<asp:ScriptManager id=”ScriptManager” runat=”server” enablepagemethods=”false” enablepartialrendering=”true” enablescriptglobalization=”false” enablescriptlocalization=”true” AsyncPostBackTimeout=”0″/>
5. Save the master page, check it in, and approve it (if you use the SharePoint publishing features).
This will resolve your issue if it is resulting from this variation of a timeout.
Please let me know if you have any questions, or if there are any pieces that you think I should add to this post. There are many things that can timeout your reports. These are just a few of the fixes that have worked for me.