none
Microsoft SQL Management Studio 2012

    Question


  • Im trying to use Microsoft SQL Server Management , but when I want to start connect to my database, it gives the error below :

    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) (.Net SqlClient Data Provider)

    How should I solve this problem


    • Edited by AshaB Tuesday, February 05, 2013 9:42 AM
    Tuesday, February 05, 2013 7:41 AM

Answers

  • Although, There are many reasons of SQL server connectivity issue. But I have setup an small checklist that helps me most of the time to find out the real cause of connectivity issue.

    1. Check SQL services are running

    2. Check SQL Browser service is running

    3. Check remote connections are enabled

    4. Network connectivity between database & application servers by TRACERT command

    5. Check TCP/IP protocol enabled at SQL server

    6. Check talent connectivity – telnet <IP address> <port no on SQL server running>

    7. Check UDP port 1434 is open or not on SQL Server

    8. Check firewall is running or not Check

    9. If firewall running, SQL Server & UDP port must be added in exception in firewall

    http://mssqlfun.com/2012/09/28/check-list-for-sql-server-connectivity-issue/


    Regards,
    Rohit Garg
    (My Blog)
    This posting is provided with no warranties and confers no rights.
    Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread.

    Wednesday, February 06, 2013 1:03 PM

All replies

  • This is a common error. SQL Server Books Online has a short tutorial that can help you resolve this. Tutorial: Getting Started with the Database Engine

    Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

    Tuesday, February 05, 2013 4:51 PM
  • Although, There are many reasons of SQL server connectivity issue. But I have setup an small checklist that helps me most of the time to find out the real cause of connectivity issue.

    1. Check SQL services are running

    2. Check SQL Browser service is running

    3. Check remote connections are enabled

    4. Network connectivity between database & application servers by TRACERT command

    5. Check TCP/IP protocol enabled at SQL server

    6. Check talent connectivity – telnet <IP address> <port no on SQL server running>

    7. Check UDP port 1434 is open or not on SQL Server

    8. Check firewall is running or not Check

    9. If firewall running, SQL Server & UDP port must be added in exception in firewall

    http://mssqlfun.com/2012/09/28/check-list-for-sql-server-connectivity-issue/


    Regards,
    Rohit Garg
    (My Blog)
    This posting is provided with no warranties and confers no rights.
    Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread.

    Wednesday, February 06, 2013 1:03 PM