Forum Discussion
Helper IIsemantic model refresh failure due to MashupFlight_SpecificErrorOnAggregatingText
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.
Super UserHi. 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,
Helper IIHi 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- Ynr225
Hi v-menakakota ,
I already tried your approach, even after publishing in different workspace I am getting same error message while refreshing.
Yes I am using on premises data gateway of latest version but no luck.
- v-menakakota
Hi Ynr225 ,
Since,you’ve already tested across different workspaces and verified the latest gateway version, it looks less like a configuration issue and more like a service-side problem. At this point, the best next step would be to open a Microsoft Support ticket and provide.Please refer below link on how to raise a contact support or support ticket.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Community Support Team.