Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hello everyone,
I have a semantic model in PowerBI.com that is refreshed by a Pipeline setting in Data Factory. The error is the following: DM_GWPipeline_Gateway_MashupDataAccessError.
This is the full 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":"<ccon>Timeout expired. The timeout period elapsed prior to completion of the operation.</ccon>"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.HostingError.Reason","detail":{"type":1,"value":"Timeout"}}],"exceptionCulprit":1}}} Table: Query1.
Does anyone have an idea of what could be wrong? It started today and sometimes succeeds but other times doesn't.
Thanks
Solved! Go to Solution.
Hi @julsr ,
This error, DM_GWPipeline_Gateway_MashupDataAccessError, often indicates that the operation took too long to complete.
So I think you can try these steps below:
1. Review and optimize the queries in your semantic model to ensure they run efficiently. This might involve indexing, reducing the amount of data being processed, or simplifying complex queries.
2. Ensure that the gateway is not overloaded and has sufficient resources. Sometimes, restarting the gateway or the server where the gateway is installed can help.
3. Verify that there are no network issues between the data source and the gateway. Stable and fast network connectivity is crucial for timely data refreshes.
4. If possible, schedule the refresh during off-peak hours when the load on the data source and network is lower.
Best Regards
Yilong Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @julsr ,
This error, DM_GWPipeline_Gateway_MashupDataAccessError, often indicates that the operation took too long to complete.
So I think you can try these steps below:
1. Review and optimize the queries in your semantic model to ensure they run efficiently. This might involve indexing, reducing the amount of data being processed, or simplifying complex queries.
2. Ensure that the gateway is not overloaded and has sufficient resources. Sometimes, restarting the gateway or the server where the gateway is installed can help.
3. Verify that there are no network issues between the data source and the gateway. Stable and fast network connectivity is crucial for timely data refreshes.
4. If possible, schedule the refresh during off-peak hours when the load on the data source and network is lower.
Best Regards
Yilong Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
@julsr , Seem like on-premise gateway is offline or not rechable
On Power Bi Service -> Setting icon (Right Top) -> Manage Connections and Gateways -> Check if the Gateway is up and running
Upgrate the gateway to latest version
Increase timeout.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Fabric update to learn about new features.
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 |