Error in add connection between database and microsoft visual studio 2010 RRS feed

  • Question

  • The error is network - related and instance - specified error occur while establishing a connection to SQL server.  The server was not found or was not accessible. Verify the instance name is correct and SQL server is configured to allow remote connections.( provider : SQL Network interfaces , error :26 - Error locating server/Instance specified ). The error is occur in windows 8. The SQL server is not shown in administration services.
    Friday, June 27, 2014 6:09 PM


  • Hello,

    For this error, please follow below steps:

    1.Make sure your database engine is configured to accept remote connections(if you are using remote connection)

    • Start > All Programs > SQL Server > Configuration Tools > SQL Server Surface Area Configuration

    • Click on Surface Area Configuration for Services and Connections

    • Select the instance that is having a problem > Database Engine > Remote Connections

    • Enable local and remote connections

    • Restart instance

    2. Check the SQL Server service account

    • If you are not using a domain account as a service account (for example if you are using NETWORK SERVICE), you may want to switch this first before proceeding

    3. If you are using a named SQL Server instance, make sure you are using that instance name in your connection strings in your application:

    • Usually the format needed to specify the database server is machinename\instancename

    • Check your connection string as well

    You can also share your connection string with us, for all standard connection string, you can find then here:


    4. You may need to create an exception on the firewall for the SQL Server instance and port you are using

    • Start > Run > Firewall.cpl

    • Click on exceptions tab

    • Add the sqlservr.exe (typically located in C:\Program Files (x86)\Microsoft SQL Server\MSSQL.x\MSSQL\Binn, check your installs for the actual folder path), and port (default is 1433)

    • Check your connection string as well

    5. Check SQLBrowser; check that it is running. You may also need to create an exception in your firewall for SQLBrowser.

    6. Check that you have connectivity to the SQL Server.

    Note what you are using to connect: machine name, domain name or IP address? Use this when checking connectivity. For example if you are using myserver

    • Start > Run > cmd

    •netstat -ano| findstr 1433

    •telnet myserver 1433

    •ping -a myserver

    Check what ports are IP addresses are being returned.

    If this does not work for you, please let me know.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    • Marked as answer by Fred Bao Monday, July 7, 2014 3:22 AM
    Monday, June 30, 2014 2:14 AM