39

I'm unable to add a database on a developer machine. I'm running win 10, visual studio 2015. I re-installed SQL server 2016 twice, last time with firewall disabled it all gave green marks in the end.

While i can create databases in VS2015 SQL server object explorer. I am unable to add a SQL database(S) to my projects, trough solution explorer.

Each time i try to add a database to a project i get event 527 SQLLocalDB 12.0 LocalDB parent instance version is invalid: MSSQL13E.LOCALDB

I've tried Start > Run > cmd > sqlcmd -L and it shows my SQLserver

Also made sure it uses the right ports as by (Why am I getting "Cannot Connect to Server - A network-related or instance-specific error"?)

i think that SQL is installed properly but that something is not allowing me to add databases (maybe because some root database?? is missing or so i am not sure i m not an export on SQL, but as the error says some DB seams missing ??

Community
  • 1
  • 1
Peter
  • 2,043
  • 1
  • 21
  • 45
  • think i solved it, it turns out the local network card was disconnected, while my developer laptop usually runs on WIFI, project explorer apparantly communicated over LAN not over wifi.. thus it couldnt find SQL. it seams to work now, keeping finger crossed as i have not yet tested to code against it. – Peter Oct 13 '16 at 17:31

6 Answers6

73

It happened to me when my LocalDB got updated (probably by Visual Studio installer)
I've recreated the instance using the following steps in PowerShell console:

λ SqlLocalDB delete MSSQLLocalDB
LocalDB instance "MSSQLLocalDB" deleted.

λ SqlLocalDB create MSSQLLocalDB
LocalDB instance "MSSQLLocalDB" created with version 13.1.4001.0.

λ SqlLocalDB start MSSQLLocalDB
LocalDB instance "MSSQLLocalDB" started.
Random
  • 4,519
  • 2
  • 38
  • 46
44

I had something similar and deleted any keys in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft SQL Server\UserInstances that did not have the correct ParentInstance key such as MSSQL13E.LOCALDB.

No need to reinstall or reboot.

David Ferenczy Rogožan
  • 23,966
  • 9
  • 79
  • 68
Dick de Reus
  • 779
  • 1
  • 7
  • 15
  • Bob-on, this. I had SQL 2016 Local DB listed in my "add remove", got shot of that, installed just the LocalDB components of SQL 2017 Express, hit this issue, removed a GUID-named key under that folder - all working :-) – Adam Houldsworth Nov 10 '17 at 13:55
21

I had the same problem for migrating from SQL LocalDb 2016 to 2017.

I simply changed the value of the ParentInstance key from MSSQL13E.LOCALDB to MSSQL14E.LOCALDB and it worked !

Ty for pointing me to the key HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft SQL Server\UserInstances

Softlion
  • 12,281
  • 11
  • 58
  • 88
10

I needed to change my install of Microsoft SQL Server LocalDB 2016 Express to 2014, so I uninstalled 2016 then installed 2014. After this I got the following error when ever I tried to attach a database:

LocalDB parent instance version is invalid: MSSQL13E.LOCALDB

To resolve the issue I uninstalled all mention of Microsoft SQL Server 2016 from my computer then deleted the related instance GUIDs from the following registry location, rebooted, installed 2014 LocalDB and all was good:

HKEY_USERS\.DEFAULT\Software\Microsoft\Microsoft SQL Server\UserInstances\
David Ferenczy Rogožan
  • 23,966
  • 9
  • 79
  • 68
Angrist
  • 147
  • 1
  • 9
0

I had the same problem after upgrading, Just delete the registry item and restart the OS. I deleted all folders under:

HKEY_USERS\.DEFAULT\Software\Microsoft\Microsoft SQL Server\UserInstances\

…and then restarted Windows.

Jeremy Caney
  • 7,102
  • 69
  • 48
  • 77
Mahdi Varzdar
  • 1
-2

Remember update the Register:

HKEY_USERS\.DEFAULT\Software\Microsoft\Microsoft SQL Server\UserInstances

Check .DEFAULT

I have to do that, because it was wrong and need it to work in Windows Server 2012.

Community
  • 1
  • 1
IsakMtz
  • 21
  • 5