Small and medium business | Business Central, N...

Getting Web Services OData Error - "An existing connection was forcibly closed by the remote host"

(2) Share

Report

Posted on by Agazziz

203

I use Power Query in Excel to connect with Business Central data using OData V4 Web Services links. However, ever since our environment upgraded to version 18 of Dynamics 365 Business Central, I get the following error message in Excel when trying to refresh these queries (they all worked great before the BC update):

"[DataSource.Error] OData: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host."

Whether I'm pulling data from Pages or Queries, it doesn't matter. And what's also odd is, I can get the data to load if the queries are simple. But when I merge data from two or more OData links, I get the error. Again, all these Power Queries worked before our environment of Dynamics 365 Business Central upgraded to V18. Could there be a setting that limits data? Maybe it's timing out? Any help would be greatly appreciated.

I have the same question (0)

All responses (10)

Answers (0)

Suggested answer

Khushbu Rajvi. 19,085 Super User 2025 Season 2 on at

Like (0)

Report

Getting Web Services OData Error - "An existing connection was forcibly closed by the remote host"

Hope this helps as weellhttps://community.powerbi.com/t5/Power-Query/oData-connection-to-Business-Central-on-prem-forcibly-closed-by/td-p/2882266

https://community.fabric.microsoft.com/t5/Service/PowerBI-Service-error-OData-Unable-to-read-data-from-the/m-p/2528045

Was this reply helpful? Yes No
Suggested answer

JA-02040828-0 4 on at

Like (0)

Report

Getting Web Services OData Error - "An existing connection was forcibly closed by the remote host"

Its just how it is, you cannot do any reporting because of this, you are forced to use a tool that doesn't work. Thank you Microsoft.

Was this reply helpful? Yes No
Gerardo Rentería Ga... 23,139 Most Valuable Professional on at

Like (2)

Report

Getting Web Services OData Error - "An existing connection was forcibly closed by the remote host"

Hi, good day
I hope this can help you, and give you some hints.

Solved: oData connection to Business Central (on prem) - f... - Microsoft Fabric Community

Best Regards
Gerardo

Was this reply helpful? Yes No
JA-02040828-0 4 on at

Like (0)

Report

Getting Web Services OData Error - "An existing connection was forcibly closed by the remote host"

4 Years later, Microsoft still does nothing.

Was this reply helpful? Yes No
Suggested answer

JodeRuiter 980 User Group Leader on at

Like (1)

Report

RE: Getting Web Services OData Error - "An existing connection was forcibly closed by the remote host"

In my case, it was during the joining of two other queries, and I found that I was trying to link up on disparate data types, so though they were the same data, one query had the column in Text, the other query had the same field in whole numbers.

All I had to do was change the type of the whole number column to text and then it worked like a charm.

Was this reply helpful? Yes No
Clinton Saunders 22 on at

Like (1)

Report

RE: Getting Web Services OData Error - "An existing connection was forcibly closed by the remote host"

We have just upgraded out client from BC 14 to BC 20, and we are encountering the same issue. In our case, the data can refresh in some companies, but not in the larger ones. WE have an On-Premise implementation. Nothing logged in the Event Logs to give clues! Can't believe there is not a solution for this yet!

This is not good for BC

Was this reply helpful? Yes No
Stirton 24 on at

Like (1)

Report

RE: Getting Web Services OData Error - "An existing connection was forcibly closed by the remote host"

Yea i have been filtering my Odata queries to only take required data but still the final query to Append my 3 queries falls over with the error above, this is a real pain!

Let me know if you find a solution and i will do likewise.

Was this reply helpful? Yes No
Agazziz 203 on at

Like (1)

Report

RE: Getting Web Services OData Error - "An existing connection was forcibly closed by the remote host"

Not solved yet. Our Microsoft Partner has been working with Microsoft on this, but they haven't found a solution. The only thing I've found that has helped is to add OData filters to my queries when possible to limit the amount of data being pulled into the query - this has worked for most, but not all, of my BC OData queries.

There is also 3rd party solutions that can use the OData links to replicate the data onto a SQL server, making the data much quicker/easier to query. Plus, this gives people that don't have BC licenses the ability to refresh queries using Business Central data.

Was this reply helpful? Yes No
Stirton 24 on at

Like (1)

Report

RE: Getting Web Services OData Error - "An existing connection was forcibly closed by the remote host"

I have the a similar issue, did you solve this?

I can load individual BC queries fine but when i append them together the query falls over with the same error message "[DataSource.Error] OData: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host."

Was this reply helpful? Yes No
Suggested answer

srttel on at

Like (1)

Report

RE: Getting Web Services OData Error - "An existing connection was forcibly closed by the remote host"

Hi,

I recommend contacting your CSP or Microsoft support providing the repro scenario which can be used on a demo sandbox, so they verify the underlying issue within the telemetry data and potentially investigate into a fix or workaround.

Was this reply helpful? Yes No