Forum Discussion
Unable to read data from the transport connection:
Hi
So aver the last two to three days I am having a varieity of issue with my Odata connection to CRM online. At first it was complaining with teh following error when trying to refresh the datasource:
"Data response result. Error: The property 'bizmap_businessid_businessunit' does not exist on type 'Microsoft.Crm.Sdk.Data.Services.BusinessUnit'." - So i assumed that a field that was part of a dataset had been changed, so i rebuilt the query in PowerBi Desktop (testing the refresh with no error" and republished.
Has the same issue again, which is odd as i tested the refresh on the desktop publisher with no errors.
Then forced a refresh again a few hours later and get a different error:
"Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host."
The odd thing is that this all worked fine for about 1 month up until 2 days ago.
Does anyone have any ideas.
Thank you in advance
21 Replies
I had this problem yesterday and this morning. My colleague found that changing the internet or wifi solved the issue for our case.
This worked for me! I would not have tried it if it wasn't because I've been having all other kinds of issues due to my connection. I switched from my 5G to normal wifi band and my dataset uploaded.
This also fixed the issue for me. I was connected via an ethernet cable, decided to switch to WiFi and the fix was instant. This fix makes no sense whatsoever given that the internet source is the same.
Power BI Desktop to the latest version and adjust parallel loading settings to prevent simultaneous execution of multiple queries, ensuring a successful report refresh. However, this may lead to a longer refresh time compared to parallel processing.
Hello guys, I recently encountered this error when I pulled data from Business Central and finally solved it so I want to share my solution for your reference.
I thought this error was caused by my data source at first. However, I was inspired by Jessica Wang's video https://www.youtube.com/watch?v=iVY1GkiYs-U and one reply in forum https://community.dynamics.com/forums/thread/details/?threadid=b6a8ffea-aaf1-4ece-a11e-1ecd8fa177ba
I converted the data type of whole numbers to text and then Power BI allows me to expand the merged tables, which is really simple and amazing. Hope this helps.
I'm getting the same error for the past two days even though mine was also working fine up to then.
Has your issue been resolved and how ?
I am facing same error and not getting a hint.
BR,
Achin
Hi there
No solution to this yet. This problem comes and goes. Which sadly impacts the business case to make it a permanent solution. I am not sure if it has to do with the fact that the feed timesout. It would be awesome if the feed would be more "real time" :)
Kind regads
Thank You for information !
I am also using CRM Online. Now I suspect, CRM online can also be possible suspect for problem.
Do we have setting where CRM online closes the connection ? I am not CRM online expert but do you have any idea
BR,
Achin
Hey, just wanted to add that we're getting this error as well. Are there any other logs we can check in PowerBI to get more of an idea of what's going on? If any find a solution can you pls post.
Thanks heaps.
Hi I'm also eager to read your blog posting to resolve this problem. Did your blog posting ever get approved or can we see the info on some other non MS approved blog ? Please do let us know.
Trying to resolve a Power BI desktop connection to Dynamics 365 online instance using:
let
Source = OData.Feed("https://DOMAIN.crm4.dynamics.com/XRMservices/2011/OrganizationData.svc"),
ContactSet_table = Source{[Name="ContactSet",Signature="table"]}[Data]Will be checking logs, fiddler etc....but still keen to read your blog.
Thks.
This issue happened with my while running several Dataflows from datasource folder in Onedrive or sharepoint, it kind of make sense that the source folder serve only one connection at a time, i resolved it by running schedual refresh time of my dataflow in a way that allow not more than two dataflow connections to hit the source folder at the same time, depends (offcourse on the datasize) leaving a reasonable gap to (30 Minutes) between every connection. it might not be a perfect solution but it gets the job done eventually 🙂
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.
This is what I found out about this issue:
Onedrive is a backup and sharing solution, and not a hot transfer node like Azure. The problem that happens is that when PowerBI requests files from Onedrive, it has to open a transfer session. OneDrive has limitations on those, because they weren't made for this purpose, hence the timeout errors.
Instead use azure hot containers, it's super cheap (I'm paying $3/month for around 25GB/day transfer) and does not cause errors because it is made for this purpose.
