I am struggled on a problem showing data from Azure Analysis Services (AAS) model in a Power BI service report. The strange thing here is that I, the creator of the Azure Analysis model and the published Power BI Desktop report can see the report but my collegues are getting a weird message saying
Couldn't load the schema for the database model
Couldn't load the model schema associated with this report. Make sure you have a connection to the server, and try again.
Please try again later or contact support. If you contact support, please provide these details.
I have just made a tabular project in Visual Studio 2017 as easy as it can be only created a data table with one column and no data source. Deployed it to Azure, I have also created a Data gateway on azure as well. Then I created a very simple Power BI Desktop report connecting the model on Azure. Then I published it to our power bi site. Everything seems normal. The report and data set shows the data. Then I added my colleague to the workspace area so he can see the report. I asked him to log on the Power BI site and try out the report and THEN he got this messages on the screen telling Couldn't load the schema for the database model
(here is what he sees)
When I log on Power BI I see the report
I seriously need help with this matter. Will assume there is a simple explanation and hope you can help me with this. Any tip will be valuable
Thank you in advance
Well, the other users are all in the Power BI Workgroup, but I guess you think there are settings on the Azure Analysis Services side that are not set properly. I am a bit lost on the Azure side. I can see the Analysis Service Admins, but I think all users won't be in that group. I must in a way set restriction on getting the data so I need to open it to others. I can see that I have not enabled firewall yet. Do you where I can set such things to open this things?
I have no clue on that. I just find it strange that you can use them, but the users cant. Thats why i think its permission related.
Are you using Active Directory by any chance?
Maybe this can help aswell:
Based on my test, it may due to the liscense problem, you could refer to below link: