Forum Discussion
Advocate IIcontainer exited unexpectedly with code 0x80131904. used features: (none).
Every time I refresh the table, I get this error:
container exited unexpectedly with code 0x80131904. used features: (none). When I go into the "edit Query" windows, here is what I find:
When I manually refresh the preview window, the error goes away:
I found the solution on a forum site:
I went to the local cache for Power Bi (something along the lines of C:\Users\username\AppData\Local\Microsoft\Power BI Desktop\Cache) and deleted all files found there. Once I did that I went back into my existing data model and everything is working again.
11 Replies
- gsalas
I found the solution on a forum site:
I went to the local cache for Power Bi (something along the lines of C:\Users\username\AppData\Local\Microsoft\Power BI Desktop\Cache) and deleted all files found there. Once I did that I went back into my existing data model and everything is working again.
Thank you for the information! I ran into the same issue with the cache when I was switching between the 64 bit and 32 bit versions of Power BI. We were updating several of our reports that are using Firebird, and the cache was causing a conflict because it stored the 32 bit version of the data.
Hi gsalas,
>>When I manually refresh the preview window, the error goes away:
I think the issue is not related to your current query. Please turn off the refresh feature of the query which not need to refresh.
Steps:
1. Choose the query which you not want to refresh.
2. Right-Click on it.
3. Cancel the check state of "Include In Report Refresh".
Regards,
Xiaoxin Sheng
- gsalas
This error is ocurring on a query that has be refreshed. I can't turn off the refresh feature.
Hi gsalas,
Did you use any custom functions to analysis the data source?
Can you share some detail content of your issue?(e.g. datasource, connect mode...etc) It will help for trouble shooting.
Regards,
Xiaoxin Sheng
I had the same problem just today. I found that one of the users changed one of the column names. When i changed it back it was all sorted. And i did not get this message again and refresh was successful.
kleighResponsive Resident
Since this is the top result in web search, I will add my findings here:
I couldn't refresh in Desktop or Service. Service gave an out of memory error on a table that had not changed.
I tried copying the entire query to a new workbook. This "worked", but is not a solution. The measures can be brought over with DAX Query View (with a lot of work to add back descriptions, folders and formats). I know many discourage calc columns, but the model has them for now and those cannot easily be moved. I'm under the impression calc columns and measures should not block a Power Query refresh, so this hinted there was nothing wrong with my query?
I tried bifurcation - deleting from my model until the error went away. Eventually, I got to a state where deleting anything from the model would fix the problem. Not instantly, though. I was instead getting one of those spurious "Please rebuild this data combination" errors that are fixed by opening the table in Power Query and refreshing preview on the guilty table. Once I cleared those, the Desktop refresh would go through.I tried forcing a model change in the original file (I deleted an old table that was no longer used). I then made the Power Query preview Refresh All. Finally, I refreshed the desktop model and the error had disappeared!
My suspicion is Power Query can get in an invalid state, which is causing both the data combination bugs and this refresh failure. Giving it a nudge will clear the error. The trick is discovering what nudge is needed.
This is in Version: 2.136.1202.0 64-bit (September 2024) - but given the long history of people posting this error it seems to be of general application.- kleigh
Version: 2.137.1102.0 64-bit (October 2024)
It happened again. I still had my bifurcated files, which resolved in the same way.Since I had the main file as a .pbip, clearing the main cache, then deleting cache.abf cleared the error. When you delete cache.abf, you will be prompted to refresh. In my case, this refresh succeeded.
- kleigh
Version: 2.157.1354.0 64-bit (August 2026) - Container exited unexpectedly with code 0x80131623
This time, deleting cache.abf and clearing the Power BI cache did not clear the error. I discovered a new trick with pushing a model refresh in Power Query:- Note which tables have the refresh error reported on them.
- In Power Query, add new columns to all of these tables. The formula can just return null.
- The affected tables will recalculate.
- You can then refresh to get the rest of the tables loaded.
- The extra columns can then be deleted.
Obviously, this only works if the errors appear at the table level. As noted in the original screenshot, you do not always have this clue. But if it's there, try making use of it!
