Visual Studio 2013 does not start SQL Server LocalDB instances

[christaylor192]

Have a problem with only Visual Studio 2013 on Windows 10. Calls to start the LocalDB instance fail with:

• A popup indicating "Your SQL Server installation is either corrupt or has been tampered with (Unknown package id). Please uninstall then re-run setup to correct this problem"
• Output indicating: "Start of LocalDB instance "v11.0" failed because of the following error: Error occurred during LocalDB instance startup: SQL Server process failed to start."
• Event log indicating: "Windows API call WaitForMultipleObjects returned error code: 575. Windows system error message is: {Application Error} The application was unable to start correctly (0x%lx). Click OK to close the application. Reported at line: 3728. "

I have confirmed this is isolated to Visual Studio 2013 on Windows 10. Visual Studio 2010 on Windows 10 can start the LocalDB instance. Visual Studio 2013 on Windows 7 can start the LocalDB instance.

Things I have tried:

• I have tried the following SQL Server Local DB version with no success: 2012, 2012 SP2, 2014, 2014 SP1, 2016.
  
• I have tried the fix to delete and create the LocalDB instance with no success.
• I have ensured the LocalDB instance folders are deleted.
• I have ensured the LocalDB instance folders have the correct permissions when created.
• I can start all LocalDB instances from the VS2013 developer command prompt.
• I can logon to all LocalDB instances from SSMS.
• I have tried my own instances rather than the automatic instances included with each LocalDB version.
• I have uninstalled and reinstalled all SQL Server LocalDB versions.
• I have repairs and uninstalled and reinstalled VS2013 update 5.

Observations:

• If I delete the local instance and try to connect to an automatic instance (ie (localdb)\v11.0) in VS2013 I see the instance folder is created and populated with 6 files (master.mdf, mastlog.ldf, model.mdf, modellog.ldf, msdbdata.mdf, msdblog.ldf).
• Thus it appears the permissions are correct, and the automatic instance is being created... although it is missing a bunch of files that other instances have (tempdb.mdf, templog.ldf, log.trc, entrophy.bin) which are usually created when the instance is started.
• If I try to start the instance after the failure in VS2013 I get the following error: "Start of LocalDB instance "v11.0" failed because of the following error: Error occurred during LocalDB instance startup: SQL Server process failed to start."
• The instance error log contains errors relating to E drive. I do not have an E drive and never have.

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.

Continue reading...