SQL LocalDb Automatic Instance Startup Failure when called from Visual Studio 2013, but not SQL Server Management Studio

Question

Per MSDN Docs: http://msdn.microsoft.com/en-us/library/hh510202.aspx

LocalDB supports two kinds of instances: Automatic instances and Named instances.

Answer 1

I had the same problem. One of the problem may be an older installed version of this product. Try to delete the database instances which are located in the following folder:

C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\VeeamEndPoint

After that it works for me!!!

Answer 2

I had the same issue. I resolved it by deleting and recreating the instance from command line:

1. Open the command line
2. Delete the session by typing: sqllocaldb delete "v11.0"
3. Recreate the instance with: sqllocaldb create "v11.0"

The new instance allows auto creation, and solves the issue.

The solution was taken from: http://answers.flyppdevportal.com/categories/sqlserver/sqlexpress.aspx?ID=8bcb5f1e-0240-4df3-8a5e-7e3e73e1c45b

Answer 3

I had the same problem on VS2015 and SQL2016 the problem my dev station is a laptop, project explorer i think uses tcpip connection, while SQLeplorer local file or so.

It worked after i made sure that SQL used the Network card, and that it had a cable plugged in (so SQL could server the request over TCP using that IP) which it couldnt over wifi (by default?)