Forum Discussion
powerbi virtual network gateway
Hi surbhi
Just checking in on your progress with connecting the semantic model to the VNet Gateway. Were you able to map the Azure Blob Storage source correctly under the gateway settings and align the path used in Power BI Desktop?
Let me know if you’re still running into issues happy to help troubleshoot further if needed!
yes i was able to create and connect to semantic model with gateway but my scheduled refresh is failing with below error:
Data source 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're sorry, an error occurred during evaluation."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}}],"exceptionCulprit":1}}} Table: BackupJobs (A).
Cluster URI: WABI-US-NORTH-CENTRAL-G-PRIMARY-redirect.analysis.windows.net
Activity ID: 4d83b86f-514f-4235-9c3d-5972633172f8
Request ID: a3bd99f6-a0a0-196e-3ed8-e5aa7225f587
Time: 2025-08-26 07:49:54Z
not getting what exactly it is
Hi surbhi
If you're seeing the error DM_GWPipeline_Gateway_MashupDataAccessError with code -2147467259, here are some targeted steps that may help resolve it:
- Ensure the On-Premises Data Gateway is online, updated, and not overloaded. Performance issues or outdated versions can cause mashup failures.
- If using a VNet Gateway, verify that the network route to the data source is stable and not experiencing latency or drops.
- Try refreshing the dataset manually in Power BI Service. If it works manually but fails on schedule, the issue may be related to refresh.
- Refresh the dataset in Power BI Desktop. If it succeeds locally but fails in the service, the problem likely lies with gateway configuration or service-side limitations.
- Isolate the BackupJobs (A) query and remove complex transformations such as joins, merges, or nested filters.
- Test a minimal version of the query in Power BI Desktop and publish it to see if it refreshes successfully in the service.
- Some users have resolved this by rebooting the data source server, not just the gateway. If feasible, this may help clear stale connections or memory locks.
Hope this helps !!
our data source is azure blob storage with private endpoints. NO idea how to restart 0r refresh that. I refreshed the reports in desktop version and it is running fine. But whenever i tried to refresh semactic model in app service getting this mashup error
Hi surbhi
- When using Azure Blob Storage with private endpoints, refreshing the semantic model in an app service can fail due to network or authentication issues.
- Ensure the app service has proper network access to the private endpoint, verify that OAuth credentials or access keys are valid and not expired, and confirm that the data source connection in the service is correctly configured to use those credentials.
- Also, check if a gateway or managed identity is required for the app service to access the private endpoint securely.
- Restarting or refreshing typically involves re-authenticating the connection and ensuring the app service can reach the storage account through the private endpoint.
Reference : https://learn.microsoft.com/en-us/power-bi/connect-data/refresh-scheduled-refresh