Forum Discussion

Shivakumarh's avatar
Shivakumarh
Icon for Helper I rankHelper I
1 year ago
Solved

Unable to connect to SQL server in Power bi desktop

While connecting i am getting the below error message:- We encountered an error while trying to connect. Details: "Microsoft SQL: A network-related or instance-specific error occurred while est...
Need Help
  • Praful_Potphode's avatar
    Praful_Potphode
    11 months ago

    Hi Shivakumarh ,

     

    we need more information on this to help you further.can you follow below checklist and see if it works?

    • Use Azure Synapse Analytics connector
      Get Data > Azure > Azure Synapse Analytics
    • Enter correct server name
      yourworkspace.sql.azuresynapse.net (for dedicated pool)
      yourworkspace-ondemand.sql.azuresynapse.net (for serverless pool)
    • Choose authentication method
      - Azure Active Directory - Organizational Account
      - Basic (SQL username/password)
      - Windows (if domain-joined)
    • Clear cached credentials
      File > Options and settings > Data source settings > Clear Permissions
    • Test port connectivity.try below command in power shell.
    Test-NetConnection -ComputerName yourworkspace.sql.azuresynapse.net -Port 1433

     

    • Test-NetConnection -ComputerName yourworkspace.sql.azuresynapse.net -Port 1433
      - Ping server to verify DNS resolution try below command in command prompt.
    ping yourworkspace.sql.azuresynapse.net
    • Check Synapse firewall settings
      Enable public network access
      Add your client IP to allowed list
      Enable “Allow Azure services to access this workspace”
    • Try Azure Data Studio for connection test
    • Download Azure Data Studio
    • Use .pbids file to force correct connector
      Create .pbids with server and connector settings
    • Verify workspace type and database context
    • Check for private endpoint configuration
      - Ensure you're on same VNet or using VPN
      - Configure private DNS zone if needed
    • Inspect Conditional Access Policies
      Confirm AAD policies aren’t blocking Power BI Desktop
    • Monitor Synapse logs for failed login attempts
      Use Azure Monitor or Diagnostic Settings in Synapse workspace

    Please give kudos or mark it as solution if it helps.

     

    Thanks and Regards,

    Praful

v-sgandrathi's avatar
v-sgandrathi
Icon for Community Support rankCommunity Support
11 months ago

Hi Shivakumarh,

 

Thank you for clarifying. From your description, it appears that the connection problem with Azure Synapse SQL in Power BI Desktop is likely due to network or firewall settings rather than an issue with credentials. The error “Named Pipes Provider, error: 40 – Could not open a connection to SQL Server” typically indicates Power BI cannot reach the Synapse endpoint over the network.

To address this, first check that you’re connecting through the right method in Power BI: go to Home > Get Data > Azure > Azure Synapse Analytics (SQL), and enter the fully qualified server name (like yourworkspace.sql.azuresynapse.net) in the Server field, without “https://” or any database name. Enter your database name if needed, select Import or DirectQuery, and choose the correct authentication method for your setup.

Next, confirm your network can reach the Synapse endpoint. You can use this PowerShell command to test connectivity: Test-NetConnection yourworkspace.sql.azuresynapse.net -Port 1433. If it fails, outbound traffic on port 1433 may be blocked by your firewall or VPN. Contact your network administrator or disconnect from the VPN to test again.

Also, review your Azure Synapse firewall settings in the Azure portal. Add your current client IP address under Networking > Firewall rules and save the changes. If you’re using a private endpoint, ensure your machine can access it.

If you need to check your credentials, use Azure Synapse Studio (web) or the Query editor in the Azure portal to connect and run a simple query like SELECT 1;. If that works, your credentials are fine and the issue is with network access.

Once you’ve followed these steps, try connecting again from Power BI Desktop.

Thank you.