Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Reply
tsf
Helper I
Helper I

Exception of type 'Microsoft.DataProxy.Exceptions.HybridException' was thrown.

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?

1 ACCEPTED SOLUTION
v-qiuyu-msft
Community Support
Community Support

@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 

Community Support Team _ Qiuyun Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

5 REPLIES 5
FredrikSweden
New Member

Hi I got the same error message and the historical updates has worked fine, until the 1 of March.
v-qiuyu-msft
Community Support
Community Support

@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 

Community Support Team _ Qiuyun Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

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.

Chemiefrik
Frequent Visitor

Same Problem here, some Reports work some get this error message.

 

Helpful resources

Announcements
April AMA free

Microsoft Fabric AMA Livestream

Join us Tuesday, April 09, 9:00 – 10:00 AM PST for a live, expert-led Q&A session on all things Microsoft Fabric!

March Fabric Community Update

Fabric Community Update - March 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors