Forum Discussion
Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
Hi,
Thank you in advance.
I have admin rights to everything mentioned below. My teammember has contributor rights.
I have a Fabric Link setup from Dataverse to Fabric Lakehouse Workspace 1. I then created a shortcut of a particular table to Fabric Lakehouse in Workspace 2. I am in need to create a sql connection through powerbi directly (without semantic model involvement). In this scenario, I can refresh easily but my teammember gets the following error. Please let us know how to resolve it. I have tried giving them admin access but still they get same error. Also, the teammember can query the data using lakehouse's sql endpoint.
Error : 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).
Hi,
Thank you for the assist 🙂
Even though my teammember had the right creds, authentication and viewer access to workspace 1, what worked for me was : giving the user "View ALL" access to the lakehouse in workspace 1. ( Or alternatively contributor access to Workspace 1).
2 Replies
v-echaithraCommunity Support
Hi Swapnil_CR ,
Thank you for reaching out to Microsoft Community.Although your teammate has access to the Lakehouse SQL endpoint, they may be missing underlying access to the source Lakehouse (Workspace 1) via the shortcut in Workspace 2.
Shortcuts in Fabric do not copy data, they point to the source data. So if your teammember doesn't have access to the original source Lakehouse in Workspace 1, then even if the shortcut exists in Workspace 2, they'll hit errors when querying through SQL.
Grant Your Team Member Access to the Source.
They must have at least Reader role on the Lakehouse in Workspace 1 or, at least item-level access to the specific table (but Workspace-level is easier). To do this go to Workspace 1, under Access tab, add your team member as a Viewer or Contributor
Alternatively, open the Lakehouse itself in Workspace 1 > use the Share feature to grant them direct access to the Lakehouse
Ensure that the shortcut target still exists and is correctly connected and the shortcut path hasn't changed (if someone renamed the table or folder in Workspace 1)If you’re using Get Data > SQL Server:
Use the SQL endpoint name (usually like workspaceName.lakehouseName.sql.fabric.microsoft.com)
Use AAD authentication in Power BI
Ensure Microsoft Entra (Azure AD) recognizes the user and grants access.
Thank you
Chaithra E.Hi,
Thank you for the assist 🙂
Even though my teammember had the right creds, authentication and viewer access to workspace 1, what worked for me was : giving the user "View ALL" access to the lakehouse in workspace 1. ( Or alternatively contributor access to Workspace 1).