Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Hi All,
Currently we use PowerBI Report server 2014 with sqlserver 2014 SP2-CU5 . we found issue PowerBI report cannot render any report and we found a lot of error "rsHttpRuntimeClientDisconnectionError" .
Actually We have application call 2-3 reports and application reduce timeout (in apps) before a lot of error happen so now application rollback timeout config to original value which help"rsHttpRuntimeClientDisconnectionError" gone. So I curious that why when PowerBI Report server have a lot of rsHttpRuntimeClientDisconnectionError error ,it impacts all reports cannot open . Do you have idea? or any configuration should be adjust in PowerBI Report server ?
thank you,
Peach
Solved! Go to Solution.
Hi @peacherry ,
Please check if this could help you:
Hi RudyCat,
Based on my research, the rsHttpRuntimeClientDisconnectionError error may occur if:
1. Reporting Services creates the report and then goes to send it back to the client.
2. Reporting Services finds out that the connection has been closed and responds with the disconnection error.
To resolve the issue, we can try to modify the TCP profile applied to the VIP.
Additionally, the issue may also occur due to a RESET coming from something between Report Server and the custom application. For example, an F5 NLB times these connections out on the either an HTTP or TCP level.
Hope this helps.
Regards,
Mike Yin
Reference: rsHttpRuntimeClientDisconnectionError - SQL 2008 R2
Best regards
Icey
If this post helps, then consider Accepting it as the solution to help other members find it faster.
Hi @peacherry ,
Please check if this could help you:
Hi RudyCat,
Based on my research, the rsHttpRuntimeClientDisconnectionError error may occur if:
1. Reporting Services creates the report and then goes to send it back to the client.
2. Reporting Services finds out that the connection has been closed and responds with the disconnection error.
To resolve the issue, we can try to modify the TCP profile applied to the VIP.
Additionally, the issue may also occur due to a RESET coming from something between Report Server and the custom application. For example, an F5 NLB times these connections out on the either an HTTP or TCP level.
Hope this helps.
Regards,
Mike Yin
Reference: rsHttpRuntimeClientDisconnectionError - SQL 2008 R2
Best regards
Icey
If this post helps, then consider Accepting it as the solution to help other members find it faster.
User | Count |
---|---|
3 | |
3 | |
2 | |
2 | |
2 |
User | Count |
---|---|
4 | |
4 | |
3 | |
3 | |
2 |