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

[v-dineshya]

Hi @DouweMeer ,

I wanted to follow up and confirm whether you’ve had the opportunity to review the information .

Please do let us know if you have any further queries.

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]

We executed a migration of all source files to a new SharePoint location for an unrelated reason. All files are xlsx and saved new. Still get these problem. Report refreshes fine through Power BI Desktop, fails through Power BI Service. 

Could it be that the sensitivity label on the files cause the corruption due to the encryption? 

[v-dineshya]

Hi @DouweMeer ,

Please try below things to fix the issue.

1. Yes, sensitivity labels applied via Microsoft Purview or Microsoft Information Protection can encrypt files, making them unreadable to the gateway.

Solution: Check if the files have labels like "Confidential" or "Highly Confidential". Try to remove the sensitivity label temporarily and test the refresh. check the gateway machine has Microsoft Information Protection client installed and configured.

2. Since the gateway runs on a different machine, It might not have the same Excel version, updates, or regional settings. It might lack access to SharePoint sync folders or have file locking issues.

Solution: Check the gateway machine has Latest version of Power BI Gateway. Access to the synced SharePoint folders. Excel installed and updated. Same regional settings as your desktop.

3. SharePoint sync can sometimes cause partial file availability or locking, especially if the file is open or syncing during refresh.

Solution: check the files are fully synced and not open during refresh. Consider using SharePoint Online URLs directly in Power BI instead of local sync folders.

4. Even though you have re-saved the files, Excel files can still contain, hidden corrupted metadata, External links and Named ranges or formulas referencing deleted sheets.

Solution: Open the file --> Save As -->.xlsx . Please remove hidden sheets, External links, Pivot caches and
Named ranges.

Note: Use Power Query to clean and trim data before loading.

5. Use Enterprise Gateway if possible more robust than personal gateway. Check the gateway logs for more detailed error messages.

I hope this information helps. Please do let us know if you have any further queries.

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]

Busy times.

1.

Yes, files are like NDA highly confidential. Would make sense then why only this report fails then on refresh. 

2.

We recently updated the software, no difference. 

3.

Files are on a secure drive and all files are marked with the green v symbol to indicate synched. 

4.

All files are xlsx and do not contain hidden sheets. 

[v-dineshya]

Hi @DouweMeer ,

Thank you for the update.  It appears this issue might require deeper investigation from the Power BI support team. I recommend opening a Microsoft support ticket so they can trace the issue. To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Regards,

Dinesh

[DouweMeer]

I'm going to check internally how to best evaluate this issue considering the NDA nature of it. 

Excluding things that it isn't is already a step forward. Thanks for the info so far.

[v-dineshya]

Hi @DouweMeer ,

Thank you for the update. As you mentioned in your previous response, you are going to check internally  to evaluate this issue. Please provide ETA on this issue.  Please do let us know if you have any further queries.

Regards,

Dinesh

[DouweMeer]

Power BI Governance team asked IT team to have a review of the software status first before escalating. It hit a snag, so that takes a week more or so. In escalating phase, I'm not familiar with expected service level of response time there. You may know better. 

[v-dineshya]

Hi @DouweMeer ,

Thank you for the update. As you mentioned in your previous response, Power BI Governance team checking with IT team. Once you got update,  please keep us posted.

Regards,

Dinesh

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?