Same error different files file contains corrupted data, value -2147467259

[DouweMeer]

My queries keep getting the same type of error. Worse, the "corrupted" value is everytime the exact same value, value -2147467259. Sometimes as well, if you refresh, it fails at a different file, same error, same value, different file. When I refresh the model from Power BI Desktop, no errors, all fine. 

It's such a hassle to have to go into the file, copy paste the data in a new Excel and then save that new one as the file just as workaround is really annoying and time consuming (not just the act, the getting error, figuring out where which file as the table reference isn't the source's location). 

Anyone knows what's causing these errors so instead I can try to mitigate it occuring? 

{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"<ccon>File contains corrupted data.</ccon>"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataFormat.Error"}}],"exceptionCulprit":1}}} Table: Excel 

[v-dineshya]

Hi @DouweMeer ,

Thank you for reaching out to the Microsoft Community Forum.

Hi @GilbertQ , Thank you for your prompt response.

Hi @DouweMeer , As you mentioned that, You are facing error “File contains corrupted data” with value -2147467259, which appears across different files during refreshes via the Gateway, but not when refreshing in Power BI Desktop.

The error code "-2147467259" corresponds to a generic COM error often triggered by data format issues or corruption in the source file. The message DM_GWPipeline_Gateway_MashupDataAccessError indicates that the Power BI Gateway is failing to access the data correctly.

Please try below steps to fix the issue.

1. You mentioned manually copyed data into a new Excel file works. Automate this by opening the file in Excel and Save it as .xlsx file. Also check no hidden sheets or broken links exist.

2. In Power BI, Go to Transform Data and apply Clean, Trim, and Replace Errors operations on all columns and Remove blank rows and columns.

3. Clear Power BI Cache, Go to File --> Options and Settings --> Options --> Data Load and Click Clear Cache.

4. Check the Gateway is updated and Verify that the file path is accessible and not on a network drive and Use Import Mode instead of DirectQuery if possible.

Please refer Microsoft official document and community threads.

Dealing with errors - Power Query | Microsoft Learn

Solved: File contains corrupted data - Microsoft Fabric Community

Solved: Re: DM_GWPipeline_Gateway_MashupDataAccessError - Microsoft Fabric Community

Solved: DM_GWPipeline_Gateway_MashupDataAccessError - Microsoft Fabric Community

Solved: DM_GWPipeline_Gateway_MashupDataAccessError (Not l... - Microsoft Fabric Community

If this information is helpful, please “Accept it as a solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.

Regards,

Dinesh

[v-dineshya]

Hi @DouweMeer ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

Regards,

Dinesh

[v-dineshya]

Hi @DouweMeer ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

Regards,

Dinesh

[DouweMeer]

I haven't had the priority to review the proposed solution as I will be on holiday in a few days. 

Will evaluate the proposed solution in, like, August. I'll probably have then more time. 

[v-dineshya]

Hi @DouweMeer ,

Thank you for the update. Once you are back and have completed the testing, please keep us posted.

Regards,

Dinesh

[GilbertQ]

Hi @DouweMeer 

The reason you're getting what looks to be like different errors is because the file has corrupted data. I would recommend going through the data and making sure all the data types are matched in the particular columns because this is where it is possibly causing the error.

[DouweMeer]

Truly corrupted data, was hoping for a bug or not having the latest version or something. 

Just one question, why would Power BI Service fail on this piece but Desktop succeed?

Bit more context. Refresh goes trough a personal gateway where the files are derived locally through synched sharepoint folders. The personal gateway runs on a different computer than the refresh for Power BI Desktop. But I can't imagine such interference would exists between two computers... Like, what would driving such issue on corrupted data?