Quite often we see such errors as these while moving the system DB’s across drives or the restore failing for system DB (Model). SQL Server won’t be starting for you at this point in time which could be frustrating. Lifeline for us? The errorlog to indicate what actually is happening at the backend, and this is where you shall be reading the error as subjected.
The database ‘model’ is marked RESTORING and is in a state that does not allow recovery to be run.
2016-11-26 06:19:37.23 spid12s Error: 927, Severity: 14, State: 2.
2016-11-26 06:19:37.23 spid12s Database ‘model’ cannot be opened. It is in the middle of a restore.
First things first, start SQL Server in a minimally configured mode-
“sqlservr.exe -sInstanceName /T3608 -m” and once service is started, establish a connection with SQL Server via SQLCMD – “sqlcmd -E -S servername/instancename,port”
“1>” means we are connected to SQL Instance and then execute the below command (hit enter at end of each line)
1>Restore database Model with recovery
RESTORE DATABASE successfully processed 0 pages in 0.0410 seconds (0.000MB/Sec)
Kabooom! You’re done. Startup your SQL service and proceed with your tasks.