Post reply

sqlserver2017 express

  • March 27, 2019 at 9:06 am

    #2033925

    Hi,

    SQL: sqlserver2017 express

    Error:
    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: SQL Network interfaces,error:26-Error locating server/Instance specified).

    Remote connections enabled and TCP/IP enabled.
    I am able to connect to the sql instance in the server without any issue but unable to connect to sql instance from out side of the server using SSMS.

    Any suggestions ?

    Thank you.

  • March 27, 2019 at 10:05 am

    #2033960

    Do you have the firewall enabled? If so, add an Inbound rule to allow port 1433 (or whatever port you are using if different than 1433). You could first try to disable the firewall and then if it works, add the rule.

  • March 27, 2019 at 10:41 am

    #2033969

    yes the firewall is already enabled  and we are able to connect to other sqlservers\instances .

  • March 27, 2019 at 10:45 am

    #2033970

    Please try to disable the firewall and attempt to connect again. Also, be sure that both TCP/IP and Named Pipes are enabled in the SQL Server Configuration Manager and then restart the database engine.

  • March 27, 2019 at 11:24 am

    #2033976

    adisql - Wednesday, March 27, 2019 10:41 AM

    yes the firewall is already enabled  and we are able to connect to other sqlservers\instances .

    Make sure you can ping the server and the server\instance name is correct. Then make sure the browser service is running or try specifying the port since this is an error you get with named instances. 

    Sue

  • March 27, 2019 at 11:28 am

    #2033977

    Sue_H - Wednesday, March 27, 2019 11:24 AM

    adisql - Wednesday, March 27, 2019 10:41 AM

    yes the firewall is already enabled  and we are able to connect to other sqlservers\instances .

    Make sure you can ping the server and the server\instance name is correct. Then make sure the browser service is running or try specifying the port since this is an error you get with named instances. 

    Sue

    Good point Sue, I forgot to ask\clarify that. If you are not using the default instance and have a named instance you will need to specify it as indicated by Sue.

Viewing 6 posts - 1 through 5 (of 5 total)

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