SSRS render timedout RRS feed

  • Question

  • Hi All,

    I am running multiple(40) reports at a same time and all the reports are success if my database is very small (1gb). Currently my database size is 40 GB. Now if I ran all those reports again then most of the report is not generating the output (pdf). I am getting "The Operation has timed out error" in ReportExecutionService.Render().

    But when I check the ExecutionLog2 and ExecutionLogStorage tables of Reportserver, it shows all the report executed successfully. (Status=rsSuccess).

    I have below setting in the ReportServer.config

    <Add Key="SecureConnectionLevel" Value="0"/>
    <Add Key="CleanupCycleMinutes" Value="10000"/>
    <Add Key="MaxActiveReqForOneUser" Value="200"/>
    <Add Key="DatabaseQueryTimeout" Value="0"/>
    <Add Key="RunningRequestsScavengerCycle" Value="6000"/>
    <Add Key="RunningRequestsDbCycle" Value="6000"/>
    <Add Key="RunningRequestsAge" Value="30"/>
    <Add Key="MaxScheduleWait" Value="5"/>
    <Add Key="DisplayErrorLink" Value="true"/>
    <Add Key="WebServiceUseFileShareStorage" Value="false"/>

    Also I am setting the timeout as 1800000 for the Render method.

    Please do let me know if anyone has idea on this.

    Thanks in advance.

    Best Regards


    Tuesday, January 21, 2014 9:31 AM

All replies

  • Try :

    Tuesday, January 21, 2014 9:44 AM
  • There are a number of timeouts in SSRS; session timeout, report execution timeouts, http request timeouts.  A session timeout in SSRS is not the same as a session timeout in ASP.NET.  I don't have the answer to your question, but i do have some articles that can help you understand the timeouts and hopefully lead you down the path of discovery.

    This articles is a good article as it discusses the session timeout and the keep alive that is sent from the report viewer.

    This article is good as well in describing some of the timeouts.

    Based on what you are describing you have a couple of options.  Tuning your queries or the DB to be more efficient in pulling the data or adjusting the report execution timeout at the system or report level.

    Tuesday, January 21, 2014 2:33 PM
  • Hi Muthuraja,

    Did you have try to use above solution to troubleshooting the issue? If the issue is persist, we can try to modify the httpRuntime executionTimeout property to resolve the issue.

    In SSRS web.config file, it has httpRuntime executionTimeout property. By default, the value is 9000. We can increase it by providing a big value.

    By default, in SSRS 2012, the file is located in: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportManager
    1. Open the web.config with TextEditor(e.g. Notepad)
    2. Modify the executionTimeout. NOTE: If this settings does not exist the web.config, please add it under the System.Web element.
    3. Use the same method to modify the web.config file in ReportServer.

    There is an article about ExecutionLog2 View - Analyzing and Optimizing Reports, you can refer to it.

    Alisa Tang

    If you have any feedback on our support, please click here.

    Alisa Tang
    TechNet Community Support

    Tuesday, January 28, 2014 5:23 AM
  • Hi Alisa Tang,

    I have tried all the settings specified in this post but nothing seems to be Working. I have opened an support call with Microsoft on this and I will post the findings.

    Thank you very much for your time on this.

    Best Regards


    Wednesday, January 29, 2014 3:15 PM
  • Hi Muthuraja,

    Did you get any solutions from microsoft?



    Friday, December 13, 2019 7:33 PM
  • Hi, 

    No, I didn't get any solution from Microsoft support. The workaround is , not to schedule all the reports at the same time. 

    Best regards,


    Sunday, December 15, 2019 7:07 AM
  • Did the reports work before?

    Is there any blocking in the Database?

    Does it work when you run just one report?

    • Edited by SuperDaniel Sunday, December 15, 2019 2:31 PM
    Sunday, December 15, 2019 2:30 PM