Forum Discussion
PowerBI Service error: OData: Unable to read data from the transport connection:
Why do you think that helped? Kurbis?
I work for an MS partner. For the last 8 weeks, and for other 4-8 week periods throughout the past 3 years, we have MANY customers at once all experiencing this issue. They have power query steps both simple and complex.
some make some adjustments like you have. Others can't and just suffer... and then magically, after several weeks, having done nothing to fix the issue, their queries finishe successfully again just like they had before the problem period. (During the problem period they will fail anywhere from 50-100% of the time varying by client. ... but some do experience some success in having their data returned.)
We are about at the end of the "fall equinox 2023 power query sucks cycle". Most of our clients are working again. None having done anything significant or material to their power query steps.
what was your data source? All the clients I am speaking on behalf of are using Microsoft business central.
the cycle seems to repeat itself just before business central releases new waves. (Mid September and mid March).. but I know there are several Microsoft technologies that use the same 2x annual release cycle. So may be more tied to that than BC releases.
if your data source is outside of Microsoft then this ruins all my hair brained theories.
Why do I think it helped? Because it did (for me anyway). With a merge I get the error, without I don't.
Do I think it's ideal? Absolutely not. The error occurred a couple of weeks ago, hence might be with the September update. Of course it is annoying, didn't know though that that's a Microsoft thing.
And yes, BC is my data source
thank you for sharing your experiences. I've been dealing with this on/off for 3+ years. And I just can't make rhyme or reason to anything. I have read that merges and other similar power query steps can cause some problems; exactly what you experienced. But why a "read data" problem? and who is the "remote host" forcibly closing the connection? And why does rewriting your power query steps (after the data has been retrieved into PowerQuery) influence anything?
Microsoft support has been, unfortunately, incapable of performing their stated duties. I was able to produce fiddler logs for some clients when this happened 12 or 18 months ago. But nothing ever came of it. Now the oddest thing about it is that today (Nov 5) all but 2 of our clients are back to normal. No material change in their query steps pre-September to now. They just suffered through it for 8 weeks. But the 2 that aren't back to normal have this experience now:- they turn on fiddler to hopefully catch the https webservice calls in the act to see which is/are failing and why? and it the data returns to excel just fine; no remote host forcibly closing any connections.
- so we think, YES!, they're through the quagmire and back to normal ... but NO!, they turn off fiddler and the errors resurface.
Well I guess we wait until March 2024 and try to get support's attention again ...Has there been any progress on this issue? Just started happening to me last week.
My data source is Business Central of course.
Answering just in case it helps somebody with the same problems querying Business Central.
Buffering the tables before doing those costly steps (Merges, Joins) 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.
