Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount.
Register nowHi Team,
I need help with new SSRS version Version16.0.8969.32906 we installed on our new server. At exactly 4PM there are lot of connections made and
there are multiple errors ocurred
e ERROR: Failed in BaseWorkerRequest::SendHttpResponse(bool), exception=System.Runtime.InteropServices.COMException (0x800703E3): The I/O operation has been aborted because of either a thread exit or an application request. (Exception from HRESULT: 0x800703E3)
at Microsoft.ReportingServices.HostingInterfaces.IRsHttpPipeline.SendEntityBody(Void* chunks, UInt16 chunkCount, Boolean finalWrite, Boolean closeConn)
at ReportingServicesHttpRuntime.BaseWorkerRequest.SendHttpResponse(Boolean finalFlush)
library!ReportServer_0-11!50f8!02/17/2025-16:35:58:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: RsWorkerRequest::FlushResponse., Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: An internal or system error occurred in the HTTP Runtime object for application domain ReportServer_SSRS_0-11-133842388366968385. ---> System.Runtime.InteropServices.COMException: The I/O operation has been aborted because of either a thread exit or an application request. (Exception from HRESULT: 0x800703E3)
at ReportingServicesHttpRuntime.BaseWorkerRequest.SendHttpResponse(Boolean finalFlush)
at ReportingServicesHttpRuntime.RsWorkerRequest.FlushResponse(Boolean finalFlush)
--- End of inner exception stack trace ---;
webserver!ReportServer_0-11!50f8!02/17/2025-16:35:58:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: An internal or system error occurred in the HTTP Runtime object for application domain ReportServer_SSRS_0-11-133842388366968385. ---> System.Runtime.InteropServices.COMException: The I/O operation has been aborted because of either a thread exit or an application request. (Exception from HRESULT: 0x800703E3)
webserver!ReportServer_0-11!50f8!02/17/2025-16:35:58:: e ERROR: RS.Server.HttpHandlerError {"shortHttpDescription":"Reporting Services Error","code":"500","path":"reportServiceHandlerWriteError","exceptionType":"Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException"}
library!ReportServer_0-11!9648!02/17/2025-16:49:00:: w WARN: Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'ODS_CAA2'. ---> System.InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
Hi @PK_2020234
The errors you are encountering in SSRS Version 16.0.8969.32906 on your new server indicate a combination of HTTP runtime issues and database connection timeouts, likely due to high concurrent usage at 4 PM. The System.Runtime.InteropServices.COMException (0x800703E3) error suggests that SSRS is experiencing an issue with processing HTTP responses, possibly due to resource exhaustion or IIS-related settings. Additionally, the Timeout expired error while connecting to the ODS_CAA2 data source indicates that the connection pool is reaching its maximum limit, preventing new connections from being established. To resolve these issues, consider increasing the connection pool size in the data source settings, optimizing the execution schedules of reports to reduce peak load, and reviewing IIS and SSRS memory limits. Also, check for long-running queries that might be holding connections open and configure database indexing or query tuning to improve performance. Monitoring server resource usage (CPU, memory, and network activity) around 4 PM could provide further insights into what is causing the spike in connections. Let me know if you need help with specific troubleshooting steps or configurations!
Hi,@PK_2020234.I am glad to help you.
Even though I'm not very good at properly configuring SSRS connection pooling, I wanted to give you some help.
Based on your provided error message. The error message says:
Connection pool timeout, HTTP response error.
This could be caused by your connection pooling being configured incorrectly.
Have you tried
Increasing the connection pool size and setting a time limit for connection timeouts
Ensuring that all database connections are properly closed after use (a point emphasized in the documentation)
URL:
SQL Server Connection Pooling - ADO.NET | Microsoft Learn
Understanding SQL Server Connection Pooling in ADO.NET - MSSQLTips.com
SQL Server LOCAL Connection: Troubleshooting localhost vs. LOCAL
You need to work with your development team.
I noticed that there is a newer version of the update, have you tried the new version?
URL:
Release notes for Reporting Services 2017 and later - SQL Server Reporting Services (SSRS) | Microso...
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Check out the February 2025 Power BI update to learn about new features.
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
User | Count |
---|---|
8 | |
3 | |
2 | |
2 | |
2 |
User | Count |
---|---|
15 | |
10 | |
6 | |
4 | |
4 |