Invalid version of parent instance of LocalDB: MSSQL13E.LOCALDB

Question

I can not add the database on the developer's machine. I am running win 10, visual studio 2015. I re-installed SQL Server 2016 twice, the last time the firewall shut down, all of which gave green labels at the end.

While I can create databases in VS2015 SQL object Explorer. I cannot add an SQL (S) database to my projects through the solution analyzer.

Every time I try to add a database to the project, I get event 527 SQLLocalDB 12.0 Invalid version of the parent instance of LocalDB: MSSQL13E.LOCALDB

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

Also make sure that it uses the correct ports as ( Why am I getting "Can't connect to server - network error or specific instance"? )

I think that SQL is installed correctly, but something does not allow me to add databases (perhaps because some root database is missing or I'm not sure if it is not exported to SQL, but since the error says there are no seams in some DB

Answer 1

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

No need to reinstall or reboot.

Answer 2

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

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

Ty to indicate the key HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft SQL Server\UserInstances

Answer 3

I needed to change my installation of Microsoft SQL Server LocalDB 2016 Express to 2014, so I uninstalled 2016 and then installed 2014. After that, I received the following error when I ever tried to connect the database:

Version of parent instance of LocalDB is not valid: MSSQL13E.LOCALDB

To fix the problem, I deleted all references to Microsoft SQL Server 2016 from my computer and then deleted the associated GUIDs from the following registry location, rebooted, installed 2014 LocalDB, and everything was fine:

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

Answer 4

This happened to me when my LocalDB was updated (probably by Visual Studio installer)
I recreated the instance using the following steps:

 λ 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. 

Answer 5

Remember to update the register:

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

Check out .DEFAULT

I have to do this because it was wrong and needs to work in Windows Server 2012.