Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
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@Chemiefrik 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@Chemiefrik 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.