So I've been struggling on this for the past few days. I cannot connect to a SQL Server 2017 (14.0.1000.169) LocalDB shared instance. I've been searching and reading all over the net why but could not find any answer that worked.

I tried on a laptop that previously had some SQL Server Express and stuff that I all have uninstalled. And also on a fresh Win10 VM. Both always have the same error.

Which is

Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : Named Pipes Provider: Could not open a connection to SQL Server [2]. . Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : Login timeout expired. Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..

This error is from SQLCMD but I've also tried with SSMS or visual studio connection string.

I tried connecting with the owner of the instance and could not. Also tried with a SQL Login with sysadmin right and could not.

I can only connect with the pipe name.

I also tried everything from these links




If someone can explain to me why I can't connect or what I didn't understand that would be amazing.

thanks for your time.

  • is your instance "running" on services.msc? How is your Protocols on "QL Server Network configuration" on sql server configuration manager ? – Racer SQL Sep 18 at 20:16
  • @RacerSQL My instance is running I can see it with Sqllocaldb.exe -i, and unless I am mistaken, there's no service running for LocalDB. The same can be said for SQL configuration manager. – Leojet Sep 18 at 20:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.