Forum Discussion
DM_GWPipeline_Gateway_MashupDataAccessError
Hey sometimes a scheduled refresh fails with the below error. The table is stored in lakehouse.
Manual refreshes right after the error always work. Is there a way to get rid of this error from ever happening?
An error occurred while processing the data in the semantic model.
Refresh failed:
Failure details: The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support.
{"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>Microsoft SQL: A transport-level error has occurred when receiving results from the server. (provider: SSL Provider, error: 0 - The specified data could not be decrypted.\r\n)</ccon>"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ErrorCode","detail":{"type":1,"value":"10478"}},{"code":"Microsoft.Data.Mashup.ValueError.Class","detail":{"type":1,"value":"20"}},{"code":"Microsoft.Data.Mashup.ValueError.ConnectionId","detail":{"type":1,"value":"b74c0d2a-5aff-42f5-8522-43ae87428443"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"SQL"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"<ccon>y64fka4vrlfepd6q3fai56rzwq-ala25fi3rk3uzhcrg3fbsoodqq.datawarehouse.fabric.microsoft.com;Dev_Data</ccon>"}},{"code":"Microsoft.Data.Mashup.ValueError.ErrorCode","detail":{"type":1,"value":"-2146232060"}},{"code":"Microsoft.Data.Mashup.ValueError.Message","detail":{"type":1,"value":"<ccon>A transport-level error has occurred when receiving results from the server. (provider: SSL Provider, error: 0 - The specified data could not be decrypted.\r\n)</ccon>"}},{"code":"Microsoft.Data.Mashup.ValueError.Number","detail":{"type":1,"value":"-2146893008"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}},{"code":"Microsoft.Data.Mashup.ValueError.State","detail":{"type":1,"value":"0"}}],"exceptionCulprit":1}}} Table: 7PaceData.
Hi rafaelr08,
Thank you for bringing this to the community, and a big appreciation to Akash_Varuna for sharing such a precise and helpful response!
As mentioned, the error DM_GWPipeline_Gateway_MashupDataAccessError is commonly linked to transient encryption or connectivity issues, particularly during scheduled refreshes involving Lakehouse or SQL-based sources. The super user has correctly highlighted the key factors and best practices to mitigate this.
Here are a few additional suggestions:
Use the refresh history and Fabric monitoring tools to identify if the error occurs at specific times or under load, which can help pinpoint service-level delays.
If multiple models or datasets are refreshing concurrently, consider staggering the schedules to reduce potential service contention.
If you're working with large volumes of Lakehouse data, explore Enhanced Refresh (if available in your workspace), which improves reliability through chunked data refresh and retry logic.
Since your source is a Fabric Lakehouse, gateway checks may not apply unless your model pulls data from external or hybrid sources. But if any other connections exist via on-premises gateways, ensure SSL certificates and trust chains are valid and up to date.
If this solution worked for you, kindly mark it as Accept as Solution and feel free to give a Kudos, it would be much appreciated!
Regards,
Sahasra
Customer Support Team – Microsoft Fabric Community.
5 Replies
Hi rafaelr08 This error is likely caused by transient connectivity or encryption issues with the Lakehouse table. To reduce occurrences, configure automatic retry attempts for scheduled refreshes and ensure network stability during refresh times. Verify the gateway setup, including SSL certificate validity, to avoid transport-level errors. If the problem persists, analyze server logs or escalate to Microsoft support for deeper troubleshooting.
Hi rafaelr08,
Thank you for bringing this to the community, and a big appreciation to Akash_Varuna for sharing such a precise and helpful response!
As mentioned, the error DM_GWPipeline_Gateway_MashupDataAccessError is commonly linked to transient encryption or connectivity issues, particularly during scheduled refreshes involving Lakehouse or SQL-based sources. The super user has correctly highlighted the key factors and best practices to mitigate this.
Here are a few additional suggestions:
Use the refresh history and Fabric monitoring tools to identify if the error occurs at specific times or under load, which can help pinpoint service-level delays.
If multiple models or datasets are refreshing concurrently, consider staggering the schedules to reduce potential service contention.
If you're working with large volumes of Lakehouse data, explore Enhanced Refresh (if available in your workspace), which improves reliability through chunked data refresh and retry logic.
Since your source is a Fabric Lakehouse, gateway checks may not apply unless your model pulls data from external or hybrid sources. But if any other connections exist via on-premises gateways, ensure SSL certificates and trust chains are valid and up to date.
If this solution worked for you, kindly mark it as Accept as Solution and feel free to give a Kudos, it would be much appreciated!
Regards,
Sahasra
Customer Support Team – Microsoft Fabric Community.
Hi rafaelr08,
We strive to make sure every issue gets addressed completely. If the previous answer helped, that’s great—please mark it as Accepted and consider giving it a Kudos.
Still facing issues? Just reply here and we’ll be right with you.
Thanks for being a valued part of the community,
Hi rafaelr08,
We wanted to follow up to see if our suggestion was helpful. Please let us know how things are progressing and if you are still encountering any issues.
If the response resolved your problem, you may mark it as the solution and give it a thumbs up to assist others in the community as well.
Thank you.
