Forum Discussion
Continued ContributorError when Pipeline refreshes semantic model
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.