Forum Discussion

steveelder's avatar
steveelder
New Member
10 years ago

SQL Connection error - Named Pipes

Hi all

first time poster , so be easy on me

When trying to connect to SQL Server ( all 2008 r2 ) i get the following error messages

This is only a problem on my production servers,,, test servers are fine. ...

 

Details: "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)"

 

So

Im running  Power BI as an admin

have the correct username/password

Have checked the SQL server is running and all services are good

Have checked to allow ports through on the servers firewall

Have checked to allow incoming connections in SQL

TCP/IP and Named are enabled on config manager

 

anything else ?

Need Help

13 Replies

  • karthik's avatar
    karthik
    Advocate I
    10 years ago

    Did you try connecting to the SQL Server from other applications e.g. Excel?

    Did you set "Allow Remote Connections to this server" property? Right click the server node from management studio--> Properties--> Connections. Check "Allow Remote Connections to this server" property is checked?

    Is your production server default/named instance? If named instance check if the SQL Server browser is running and ensure that you add SQLBrowser.exe as an exception in the firewall.

     

    • steveelder's avatar
      steveelder
      New Member
      10 years ago

      Similar error message when connecting through excel

      remote connections is enabled

      default instance 

      sqlbrowser service is stopped

       

      • Anonymous's avatar
        Anonymous
        Not applicable
        10 years ago

        Hi steveelder ,

        Do you use IP address or computer name to connect to the remote SQL Server default instance? According to the above error message, there are some proposals for you troubleshooting this issue.

        1. Make sure the machine that is running SQL Server is reachable. In other words, you are able to ping the server.
        2. Verify that the target SQL Server is listening on 1433 port, if you are connecting to a port other than TCP port 1433, you must also open the UDP port 1434 for the SQL Server Browser service.
        3. Use “IP address, port” or “tcp:computername” as server name to connect to SQL Server and check if it is successful.

        For more detailed troubleshooting steps, please review the following blog.

        http://social.technet.microsoft.com/wiki/contents/articles/2102.how-to-troubleshoot-connecting-to-the-sql-server-database-engine.aspx

        Thanks,
        Lydia Zhang

  • teckling's avatar
    teckling
    Regular Visitor
    10 years ago

    I am exactly the same problem and also on Win2008R2 (no SP1) running SQL2008.

     

    1. I can connect to \\10.1.1.130\c$ from my PC by providing Administrator credential

    2. I can remote desktop to 10.1.1.130 using Administrator credential

    3. But when get data via PowerBI I failed with exactly the same error message.

     

    My workaround now is to directly installed PowerBI inside the SQL2008 server. This seems to work - but I need to verify further.

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    I had the same problem and found the resolution for me was to set 1433 as the port for connection in the SQL configuration on the server. Once this was set it worked without issue.

     

     

    I was using PowerBI desktop december 2020 release and SQL Server 2016 running on Microsoft Server 2016.

     

    Hope this helps someone in the future looking for a resolution.