Refresh fail - Memory error: Allocation failure

[ruimonteiro]

Hi,

I'm getting this error while refreshing a dataset connected to a SQL Data Warehouse:

Memory error: Allocation failure . If using a 32-bit version of the product, consider upgrading to the 64-bit version or increasing the amount of memory available on the machine. Memory error: Allocation failure . If using a 32-bit version of the product, consider upgrading to the 64-bit version or increasing the amount of memory available on the machine

Can anybody help?

Thanks in advance.

[GTR]

The 32-bit setup is not as efficient in storing large amounts of data as the 64-bit version. I had this same issue and uninstalling the 32-bit, followed by installation of the 64-bit fixed it.

[ruimonteiro]

Hi, This error occurred in power bi portal, not desktop. The dataset is connected to a Azure Data Warehouse. Thanks!

[cwayne758]

Hey @ruimonteiro! Did you ever resolve this? Please say yes! Lol.

This has been a thorn in my side for the past days or so.

Thanks

[ruimonteiro]

Hi @cwayne758!

Well, it's good to see that I'm not so alone with this issue as I thought lol

Apparently it's a bug (I've received this information through PBI Desktop feedback by the PBI Team when I reported another issue). In my case I'm trying to refresh a dataset connected to a fact table with about 11 million records (SQL Azure DW). Hope that this will be fixed soon!

Rui

[rdeken]

Has this bug been fixed?  I'm hitting it with a very small dataset.

[hongkwokkwok]

I have just added 2 more queries into 20 queries. And then, I got this error.

The data is retrieved thru Enterprise Gateway

[hongkwokkwok]

I've tried to remove some columns and publish the powerbi again.

It works now.

[cwayne758]

Did they say what prompted that the error with that particular dataset? Are your other datasets refreshing?

[ruimonteiro]

No, they just said that they have filed a bug for this. For now I have only this dataset and I can refresh it when o have only a few thousands records on the fact table.

[cwayne758]

Yes my issue is pretty similar. I've seen a few people with this error--no one has gotten it resolved yet.

I just decided to break my report into several smaller one until I here of a more concrete solution.