Reply
Highlighted
Frequent Visitor
Posts: 3
Registered: ‎05-30-2017

Refreshing Error Due to Insufficient Memory

Hi,

 

I am having refreshing issues on both service and desktop due to insufficient errror, and cannot resolve it. I would appreciate if anyone can provide me guidance.

 

This is the message I see when I attempt an 'on demand' refresh:

PBI Error 1.png

 

 

 

 

 

 

 

I see the error message above although I have the following set:

 

1. Max. allowed data is 100,000 mb

PBI Error 2.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

2. There is more than enough personal space

 

PBI 3.png

 

 

 

 

 

 

 

 

 

Thanks

Super User
Posts: 1,830
Registered: ‎02-28-2017

Re: Refreshing Error Due to Insufficient Memory

What is the memory like on your Gateway? Could your gateway machine be running out while its processing?  I'd consider both RAM and hard drive.


   

              Did I answer your question? Mark my post as a solution!
       

Proud to be a Datanaut!


   


Frequent Visitor
Posts: 3
Registered: ‎05-30-2017

Re: Refreshing Error Due to Insufficient Memory

[ Edited ]

Hi @Ross73312,

 

Thank you for your post! I am using 16 GB of RAM on my PC. I am not using Gateway tho; connecting directly to an online server.

PBI - Connect.png

 

 

Frequent Visitor
Posts: 3
Registered: ‎05-30-2017

Re: Refreshing Error Due to Insufficient Memory

I have double checked on both my ram and harddrive usage. I don't see any problem with them. Looks like there is a different type of issue.

 

RAM Usage

PBI - RAM.png

 

 

 

 

 

 

 

 

 

 

 

 

Harddrive

PBI - Harddrive.png

 

 

Super User
Posts: 1,830
Registered: ‎02-28-2017

Re: Refreshing Error Due to Insufficient Memory

Ok that does change things as using Direct Query has alternate limitations.  Does your query fall foul of any of these (such as the million row limit):

 

  • All tables must come from a single database

  • If the Query Editor query is overly complex, an error will occur. To remedy the error you must either delete the problematic step in Query Editor, or Import the data instead of using DirectQuery

  • Relationship filtering is limited to a single direction, rather than both directions

  • Time intelligence capabilities are not available in DirectQuery. For example, special treatment of date columns (year, quarter, month, day, so on) are not supported in DirectQuery mode.

  • By default, limitations are placed on DAX expressions allowed in measures; see the following paragraph for more information

  • There is a 1 million row limit for returning data when using DirectQuery. This does not affect aggregations or calculations used to create the dataset returned using DirectQuery, only the rows returned. For example, you can aggregate 10 million rows with your query that runs on the data source, and accurately return the results of that aggregation to Power BI using DirectQuery as long as the data returned to Power BI is less than 1 million rows. If more than 1 million rows would be returned from DirectQuery, Power BI returns an error.


   

              Did I answer your question? Mark my post as a solution!
       

Proud to be a Datanaut!