March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Hi,
Since yesterday I have this message error when I refresh the report in Power BI Desktop, it never happened to me, and I'm not able to find any information of this error in the web
It happened instantly, and also I'm able to do query's in SSMS, basically doing the query in SQL I got returned the whole table without any problem, so basically now I don't have any clue about where this issue is coming from,
So I guess that this error comes from Power BI but I can't find solutions anywhere,
Hope this message helps,
Solved! Go to Solution.
Hey Guys,
I resolved the problem reseting all the data source connections and cleaning the cache of the report,
Hope this helps to you in the future,
Regards to all
Angelvelz90p@gmail.com
Has anyone solved this for Power BI Online? Our Desktop version refreshes fine but when we try to refresh online with on-prem gateway for multiple EXCEL file source, we are getting following error:
The file that fails is different every time so I feel it is a timing issue where more than one file is trying to refresh data at once and EXCEL locks up.
Thank You,
Chirag Shah
Wild, according to this:https://stackoverflow.com/questions/50694925/how-to-solve-the-system-error-h80040e14-2147217900-in-e...
Hey Guys,
I resolved the problem reseting all the data source connections and cleaning the cache of the report,
Hope this helps to you in the future,
Regards to all
@uvil , Some issue with Connecting with the source. check VPN of Ip whitelisting .
refer
https://support.microsoft.com/en-in/help/966146/run-time-error-2147217900-80040e14
User | Count |
---|---|
117 | |
77 | |
58 | |
52 | |
46 |
User | Count |
---|---|
171 | |
117 | |
63 | |
57 | |
51 |
DB_CONNECT_STRING
- perhaps the database is no longer compatible with it. – CLR Jun 5 '18 at 9:28