Forum Discussion
cannot load model
Hi Anonymous ,
Do the users have access to the data model?Do they configure the data source in service successfully?If their user name in Azure Active Directory (Azure AD) doesn't match a UPN in your local AS data model,they need to map users in their data source configuration.
Here is the reference.
https://docs.microsoft.com/en-us/power-bi/service-gateway-enterprise-manage-ssas
Best Regards,
KellyDid I answer your question? Mark my post as a solution!
Hi Anonymous ,
Do the users have access to the data model?Do they configure the data source in service successfully?If their user name in Azure Active Directory (Azure AD) doesn't match a UPN in your local AS data model,they need to map users in their data source configuration.
Here is the reference.
https://docs.microsoft.com/en-us/power-bi/service-gateway-enterprise-manage-ssas
Kelly
The user has access to the dataset, I even tried to map the user as proposed by Kelly but still no change in the issue. \The user cannot create a report if this dataset is being used, any other dataset is not giving any issue.....User still gets this message:
Cannot load 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.
Underlying error code: -1055391743=Underlying error message: Either the user, 'DomainXXX\jdoe' does not access to the 'Sls_XXX' database or the database does not exist. Correlation ID: 15aa433c-633c-24c7-819c-b7f861a8a475
DM_ErrorDetailNameCode_UnderlyingHResult: -2146233088
Activity ID: 76282630-ebf0-40c1-bcaf-e128ee014419
Request ID: a5de1fcb-c1dd-36db-d92c-d332ca5acf4f
Time: Mon Mar 09 2020 14:02:11 GMT+0100 (W. Europe Standard Time)
Service version: 13.0.12522.196
Client version: 2002.4.021
Cluster URI: https://wabi-us-north-central-redirect.analysis.windows.net/
\
Hi Anonymous ，
1. Make sure the reports you are creating in PBI 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 ,re-create them , make them point to the right server and database to see whether it works.
Best Regards,
KellyDid I answer your question? Mark my post as a solution!Hi Anonymous
Providing the access rights to Sls_XXX database for the DomainXXX\Jdoe should resolve your issue.