Cannot start the LocalDB instance from Visual Studio 2013 on Windows 10. Posting here cause I finally got an error log that may indicate why the LocalDB instance will not start.
Deleted the LocalDB instance, including the folders, and tried to start the automatic instance (localdb)\v11.0 from VS2013. The error log references files that do not exist on my machine in path: e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\
Looking for help from SQL Server experts where these paths might be coming from. I have tried reinstalling and repairing SQL Server and Visual Studio with no luck. Thinking these paths might be buried in the registry or a config file and need to be purged manually.
This is the error log:
2018-07-27 16:52:02.91 spid5s Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\110\LocalDB\Binn\\ftimport.dll'.
2018-07-27 16:52:02.91 Server CLR version v4.0.30319 loaded.
2018-07-27 16:52:02.91 spid9s Starting up database 'mssqlsystemresource'.
2018-07-27 16:52:02.91 spid11s Server local connection provider is ready to accept connection on [ \\.\pipe\LOCALDB#55BBB5AB\tsql\query
].
2018-07-27 16:52:02.91 spid11s Dedicated administrator connection support was not started because it is disabled on this edition of SQL
Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2018-07-27 16:52:02.92 spid9s The resource database build version is 11.00.7001. This is an informational message only. No user action
is required.
2018-07-27 16:52:02.94 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2018-07-27 16:52:02.94 spid9s Starting up database 'model'.
2018-07-27 16:52:03.07 spid5s Error: 17204, Severity: 16, State: 1.
2018-07-27 16:52:03.07 spid5s FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf
for file number 0. OS error: 21(The device is not ready.).
2018-07-27 16:52:03.07 spid5s Error: 5120, Severity: 16, State: 101.
2018-07-27 16:52:03.07 spid5s Unable to open the physical file "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf".
Operating system error 21: "21(The device is not ready.)".
2018-07-27 16:52:03.10 spid9s Error: 17204, Severity: 16, State: 1.
2018-07-27 16:52:03.10 spid9s FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\model.mdf
for file number 1. OS error: 21(The device is not ready.).
2018-07-27 16:52:03.10 spid9s Error: 5120, Severity: 16, State: 101.
2018-07-27 16:52:03.10 spid9s Unable to open the physical file "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\model.mdf".
Operating system error 21: "21(The device is not ready.)".
2018-07-27 16:52:03.18 spid9s Error: 17207, Severity: 16, State: 1.
2018-07-27 16:52:03.18 spid9s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while
creating or opening file 'e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2018-07-27 16:52:03.18 spid9s File activation failure. The physical file name "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf"
may be incorrect.
2018-07-27 16:52:03.18 spid9s Error: 945, Severity: 14, State: 2.
2018-07-27 16:52:03.18 spid9s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See
the SQL Server errorlog for details.