Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
Kwarre35
Helper I
Helper I

DM_GWPipeline_Gateway_MashupDataAccessError: Problems Refreshing Semantic Model in Power BI Service

Hello, 

 

I have a semantic model, sourced from dataflows. Not sure why I am seeing this error. Refresh works in desktop. 

 

Not sure what else to try. I have tried:

1. Re-started On Premises Data Gateway

2. Re-credentialed to sources (Data Source Settings > Edit Permissions > Re-publish Desktop to Service, Re-trigger manual refresh

3. RE-checked that me as Admin, and the user that is testing, were added to the appropriate connections established, pointing through the Gateway we were using. 

 

Any thoughts?

 

 

 

 

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":"Microsoft SQL: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Class","detail":{"type":1,"value":"20"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"PowerPlatformDataflows"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"PowerPlatformDataflows"}},{"code":"Microsoft.Data.Mashup.ValueError.ErrorCode","detail":{"type":1,"value":"-2146232060"}},{"code":"Microsoft.Data.Mashup.ValueError.Message","detail":{"type":1,"value":"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"}},{"code":"Microsoft.Data.Mashup.ValueError.Number","detail":{"type":1,"value":"53"}},{"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: Fact View Activities.
Cluster URI: WABI-US-NORTH-CENTRAL-E-PRIMARY-redirect.analysis.windows.net
Activity ID: 75d0bbe7-3ad1-4f6e-8fe4-97bd29f547dc
Request ID: a6c602d5-1c40-16d6-de0b-912d7ad24a03
Time: 2024-05-31 19:50:40Z

2 REPLIES 2
v-jialongy-msft
Community Support
Community Support

Hi @Kwarre35 

 

Does @sergej_og 's method help you solve your problem? If solved then please consider Accept it as the solution to help the other members find it more quickly. If not, you can also check the following aspects:

  1. Verify SQL Server Configuration: Ensure that the SQL Server instance is configured to allow remote connections. This is crucial for the On-Premises Data Gateway to connect successfully. You can refer to the official documentation for guidance on how to enable remote connections:Configure remote access (server configuration option) - SQL Server | Microsoft Learn.

  2. Check Network Connectivity: The error message indicates a network-related issue. It's important to verify that there are no network barriers such as firewalls or network security groups blocking the connection from the gateway to the SQL Server. Specifically, ensure that the TCP port 1433 (default for SQL Server) is open.

 

 

 

 

 

Best Regards,

Jayleny

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

sergej_og
Super User
Super User

Hey @Kwarre35 ,
make sure that your connection string used in Desktop to connect to db is exactly the same you created in your gateway connections section.
Another approach, check your credentials on the dataflow side:

sergej_og_0-1717189342758.png


Regards

Helpful resources

Announcements
July 2024 Power BI Update

Power BI Monthly Update - July 2024

Check out the July 2024 Power BI update to learn about new features.

PBI_Carousel_NL_June

Fabric Community Update - June 2024

Get the latest Fabric updates from Build 2024, key Skills Challenge voucher deadlines, top blogs, forum posts, and product ideas.