Unable to read data from the transport connection error

[jaineshpoojara]

Greetings Power BI Community,

I'm encountering a perplexing issue while loading web services from Business Central into Power BI. Specifically, when attempting to merge two web services and expand them within the same table, I'm consistently met with the following error:

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

Note: - "I have checked the Data types as well but that is not an issue"

Has anyone else encountered a similar roadblock when working with web services in Power BI? If so, I'd greatly appreciate any insights or solutions you've uncovered. Your assistance would be invaluable in overcoming this obstacle. I am attaching an image, hope that helps you understand the scenario better!!

Thank you sincerely for your time and consideration.

I've merged Invoice Line table into Invoice Header and while expanding it takes around 5-10 minutes time to load and then returns an error.

[JRALCON]

Its amazing how Microsoft forces you to use their solution and it just doesnt work.

[jaineshpoojara]

@Anonymous@lbendlin @Ashish_Mathur @amitchandak @Greg_Deckler  Thank you for the consideration!!

Can you please let me know the cause of this issue?
Is it a time out error that is caused due to large volume of data or something else?

[Anonymous]

Hi @jaineshpoojara ,

Some of these users seem to have solved the problem after deleting some tables to reduce calls to Business Central. You can try .

[jaineshpoojara]

@Anonymous I have tried the same!!

I have opened a new Power BI file and only transfromed 2 tables and when I tried merging it, the operation was successful.
But when I tried to apply the changes to move that one table into Power BI desktop, it showed me the same error.

                             

[jaineshpoojara · Accepted solution]

The solution which I have implmenented to complete all my reports was, I created "Query" instead of "Page" in Business Central and then I loaded all the queries in Power BI.

This helped me to complete all the process very smoothly. 

[PabloVR]

Answering just in case it helps somebody.

In my case, querying Business Central web services and then getting the error when having a few join or merge steps, buffering the tables before doing those costly steps helped being able to refresh the report in the desktop. The report wasn't failing in the Power BI Service.

2025 edit: after still getting the error, although less frequently, I might add that as somebody has mentioned before, setting the same datatypes for the columns involved in a join helps reducing the occurrence of the problem.

[Eduardo_Suela]

Exactly the same issue:

• read two fact tables from Business Central
• some operations: filters, column selections, replaces, calculations
• merge of those two tables
• group by

Fact tables are small (about 100k lines), so that shouldn't be the problem.

These operations make virtual memory grows as crazy.

A computer with 16GB can process it in desktop

A computer with 12GB cannot

Refreshes in service sometimes cannot do it

We have tried:

filters (short term solution. Next year the problem would be back)

buffers and stopfolding, some tiems work, sometiems don't

We need a solution for that

[Eduardo_Suela]

Finally I could make it work

We had to add Table.StopFolding every where

And now it works

It looks like some optimizations folded into the source system were unfeasible after the update 

[Anonymous]

Hi @jaineshpoojara ,

Regarding your question, after doing some searching on my part, this seems to be a problem that has been going on for several years. I can't seem to find a solution.

PowerBI Service error: OData: Unable to read data ... - Microsoft Fabric Community

If you have a Pro license you can open a Pro ticket at

Power Platform admin center (microsoft.com)