The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Thanks for quick response, We are matching all this required criteria’s but still we are facing same refresh and mashup exceptions error. Gateway version 3000.246.5
Hello @Nagireddy
Please see if any of these applies to your suitation :
Common Causes of Mashup Errors
1. Data Source Issues
• Errors may arise due to mismatched data types, invalid transformations, or unsupported operations (e.g., applying an operator to incompatible data types like `Number` and `Record`).
• Problems with data quality, such as null values or missing keys, can also trigger these errors.
2. Gateway Problems
• If you’re using an on-premises data gateway, an outdated version can cause connectivity and refresh issues.
• Incorrect firewall settings or blocked ports can also prevent the gateway from functioning properly.
3. Staging and Metadata Failures
• Issues with staging Power Query or metadata updates in the Lakehouse SQL catalog can result in errors like “Failed to insert a table” or “Metadata refresh failure”.
4. Configuration Errors
• Misconfigured queries, such as incorrect parameter handling or M code logic, can lead to mashup exceptions.
• Deleting entities or tables without properly updating dependencies in the dataflow can also cause errors.
5. Performance or Resource Contention
• Intermittent failures may occur due to resource contention in shared environments, particularly for users without Power BI Premium.
thanks