Failed to open the MSOLAP connection - premium capacity

[Anonymous]

We are getting below error message.

Our datasets and reports are in a premium capacity. We have RLS on the dataset. Using as Power BI embedded. Code able to get embed token and try to embed it, it get metadata of report and start loading data, take few minutes and message says Almost Done.. and then fail with the below message

Could not load the model schema associated with this report. Make sure you have a connection to the server and try again.

Underlying Error: PowerBI service client received an error HTTP response. HttpStatus: 503. PowerBIErrorCode: OpenConnectionError
OpenConnectionError: Failed to open the MSOLAP connection.
Correlation ID: a5729f30-e11c-ce79-c8f4-0f3709dd1e61

[v-yueyunzh-msft]

Hi , @Anonymous 

Based on my research on your issue situation met and error given, this error message indicates that there was an issue loading the model schema associated with your report in Power BI. The cause of this issue could be a connection problem with the server or a problem with your dataset.

Here are a few potential solutions to resolve this error:

1 Check your internet connection: Ensure that you have a stable internet connection and try refreshing the report again.

2 Check Power BI service status: Verify that the Power BI service is up and running by checking the Power BI service status page.

3 Check dataset settings: Ensure that the dataset you are trying to access is set up correctly and that it has been published to the Power BI premium capacity successfully.

4 Check RLS settings: Review your Row-Level Security (RLS) settings to ensure that they are configured correctly and that they are not blocking your access to the report.

Thank you for your time and sharing, and thank you for your support and understanding of PowerBI! 

Best Regards,

Aniya Zhang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

[Anonymous · Accepted solution]

Thanks for you response.

We tried all above points you suggested, before raising issue but was not able to resolve.

However we manage to fix issue and it was to do with our proxy service and way we passing identity object when using RLS.

Just for benefit of others sharing information:

Problem was we were passing parent dataset id and reports own dataset id (both) in the Identity object (we have composite data model). RLS was exist only on parent dataset id. We were not sure about how RLS will work when using composite model.  Without composite Model our report embedding was working fine with RLS.

After few trials and errrors, finally figure out only that in identity object only pass dataset id where RLS is configured (dont pass any other child dataset id). This works for us.