RTI Dashboard Is Showing Errors on Visuals: "Unable to read data from the transport connection:"

[Kelderic]

I have an RTI Dashboard connected to an EventHouse. All of the visuals that are connected to one specific table are showing the same error, which is:

'Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..'

The DB shows no errors though and loads correctly:

Anyone know what might be happening? It was all working yesterday and no changes were made except for new data flowing in.

[V-yubandi-msft]

Hi @Kelderic ,

Just checking in has your issue been resolved, or are you still experiencing the error? If everything is working now, please mark the response as the accepted solution.
If you're still facing any issues, kindly share more details so we can assist you further.

Thank you.

[Kelderic]

Hey, sorry, I've been out on PTO. I just marked your first response as the solution.

[V-yubandi-msft]

Hi @Kelderic ,

Could you confirm if your issue has been resolved or if you're still facing challenges. If the solution worked for you, please consider marking it as the accepted solution so it can help other community members. If you're still experiencing issues, feel free to share the details.

Thank You.

[V-yubandi-msft · Accepted solution]

Hi @Kelderic ,

Thanks for posting your query in the Microsoft Fabric Community.  Please review the query duration and row limits in your visuals. Limit the number of returned records, use top, or restrict the date range to see if it stabilizes. Consult your network admin to check recent changes to firewall/proxy settings, particularly outbound TCP connections or SSL inspection. 

Restart the Power BI dataset refresh or the underlying compute container if possible, and verify if throttling or API limits were reached. Check if the new data contains any anomalies, such as very large rows, unexpected nulls, or corrupted types. Run the same query used by one visual directly in Kusto Explorer or Data Explorer to confirm.

Additionally, follow these debugging steps: convert one visual to a table in Power BI and run step-by-step to locate the issue. Disable visuals one by one to determine if it’s tied to a specific column or expression. Copy the query behind a failing visual and run it in Kusto Web Explorer or the Azure Data Explorer UI to validate whether the issue replicates outside the dashboard.

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.