Error: "Unable to read data from the transport connection" - Help with troubleshooting OData connection issue

[ctt]

I’m encountering an issue when trying to refresh data in Power BI from an OData feed. I get the following error message:

Data Source Error:
OData:
Unable to read data from the transport connection:
An existing connection was forcibly closed by the remote host.
RootActivityId = 138bc000-63a6-448a-ab57-56ba3ed3f545.
Param1 = DataSource.
Error:
OData:
Unable to read data from the transport connection:
An existing connection was forcibly closed by the remote host.
Request ID: e9abbf3d-cc22-90b4-1f58-ef55449f1c39.

This happens when I try to refresh my Power BI report using data from an Exact Online API-endpoint.

• I’ve ensured that my OData.Feed connection has a sufficiently high timeout value.
• The dataset was large, but I reduced it to the past year’s data, and it was working fine until recently.
• The issue persists whether I refresh manually using Power BI Desktop or automatically through the Power BI Service.

Has anyone experienced this error before, and do you have any suggestions on how to troubleshoot or resolve it? Could this be related to any recent changes in the Exact Online API, or is it more likely a connection issue on my end?

Any advice would be greatly appreciated!

Bridge Online shot of request 0HNBRR6QI1AU8:00000003:

[forums]

It concerns a Visma.net datasource for retrieval of the general ledger journal entry lines.

Approximately 284.000 rows have been retrieved, with the last row returned a few seconds before the download was canceled.

According to Invantive Cloud, the download was cancelled client side.

A deeper analysis was made to establish the cause. According to the logging, the client went away. This is typically a powerbi.com issue.

Strange is that the same problem happens with Microsoft Power BI Desktop.

It is recommended to try the download again at most 3 times.

In case that fails, please try the download using curl from the Windows command prompt:

curl --user john.doe@acme.com:secret --output somefilename.json https://...

where the user, password and URL are replaced by the Cloud user name, password and the path from the screenshot (“Sti”).

In case it still fails with such an error, please leave a reply. Through delegation access will be requested then to further analyze the issue.

[forums]

This question was automatically closed after at least 1 week of inactivity after a possible solution was provided. The last answer given has been marked as a solution.

Please ask a new question via a separate topic if the problem occurs again. Please include a link to this topic in the new question by pasting its URL into the text.