Forum Discussion

NeeleshRaheja's avatar
NeeleshRaheja
Icon for Advocate I rankAdvocate I
10 years ago

Couldn't load the model schema - Error with latest PBIDesktop live connection SSAS Multidimensional

using live connection with PBI Desktop, I can see the cube but on selecting a cube, get an an error Couldn't load the model schema   trace is below   DataMashup.Trace Critical: 24579 : {"Start":"...
Need Help
krepko7's avatar
krepko7
Icon for Microsoft Employee rankMicrosoft Employee
10 years ago

Thanks for the post.  Unfortunately this issue occurs when connecting from Power BI Desktop live to SSAS not in the Power BI Service where you have the option to map user names in the data source user options.

  • ManuMCD's avatar
    ManuMCD
    Regular Visitor
    10 years ago

    I have exactly the same issue since 1 moth ago and the users can't use tabullar tables from Power BI. I have tried to ask to MS support and they are no able to explain the problem. At this moment i guess is a issue problem AS instance or domain.

     

    If  anybody has be able to solve that?

     

    Regards

    • Simon_W's avatar
      Simon_W
      Icon for Helper I rankHelper I
      10 years ago

      In my case it only concerns MOLAP Cubes, I'm not sure if we then really face the same Problem. The only funny thing is that I have several different MOLAP Cubes on the same Instance and some work and other don’t work with Power BI Desktop.

       

      So my guess it has to be within the Model some kind of feature or anything else that breaks the use of Power BI (DAXMD).

       

      Any further findings please share because it is pretty difficult to explain this my customers.

       

       

      • krepko7's avatar
        krepko7
        Icon for Microsoft Employee rankMicrosoft Employee
        10 years ago

        In this particular case the issue was caused by a date dimension that had a level (year, month, day etc) defined where two fields had the AttributeHierarchyEnabled property set to true.  There are two fields defined for the level since one was used for hierarchy and one for sorting.  Once the AttributeHierarchyEnabled property was set to false for one of the fields it worked.  Hope this helps.