container exited unexpectedly with code 0x80131904. used features: (none).

[gsalas]

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:

[gsalas · Accepted solution]

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.

https://social.technet.microsoft.com/Forums/en-US/e5c8a3b6-2604-41c3-88cf-152b69b6c091/microsoftmash...

[Greg_Z]

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.

[v-shex-msft]

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.

[v-shex-msft]

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

[gsalas]

No Custom functions.  Data is SQL Server.  Connection function is standard out-of-the-box Power Bi Desktop App "Get Data" --> "SQL Server" function.

[Eric_Zhang]

@gsalas

What is the Power BI version in your case? Can you be more specific about the steps to reproduce that issue? Have you tried with the latest Power BI Desktop?