Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
This error just started occurring two days ago when refreshing data in the service for all of the reports we publish to our PBI site. (Our cube-based reports hitting our on-prem AS server are working fine.)
I read in another post that a possible work-around was to re-publish using the latest version of PBI Desktop. However, I've done this and still get these errors. What should I check? Any known problems with this?
Solved! Go to Solution.
@tsf@Anonymous Did you not able to refresh SQL on-prem dataset with error message: Microsoft.DataProxy.Exceptions.HybridException? Which gateway did you configure for those datasets? Please uninstall the personal gateway or on-premise data gateway and download the latest version.
Best Regards,
Qiuyun Yu
@tsf@Anonymous Did you not able to refresh SQL on-prem dataset with error message: Microsoft.DataProxy.Exceptions.HybridException? Which gateway did you configure for those datasets? Please uninstall the personal gateway or on-premise data gateway and download the latest version.
Best Regards,
Qiuyun Yu
Looks like the upgrade resolved that particular message, but now I'm getting a PrincipleNameMismatch error reason related to SQL (which I didn't have previously). I see that the documentation refers to using the FQDN, but so far my attempts haven't brought a resolution. I'll keep looking and start another post if I can't get past that. Thanks.
Thank you, for your quick responce.
I reinstalled my personal Gateway, some reports start working again.
But on another Report i get another error: "
Not a legal OleAut date.. The exception was raised by the IDataReader interface.
"
I looked up that error in the community and it was caused by a wrong Date which was. 07.06.017 (the 2 of the year is missing)
So Thank you, for solving it.
Same Problem here, some Reports work some get this error message.
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
9 | |
7 | |
5 | |
5 | |
5 |
User | Count |
---|---|
10 | |
8 | |
6 | |
6 | |
6 |