Forum Discussion
Helper ICannot load model in report on group Workspace starting from June 22. In MyWorkspace it loads
I have an issue every time I open a report on Power BI Service in a group working space. It started on June 22. It tries to open for a few minutes then the following message appear. When I open the same report on My Working space it opens in 2 seconds without any problems, as always before.
The same issues I face with other reports
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 check the technical details for more information. If you contact support, please provide these details. •
Underlying ErrorPowerBI service client received error HTTP response. HttpStatus: 503. PowerBIErrorCode: OpenConnectionError •
OpenConnectionErrorYou have reached the maximum allowable memory allocation for your tier. Consider upgrading to a tier with more available memory. •
Correlation ID894739a4-5cd7-643f-d3b9-b814b5ebd97a •
Activity ID1d010036-06a8-4ba9-931e-e39417ec58af •
Request IDe649a56c-9b0c-7b46-bf9e-50bd27254b6a •
TimeTue Jun 23 2020 09:13:32 GMT+0300 (Восточная Европа, летнее время) • S
ervice version13.0.13599.209 • Client version2006.2.01600-train •
Cluster URIhttps://wabi-west-europe-redirect.analysis.windows.net/
Hi Raaassotto
Have you analyzed your Premium environment? You can do this with the Premium Capacity Metrics App: https://docs.microsoft.com/nb-no/power-bi/service-admin-premium-monitor-capacity
If you have a lot of datasets, with a lot of users, you might want to upgrade to a higher SKU, or if applicable, split your current SKU into one or more smaller SKU.
You can use the Metrics app to identify the hours during the day with the heavies workload, in addition to the datasets pulling the most resources.
Sometime this may be a temporary error.
You could have a reference of these two similar threads which have been solved.
https://stackoverflow.com/questions/45634697/azure-analysis-services-maximum-allowable-memory-issue
- Hi Raaassotto,
this is definitely a Premium capacity error. So the memory available is not sufficient. Can you confirm you are using Power BI Premium? You can see that if the diamond shows after the workspace name.
My Workspace is never in Premium capacity, that's why those reports are always working.
You (or at least the Power BI Service Admin with sufficient rights) can indeed analyze the memory usage with the Premium Capacity Metrics App. Either get less workspaces in Premium, or improve the performance/decrease the size of your datamodels.
4 Replies
- v-diye-msft
Community Support
Hi Raaassotto
The reason why you are getting that error is because you sent a dashboard with "Pro" content to someone who does not have a "Pro" license. https://powerbi.microsoft.com/en-us/documentation/powerbi-power-bi-pro-content-what-is-it/
Here're another threads for your reference:
https://community.powerbi.com/t5/Desktop/Couldn-t-load-the-schema-for-the-database-model/m-p/494790
RaaassottoHi, Dina Ye
The problem is when I open a report, not dashboard. I left only pro users in an access list to the report . It didn't help. The error message says about "Memory error: You have reached the maximum allowable memory allocation for your tier. Consider upgrading to a tier with more available memory" What does it mean?
- v-diye-msft
Hi Raaassotto
Have you analyzed your Premium environment? You can do this with the Premium Capacity Metrics App: https://docs.microsoft.com/nb-no/power-bi/service-admin-premium-monitor-capacity
If you have a lot of datasets, with a lot of users, you might want to upgrade to a higher SKU, or if applicable, split your current SKU into one or more smaller SKU.
You can use the Metrics app to identify the hours during the day with the heavies workload, in addition to the datasets pulling the most resources.
Sometime this may be a temporary error.
You could have a reference of these two similar threads which have been solved.
https://stackoverflow.com/questions/45634697/azure-analysis-services-maximum-allowable-memory-issue