Forum Discussion
Same error different files file contains corrupted data, value -2147467259
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
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
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
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.
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
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.
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
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.
