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

This is de solution.

https://powerbi.microsoft.com/en-us/blog/tech-tip-thursday-user-principal-name-upn-mapping-in-power-bi/

NeeleshRaheja

In Power BI Desktop, when you open live connection to SSAS, you need to select specific cube.

If you select entire database, it will throw above error.

Regards,

I have the same error.  Is there any guide or solution to this..?

gzeladaNeeleshRaheja I ran into a similiar error yesterday on a Tabular model (I don't recall the exact error) Have you tried deleting the stored datasource in the Desktop? That worked for me. I just re-connected after removing the cached version.

File -> Options and Settings -> Data Source Settings -> Tick "Global" -> select the data source -> Clear Permissions -> delete

I'm running into the same issue. Have tried Anonymous's idea and it didn't work :/

Was going to upload new cubes and new content packs to our users but now..gotta keep trying. I'll come back if I find anything :(

EDIT: Solved it, I think.

1. Make sure the reports you are creating in PBI desktop are pointing to the right server and cube

2. Make sure the datasources in your Enterprise gateway points to the right server and cube. 

Simple but something you easily can forget if you have several environments. Tried deleting the SSAS datasources in the Enterprise Gateway and re-created them and made them point to the right server and database and it worked :) 

Hi, What I came across today - is permission related. Even if the gateway account has access to specfic cubes (local), it wasnt' working untill I've added this account to SSAS server administrator list. After that model loaded.

Anyway, need to check attribute  AttributeHierarchyEnabled approach as setting security this way doesn't seem right.

Try this, go to 'Manage gateways' on the top right corner of the web powerbi and in the gateway, go to your datasource. Now, make sure you have it online and also in the 'Users' section, you have the access to the account, which has the permissions on the cube and now, go to the 'Map user names' and select 'CustomData' and hit 'Ok' (doesn't have to specify any mapping information, if not needed to). Give it sometime and check the report back, if still have the same issue, trying deleting the existing dataset and publish the report from the desktop once again.

I have the same error.  Is there any guide or solution to this...?

Any news on this ?

My trace on AS says this:

Internal error: An unexpected error occurred (file 'xlmodel.cpp', line 4835, function 'XLTableAttrPaths::InitOLAP').

/m

I solved my problem recently. Unfortunately, I did not find the root cause.

But here is what I did to solve the problem:

I took my non-working SSAS project and deployed the hole project into a test SSAS DB.

Then I processed only the structure.

Next I opened SSMS connect to the SSAS instance and opened a MDX query window:

Here I typed a simple DAXMD query like:

Evaluate 'Date'

If it works like it does in Adventure Works

It should look something like this:

If it doesn’t it should give you the error massage

"unexpected error"

If the error message is different either you need the following connection string property:

Or you are dealing with a different problem.

---------------------

From here on comes the part which involves some work depending on the size of your SSAS project (I assume from now on you received the "unexpected error" from advanced):

Open the non-working SSAS DB online which had only been processed with "process structure" in visual studio.

And then you need to start delete cube dimensions one by one.

After you deleted the first dimension do a process structure again and try your DAXMD query again in SSMS:

Evaluate 'YourDimension'

You need to repeat this until you find the dimension which causes the "unexpected error".

In my case it has been a role playing dimension.

Once I found the troubling dimension I went back to my source control version of the SSAS project removed the cube dimension in question and added it again. Be careful that you set all depending things like security, dimension usage, perspectives, action, aggregations etc. related to the deleted dimension back to way they had been.

Then I deployed the project again and now DAXMD and Power BI works.

I did a diff on the hole xmla of the SSAS DB and apart from the order of some codes parts I could not find any difference in the working and the non-working Cube.

Never the less no it works and I hope my instructions help to solve the problem for others as well.

.