SQL SERVER – Resolving SQL Server Connection Errors – SQL in Sixty Seconds #030 – Video

One of the most famous errors related to SQL Server is about connecting to SQL Server itself. Here is how it goes, most of the time developers have worked with SQL Server and knows pretty much every error which they face during development language. However, hardly they install fresh SQL Server. As the installation of the SQL Server is a rare occasion unless you are DBA who is responsible for such an instance – the error faced during installations are pretty rare as well.

I have earlier written an article about this which describes how to resolve the errors which are related to SQL Server connection. Even though the step by step directions are pretty simple there are many first time IT Professional who are not able to figure out how to resolve this error. I have quickly built a video which is covering most of the solutions related to resolving the connection error.

In the Fix SQL Server Connection Error article following workarounds are described:

  1. SQL Server Services
  2. TCP/IP Settings
  3. Firewall Settings
  4. Enable Remote Connection
  5. Browser Services
  6. Firewall exception of sqlbrowser.exe
  7. Recreating Alias

Related Tips in SQL in Sixty Seconds:

What would you like to see in the next SQL in Sixty Seconds video?

Reference: Pinal Dave (https://blog.sqlauthority.com)


Database, SQL in Sixty Seconds, SQL Scripts, SQL Server Management Studio
Previous Post
SQL SERVER – Order By Numeric Values Formatted as String
Next Post
SQL SERVER – Last Two Days to Get FREE Book – Joes 2 Pros Certification 70-433

Related Posts

7 Comments. Leave new

  • Very helpful post. When I was starting my carrer, sometimes I had problems needing resolve like in this video. Shame there wasn’t video like this then :).

    Anyway, have you ever encountered problem with debugging alone? One day, I wanted debug same cursor on local serwer instance and I encountered error message: “Unable to start T-SQL Debugging. Could not connect to computer ‘(local)’. […]”
    I was using Windows authentication and ‘(local)’ as server name. It turn out that debugging is only available, when server name contains computer name explicitly.

  • RadhaKrishna k
    January 23, 2013 5:59 pm

    Hi, i am getting this type of erroe when i am adding new column in table and storedprocdure .
    Msg 206, Level 16, State 2, Procedure usp_Testimonial_Insert, Line 26
    Operand type clash: text is incompatible with datetime.

    Please help me on this problem

  • TITLE: Connect to Server

    Cannot connect to localhost.


    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) (Microsoft SQL Server, Error: 2)

    For help, click:



  • thank you very much :*
    you helped me a lot… :D

  • Abdallah Sajid Abubakar
    May 27, 2015 11:50 am

    I wished u provided for me a step by step written solution of solving the sql error not in video

  • Wow. Thank you.

  • to the next guy.
    I was having this problem while trying to connect to a SQL AlwaysOn listener.

    My issue was that when the listener was configured they changed the default port number from 1433 to something else

    in order to sucessfully connect to it use: listener,port


Leave a ReplyCancel reply

Exit mobile version