error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53

  • I installed an instance last night and was able to connect successfully and do configurations. I woke up this morning to the connection error when trying to log in with SSMS.

    I've:

    Verified shared memory, named pipes, tcp/ip are enabled.

    Telnet provides a blank screen when I 'telnet servername 1433'

    I can connect via sqlcmd.

    Do I have to add a start up parameter.

  • What is the error message you are getting?

    M&M

  • ...

    TITLE: Connect to Server

    ------------------------------

    Cannot connect to 3MRASSDB1.

    ------------------------------

    ADDITIONAL INFORMATION:

    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: 53)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476

    ------------------------------

    BUTTONS:

    OK

    ------------------------------

  • Is the service running?

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

  • Did you check if that server name is correct?

    If you are not sure, you should be able to get that from the error log.

    M&M

  • It is correct. I can query @@servername through sqlcmd and get the correct servername.

    edit: yes the service is running. I can connect via sqlcmd

  • Also, I've tested installing additional instances and they all have this same problem.

  • check for authentication mode

  • thanks for the idea, wouldn't it be a different error if it were an authentication error?

  • Were you able to check contents of SQL Server error log in that install folder location. Do you see any errors etc.

    M&M

  • Sorry, busy day. At some point between 22:30 last night and 06:30 this morning someone changed the servername. A one letter difference

  • Okay that was funny ....

    I just want share one problem faced by me. this morning....

    last night I were playing with network options and today I got one error while establishing connection with ssms

    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)

    that was due to VIA protocol enabling. I just disable that and able to connect ssms.

    actually VIA Pro. for special VIA network for big scenario

  • Hi,

    VIA is already disable in my SQL Server, they also i am not able to connecting.

    My main issue is i am able to connect through IP not Instance name...... I want to connect through Instance name....

Viewing 13 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic. Login to reply