Reporting API
1 TopicSSRS Report Rendering Issues via ReportExecution2005 API
Hello everyone, We are encountering intermittent issues while requesting PDF renders of large SSRS reports from our SSRS server using the ReportExecution2005 API from a .NET 6 backend. While this generally works, we occasionally run into unexplained failures. For example, we have a report with approximately 47,000 pages. Every time we attempt to generate this report, the process fails after about 17.5 minutes. Examining the ExecutionLog and our own logs, we can confirm that: The data query executes successfully Report processing completes without errors The rendering process runs for a few minutes before the SSRS service throws an error, terminating the connection with our backend The ReportingService log file contains the following error: System.Threading.ThreadAbortException: Thread was being aborted. Additionally, ExecutionLog3 lists the status as: rsInternalError Since this issue consistently occurs around the 17.5-minute mark, we initially suspected a timeout and increased all possible timeout values. However, this had no effect. Interestingly, when we restart the SSRS service, the PDF sometimes renders successfully, taking about 40 minutes to complete. After that, all subsequent requests again fail with the same error. This raises a few questions: If the report sometimes completes successfully, can we rule out a timeout issue? Memory usage remains well below the configured limits, and we can manually request and render multiple large reports simultaneously without issue. Is there any known SSRS behavior that could cause this repeated failure over time? As a temporary workaround, we’ve set up subscriptions to trigger SSRS to render the PDF independently, but we would prefer to resolve the API issue so we can use our direct request approach. Has anyone encountered a similar issue or have insights into what might be happening? Thanks in advance!88Views0likes0Comments