Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
I have a few reports that are failing to refresh automatically but do refresh successfully in Desktop. The reports refreshed without issue prior to adding adding a new query that is combining all docs in a sharepoint folder. I created a power automate flow to push the daily excel attachment from a report subscription to a sharepoint folder and have the folder pulled into the report. When I download the report and refresh, I need to run the refresh multiple times as it says errors are blocking the refresh but after a few times it runs all the way through and refreshes fully. Any ideas?
Here is the message from one of the reports.
Data source error{"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":"File contains corrupted data."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataFormat.Error"}}],"exceptionCulprit":1}}} Table: Query1.
Solved! Go to Solution.
Hi @bhenry ,
After reviewing your error message, I found the following key points:
1. DM_GWPipeline_Gateway_MashupDataAccessError: this usually indicates that there is an error accessing the data source from the gateway.
2. File contains corrupted data: This indicates that the file fetched from the SharePoint folder may have data corruption issues.
Here are some of the solutions I have provided for you:
1. See to check if the file is corrupted as it can be refreshed normally before adding a new query, it is possible that after adding a new query, there is an issue with the file format, you can manually download the SharePoint file to see if there is any corruption or formatting issue.
2 Verify Gateway Settings: Ensure that the gateway on the server has normal access to the SharePoint folder and that there are no problems with the gateway's permission settings.
3 Data format check: Verify that the newly added query is processing the files in SharePoint correctly and that all files are formatted as expected by Power BI.
Finally, you can try manually republishing the report on Power BI Desktop to see if it refreshes properly.
Below is the documentation I found for you, I hope this helps you resolve your issue, your issue is most likely with incorrect data after the merge.
Solved: DM_GWPipeline_Gateway_MashupDataAccessError - Microsoft Fabric Community
Solved: DM_GWPipeline_Gateway_MashupDataAccessError - Microsoft Fabric Community
Hope it helps!
Best regards,
Community Support Team_ Tom Shen
If this post helps then please consider Accept it as the solution to help the other members find it more quickly.
Hi @bhenry ,
After reviewing your error message, I found the following key points:
1. DM_GWPipeline_Gateway_MashupDataAccessError: this usually indicates that there is an error accessing the data source from the gateway.
2. File contains corrupted data: This indicates that the file fetched from the SharePoint folder may have data corruption issues.
Here are some of the solutions I have provided for you:
1. See to check if the file is corrupted as it can be refreshed normally before adding a new query, it is possible that after adding a new query, there is an issue with the file format, you can manually download the SharePoint file to see if there is any corruption or formatting issue.
2 Verify Gateway Settings: Ensure that the gateway on the server has normal access to the SharePoint folder and that there are no problems with the gateway's permission settings.
3 Data format check: Verify that the newly added query is processing the files in SharePoint correctly and that all files are formatted as expected by Power BI.
Finally, you can try manually republishing the report on Power BI Desktop to see if it refreshes properly.
Below is the documentation I found for you, I hope this helps you resolve your issue, your issue is most likely with incorrect data after the merge.
Solved: DM_GWPipeline_Gateway_MashupDataAccessError - Microsoft Fabric Community
Solved: DM_GWPipeline_Gateway_MashupDataAccessError - Microsoft Fabric Community
Hope it helps!
Best regards,
Community Support Team_ Tom Shen
If this post helps then please consider Accept it as the solution to help the other members find it more quickly.
Thanks Tom.
1. I found out there one of our IT Admins removed our past IT Director from a Teams site where many of the sources were held and that was causing the break in access to the data. He was the Admin that granted me access and did not require credentials in the datasource. We have added him back in and reset his permissions which has fixed the issues.
2. The corrupted data is coming from a Sharepoint Folder and documents that are pushed there from a Power Automate flow that gets a daily email and pushes the attached report (xlsx file) into the folder each day when it arrives in my inbox. It seems that once I open that new file in excel online the corrupted data error goes away and the datflow that is combining all of these daily reports works again. I am looking at what I need to do to fix that so I don't need to manually open the file each day
User | Count |
---|---|
24 | |
21 | |
11 | |
11 | |
10 |
User | Count |
---|---|
50 | |
31 | |
20 | |
18 | |
15 |