Forum Discussion
Memory error: You have reached the maximum allowable memory allocation for your tier.
- Anonymous3 years ago
HI Anonymous
You need to upgrade the shared capacity with premiumn capacity to solve this problem, because you have used resources that exceed the upper limit, or you need to optimize the underlying data source to make the query return less data.
You can download the pbix file and refresh it, see how much memory it consumes when refreshing. You can monitor this by going into task manager and looking for "msmdsrv.exe" this is the analysis services engine.
If you exceed the allowable capacity, then you will want to consider upgrading your capacity to Premium capacity and purchasing the appropriate SKUs.
What is Power BI Premium Gen2? - Power BI | Microsoft Learn
Best Regards,
Community Support Team _ Ailsa Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
HI Anonymous
You need to upgrade the shared capacity with premiumn capacity to solve this problem, because you have used resources that exceed the upper limit, or you need to optimize the underlying data source to make the query return less data.
You can download the pbix file and refresh it, see how much memory it consumes when refreshing. You can monitor this by going into task manager and looking for "msmdsrv.exe" this is the analysis services engine.
If you exceed the allowable capacity, then you will want to consider upgrading your capacity to Premium capacity and purchasing the appropriate SKUs.
What is Power BI Premium Gen2? - Power BI | Microsoft Learn
Best Regards,
Community Support Team _ Ailsa Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I encountered the same error message one week ago, but I couldn't duplicate the error message. I have even created a test data model with double size, but no error when I published it to PB service. So I guess this is a temporary issue on PB service. Could someone reveal more lights on this type of error?
Here is a similar thread on the issue: https://learn.microsoft.com/en-us/archive/msdn-technet-forums/94758523-b9fa-4567-b3d9-1759abb54a84