Forum Discussion

mdw's avatar
mdw
New Member
1 year ago
Solved

Power BI Non-null assertion failure

Anyone seen this - "Non-null assertion failure: resource: Resource should be available for query (queryname) to store FoldedArtifacts in cache"?

 

Power BI wants me to report this issue to Microsoft.  

 

Thoughts on how I can get by this?

 

Thanks.

  • Anonymous's avatar
    Anonymous
    1 year ago

    Thanks for parry2k's concern about this issue. 

     

    Hi, mdw 

    I am glad to help you.

     

    May I ask what type of data source are you using? What operation is being performed that is causing this error? Is a very large dataset being used?


    In Power BI, this error may occur if the dataset is too large or the query is complex such that the memory consumed by the query or calculation exceeds the configured limit.


    If this is the reason, you can try to optimize your dataset by simplifying the query and removing unnecessary columns to reduce memory consumption.
    If you are using import mode to connect to the data source, you may also want to consider using DirectQuery mode or Live Connection mode to connect to the data source.

     

     

    I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
    Best Regards,
    Fen Ling,
    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

8 Replies

  • tomwill's avatar
    tomwill
    Microsoft Employee

    I am getting this error and the response marked as Solution is not a solution.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Thanks for parry2k's concern about this issue. 

     

    Hi, mdw 

    I am glad to help you.

     

    May I ask what type of data source are you using? What operation is being performed that is causing this error? Is a very large dataset being used?


    In Power BI, this error may occur if the dataset is too large or the query is complex such that the memory consumed by the query or calculation exceeds the configured limit.


    If this is the reason, you can try to optimize your dataset by simplifying the query and removing unnecessary columns to reduce memory consumption.
    If you are using import mode to connect to the data source, you may also want to consider using DirectQuery mode or Live Connection mode to connect to the data source.

     

     

    I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
    Best Regards,
    Fen Ling,
    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

    • moone33's avatar
      moone33
      Frequent Visitor

      The operations is when I click on the refresh button on the Home menu.  This error occurs on small and large datasets.  It only happens on the ones with Incremental refresh is enabled.  When I disable Incremental refresh, no error, no matter if it is large or small dataset.  I forgot to add it still refreshes the dataset

    • aswinf's avatar
      aswinf
      Regular Visitor

      This isn't a solution for me either. I'm seeing the issue with a direct query to SQL Server that is returning a small (few thousand rows) result set. I have 10GB of free memory and no way should memory be exceeded. 

  • moone33's avatar
    moone33
    Frequent Visitor

    I see the resolution but my rows returned is ONLY 6 million records.  This is very small compared to other dataset I publish.  Is this the only resolution?

     

    The only time I dont get this error is when I remove the Incremental refresh.

     

     

  • TE's avatar
    TE
    Helper I

    I have the same issue. Was there a solution?