Power BI Personal Gateway - Data Refresh failure

[heathernicole]

I have setup a computer for reporting for each of our companies. 

Each one has their own personal gateway.

I've made sure the credentials are correct - but I keep getting an error message - any ideas??? 

Last refresh failed: Tue Mar 01 2016 00:20:43 GMT-0500 (Eastern Standard Time)
An error occurred while processing the data in the dataset.

Hide details

Processing error:	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. 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. 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.
Cluster URI:	WABI-US-EAST2-redirect.analysis.windows.net
Activity ID:	165fa9e4-eff2-468c-9581-24e295eb05a5
Request ID:	804c2162-476d-484b-b1a3-4ac54f292a39
Time:	2016-03-01 05:20:43Z

[Greg_Deckler]

Just spit-balling here, but are you on a 32-bit or 64-bit OS? Is this happening on all of the machines?

[heathernicole]

Both computers are 64-bit.

One company is refreshing fine - the other isn't. 

[austinsense]

Aggghhh this just happened to me with a client - I can't find a solution.

[heathernicole]

Still having this issue - and apparently no one else is sure what's causing it either. 🙂 

[austinsense]

Here's my guess - the Azure service running the Power BI update job in the background has some memory limitations.

I ran the update job manually yesterday and watched the computer with the gateway service running.  There wasn't a spike in memory consumption and it certainly never got close to maxing out.  I shrank my model a little bit, just taking some dates off of the main fact table, and now everything works fine.  This is a bad error that Microsoft should be aware of - for now shrinking the model a bit seems to fix the problem.