Forum Discussion

tsf's avatar
tsf
Helper I
9 years ago
Solved

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?

  • tsfAnonymous 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 

5 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

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

     

  • v-qiuyu-msft's avatar
    v-qiuyu-msft
    Community Support

    tsfAnonymous 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 

    • Anonymous's avatar
      Anonymous
      Not applicable

      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.

    • tsf's avatar
      tsf
      Helper I

      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.

  • Hi I got the same error message and the historical updates has worked fine, until the 1 of March.