Forum Discussion
Helper IIsemantic model refresh failure due to MashupFlight_SpecificErrorOnAggregatingText
Hello All,
I have created a report using SQL servers as a data source in Power BI desktop and created a report. Later i published it in Power BI service and scheduled refresh. Till this month 11th scheduled refresh works fine, now it is failing because of below 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":"We got an unexpected value for configuration property 'MashupFlight_SpecificErrorOnAggregatingText'; it had the type '(null)', but we were expecting the type 'System.Boolean'."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ErrorCode","detail":{"type":1,"value":"10760"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"Expression.Error"}}],"exceptionCulprit":1}}} Table: ObservationResults.
In Power BI desktop report refresh works fine but in service only it is failing to refresh. Did any one facing this issue.
Hey, everyone. Please try again. We were about to submit a ticket, but we decided to try refreshing one last time (Tuesday, August 19 at 11:30 MDT). It worked!
Please respond if the issue has been resolved for you as well. And may the odds be ever in your favor.
15 Replies
I am encountering exactly this same problem. I had to check that I didn't write the original post without remembering or something! It is literally the same for me:
- It's the same error message (except for table name)
- The report has been deployed and refreshing fine for a long time.
- The data refreshes fine on Power BI desktop.
- Refresh fails only in the online service.
- The problem started on 11 August.
Currently, I'm refreshing the report in Power BI Desktop locally and uploading it so users can get semi-up-to-date data.
- ibarrau
Super User
Hi. Is this the something that happened one time and worked again or is it failing now and it just won't work? sometimes the transformations fails. It could be capacity overload, it can be that the data source was working to much when requested, etc. Those failures are one from time to time.
If this is totally failing each time you refresh it in service, then do the following.
To make sure there is no error in the transformations, let's do a check. Open power bi desktop. Go to queryeditor/transformdata. Open the tables one by one selecting all the columns and filtering by "Keep Errors". Make sure there is no row for each one. If there are no error rows at any table, then it's something with mysql and power bi service. Otherwise, you can have an error in the ETL. Sometimes power bi desktop shows warnings after apply and refresh that will be errors in Service.
I hope that helps,
Ynr225Hi ibarrau ,
- Thanks for the response! Refresh is failing every scheduled refresh in Power BI. I checked in Fabric capacity metrics app, it's usage is only 50%.
- As you suggested I opened the report in Power BI desktop and opened the query transformation and filtered with errors and I don't see any errors in it. Refresh is perfectly working in Power BI desktop. Don't know suddenly the refresh stops working in service after 11th of this month.
v-menakakotaCommunity Support
Hi Ynr225 ,
Thanks for reaching out to the Microsoft fabric community forum.
I would also take a moment to thank ibarrau , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
This could be related to a recent change in the Power BI Service affecting how certain mashup configurations are handled (MashupFlight_SpecificErrorOnAggregatingText). I’d recommend the following next steps:Publish the same report and dataset to a different workspace and try a scheduled/manual refresh to see if the issue persists.
Check Gateway and Data Source Settings, If using an On-premises data gateway, ensure it’s on the latest version and revalidate the connection in the service.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Community Support Team
I am facing the same issue.
Each time I modify the table and try to refresh in Power BI service, same error is thrown for a different table. These tables don't even have Boolean columns. Hopefully, the issue is resolved soon.
- Shubham_rai955
I am also running into this exact issue and it seems to have started recently. Refresh in Power BI Desktop works fine, but in the Service the scheduled or manual refresh fails with the same "MashupFlight_SpecificErrorOnAggregatingText "error.
From what I have gathered, this is not caused by your model or query logic but rather something Microsoft flipped in the Service environment. A few things that helped me keep data flowing in the meantime: refresh in Desktop and republish the dataset, update and rebind the on-prem gateway if you use one, and try publishing to another workspace to see if the error is consistent. Some users suggest adjusting Group By steps that aggregate text columns, but even that may not fix it since the bug is on the Service side.
Best bet is to open a support ticket with Microsoft and include the Activity ID so they can link it to the ongoing incident. Hi,
We have the same issue, starting from the same day. We didn't change anything on our side, and the data is the same as previously.
have you found a solution already?I am also encountering this same issue which started on August 11th. Please get someone to look into this!
Hey, everyone. Please try again. We were about to submit a ticket, but we decided to try refreshing one last time (Tuesday, August 19 at 11:30 MDT). It worked!
Please respond if the issue has been resolved for you as well. And may the odds be ever in your favor.
Why is this marked as solved? This is still broken for us too and manually refreshing is not a solution. Any updates from anyone else on this?
- v-menakakota
Hi Admin9k ,
The solution is accepted by the person who has raised the thread, could you please let us know if you are facing the same issue please reply here or else create a new ticket.
Best Regards,
Community Support Team.
