Forum Discussion
There's Not Enough Memory To Complete This Operation
Hi, I ran into the same problem when only refreshing 67MB data. Do you have any idea why it failed?
Does it always fail? What about after a reboot?
Ensure you are using 64bit to make best use of memory.
Are you on the latest version?
- ludovit88 years ago
Helper I
It always fail, there is daily reboot. We use 64bit memory, profi server memory. It is problom in powerBI not in HW.
Latest version, yes, of course.
- stretcharm8 years ago
Memorable Member
Are you doing anything complex? E.g. lots of pivots/unpivot merge duplication & functions.
Are you able to reduce the data sets or disable some of the queries to see what if will complete and isolate where the problem may be.
It should easily cope with 67Mb of data so it might be worth loggin a support ticket to get help.
If you have lots of queries does it get stuck running them all? I have sometimes had to run them one at a time due to time outs.
Are you using Direct Queries? If so try the Query Reduction Options.
Also try different options on the Data Cache (under Data Load in settings) however I've never needed to change these.
- Anonymous8 years agoNot applicable
Greetings, to me this seems to be a 'bug' in the memory management of the widgets. I have done this in the past versions with no ill affect but in the past 2 versions this has become an issue.
I have a lot of memory available and I am simply pulling a list of dimension objects in (SSAS MD Cube) into a simple table widget. All works well returning less then 100 rows, 4 columns of data. When I add one more Fact column...memory issue happens. Pull that fact item out and add another dim item (now at 5 columns)...no problem.
Yes, when I filter the data down to a few records it returns fine. However the process to use the UI is to allow the end user to filter down to get a question answered that would imply the initial rendering would not be filtered and should have the capacity to handle, to some real memory limit, a large dataset. This also fails in a similar way when the report is deployed into PBIRS and view via the browser.