Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
Theo_Westsite
Frequent Visitor

Refresh error / Exceed maximum page size of the storage object (65528 bytes)

Hello guys,

 

i have the same problem as described in this post:

Analyze in Excel Memory Error - Microsoft Fabric Community

 

I would like to understand if there are any new insights into how to deal with this problem?

 

I use Excel O356 64-bit (latest version) and retrieve data from PowerBI into Excel via an OLAP cube. This worked fine until recently. I had a dataset in PowerBI with many queries (queries on Excel tables), the number of which I recently drastically reduced. Afterwards, I added only one query (query on Excel tables), which is now causing the problem.

What makes this strange is:

a) The new query has significantly fewer rows than the old queries I deleted. I also made sure that the table range in Excel is relatively small.
b) As an attempt to solve this, I reduced the number of columns and rows sequentially, so much so that in the end there was only one row and five columns, but the problem persists.
c) I deleted all columns with long text and reduced the decimal places in the Excel table to two.
d) I converted the new Excel file from xlsx to csv, but that didn't help either.
d) DAX Studio didn't identify any problematic data sets.

Does anyone have a solution for this?

Thanks in advance.

Thanks for refraining from saying things like, "Just use PowerBI and forget about Excel/OLAP etc."

1 ACCEPTED SOLUTION
Theo_Westsite
Frequent Visitor

After extensive search, we came to the conclusion, that the dataset had too many columns. The number of rows wasn't an issue—it was all about the columns. This, combined with the architecture of the dataset, caused the problem.

We are loading multiple tables with this structure:

 

Row Nr.Item01/31/2021.....12/31/2045
1Europe0,05.....2,5
2Asia2,5.....2,6
.....................
10.000NA5,5.....5,4

 
The dataset architecture used queries for each of these tables. In the second step, we merged all these queries into a master table and repivoted all the columns from the matrix format into one table with only four columns:

 

Row Nr.ItemDateValue
1Europe01/31/20210,05
................
1Europe12/31/20452,5
................

 

When reloading the OLAP Cube, the error message popped up.

 

How did we fix the issue?

We repivoted each table before merging them into the master table. By doing this, we prevented the OLAP Cube from loading an excessive number of columns.

 

An alternative, maybe easier approach is - if the multiple tables are being merged into one table and repivoted (like in the example above) - deactivating the single Tables/queries from being loaded into the dataset also helps. The data is still being considered in the master table, but the single Tables/queries are spared from entering the OLAP Cube.

 

Hope that helps someone.

View solution in original post

11 REPLIES 11
Theo_Westsite
Frequent Visitor

After extensive search, we came to the conclusion, that the dataset had too many columns. The number of rows wasn't an issue—it was all about the columns. This, combined with the architecture of the dataset, caused the problem.

We are loading multiple tables with this structure:

 

Row Nr.Item01/31/2021.....12/31/2045
1Europe0,05.....2,5
2Asia2,5.....2,6
.....................
10.000NA5,5.....5,4

 
The dataset architecture used queries for each of these tables. In the second step, we merged all these queries into a master table and repivoted all the columns from the matrix format into one table with only four columns:

 

Row Nr.ItemDateValue
1Europe01/31/20210,05
................
1Europe12/31/20452,5
................

 

When reloading the OLAP Cube, the error message popped up.

 

How did we fix the issue?

We repivoted each table before merging them into the master table. By doing this, we prevented the OLAP Cube from loading an excessive number of columns.

 

An alternative, maybe easier approach is - if the multiple tables are being merged into one table and repivoted (like in the example above) - deactivating the single Tables/queries from being loaded into the dataset also helps. The data is still being considered in the master table, but the single Tables/queries are spared from entering the OLAP Cube.

 

Hope that helps someone.

v-pagayam-msft
Community Support
Community Support

Hi @Theo_Westsite ,
Thank you @lbendlin  for the prompt response!

May I ask if you have gotten this issue resolved?
If it is solved, please mark the helpful reply or share your solution and accept it as solution, it will be helpful for other members of the community who have similar problems as yours to solve it faster.

Thank you.

lbendlin
Super User
Super User

I assume you want to stick with MDX and do not want to consider running DAX queries instead?

Unfortunately, setting an entire new model (DAX) isnt an option. I dont get why multiple queries with a lot of columns and rows doesnt cause an issue, but deleting them and implemeneting an single query with less columns and rows does...

When you connect to an OLAP cube you connect to all of it.  Performance will depend on which columns you choose and how they are related in the multi dimensional data model.  It is very easy to bring a cube to its knees by choosing only a few but unrelated columns.

Thanks for your feedback. I checked but couldnt find any unrelated columns in the model. Is it possible to load only selective data into the OLAP cube? If not, is there any other approach i could try?

Is it possible to load only selective data into the OLAP cube? 

Not sure what you mean by this or what this could have to do with the issue you are describing. Are you the cube owner?

Yes, im the cube owner. Got it, so there is no way to selectively load data into an OLAP Cube. Do you have any furhter advice / approach i could try?

You can selectively process individual cube partitions. Still not sure what that has to do with the original question.

Oddy
Frequent Visitor

Did you find a solution to this? Got entire systems brought to it's knees because of this

Yes, found a solution for that. See above.

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

Check out the August 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.