SQLLocalDB.exe info - returns error code 15100, etc

Thanks for the reply Paul. I have also removed all older SQL installs, but to get information on a particular LocalDB server instance using the SqlLocalDB.exe utility, I had to install the 2017 version. For instance I can now get information on an instance of SQLLocalDB (2016 version) that I created and called 'TAS_LocalDB_V13' using the command -

SqlLocalDB i TAS_LocalDB_V13

But, since there are now two versions of SQLLocalDB installed, there are two executables named SqlLocalDB.exe. The one that will run depends on the system environment path variable. I had to edit the path variable so that the path to SqlLocalDB.exe appearing first in the list was the 2017 version (which works).

Note - even though the i command in 2016 version does not work, other important commands like 'c' to create a server instance do work.

I fixed this by removing all traces of SQL from my machine and re-installing only what I needed (2016 in my case). Basically, search for "SQL" in Control Panel and remove whatever shows up.

I think this has to do with having multiple versions installed, and/or corruption happening when you update them, because:

• I had SQL components ranging from 2008-2017 installed (both standard and express), and,
• the problem started happening right after I applied the latest cumulative updates, which were mainly for SQL 2016.

UPDATE: it looks like the fix for this is closer to: re-install 2016 and install the 2017 sqllocaldb - no need to clean up other versions as I did. See Victor's subsequent post as well as my comment there.