Hi,
I tried to install a new instance of SQL Express Server 2014 on our Windows 2012 R2 Server but it stopped, displaying a message about cpu64, sorry I cannot remember the full details, eventually I had to crash out of the installation.
The first error message I can see in the Event Viewer is:
FCB::Open failed: Could not open file E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\MSDBData.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
Followed by:
FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\MSDBLog.ldf'. Diagnose and correct the operating system
error, and retry the operation.
The errorlog shows the following:
2016-01-08 14:07:17.08 spid10s Error: 17204, Severity: 16, State: 1.
2016-01-08 14:07:17.08 spid10s FCB::Open failed: Could not open file E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\MSDBData.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2016-01-08 14:07:17.08 spid10s Error: 5120, Severity: 16, State: 101.
2016-01-08 14:07:17.08 spid10s Unable to open the physical file "E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\MSDBData.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2016-01-08 14:07:17.08 spid15s Server is listening on [ 'any' <ipv4> 56850].
2016-01-08 14:07:17.08 spid15s Server local connection provider is ready to accept connection on [\\.\pipe\SQLLocal\HOTH ].
2016-01-08 14:07:17.08 spid10s Error: 17207, Severity: 16, State: 1.
2016-01-08 14:07:17.08 spid10s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\MSDBLog.ldf'.
Diagnose and correct the operating system error, and retry the operation.
2016-01-08 14:07:17.08 spid15s Server named pipe provider is ready to accept connection on [\\.\pipe\MSSQL$HOTH\sql\query ].
2016-01-08 14:07:17.09 spid10s File activation failure. The physical file name "E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\MSDBLog.ldf" may be incorrect.
2016-01-08 14:07:17.09 spid15s 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.
2016-01-08 14:07:17.09 spid15s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2016-01-08 14:07:17.09 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This
is an informational message. No user action is required.
2016-01-08 14:07:17.10 spid12s The resource database build version is 12.00.2000. This is an informational message only. No user action is required.
2016-01-08 14:07:17.11 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/PN-SERVER.pnsl.local:HOTH ] for the SQL Server service. Windows return code: 0x21c7, state: 15.
Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been
manually registered.
2016-01-08 14:07:17.11 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/PN-SERVER.pnsl.local:56850 ] for the SQL Server service. Windows return code: 0x21c7, state:
15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not
been manually registered.
2016-01-08 14:07:17.18 spid12s Starting up database 'model'.
2016-01-08 14:07:17.18 spid12s Error: 17204, Severity: 16, State: 1.
2016-01-08 14:07:17.18 spid12s FCB::Open failed: Could not open file E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\model.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2016-01-08 14:07:17.19 spid12s Error: 5120, Severity: 16, State: 101.
2016-01-08 14:07:17.19 spid12s Unable to open the physical file "E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\model.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2016-01-08 14:07:17.19 spid12s Error: 17207, Severity: 16, State: 1.
2016-01-08 14:07:17.19 spid12s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\modellog.ldf'.
Diagnose and correct the operating system error, and retry the operation.
2016-01-08 14:07:17.19 spid12s File activation failure. The physical file name "E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\modellog.ldf" may be incorrect.
2016-01-08 14:07:17.19 spid12s Error: 945, Severity: 14, State: 2.
2016-01-08 14:07:17.19 spid12s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2016-01-08 14:07:17.19 spid12s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
Since then I have tried repairs but they tell me that the database is not in a condition in which it can be repaired.
The path to my SQL installation is:
E:\Program Files\Microsoft SQL Server\MSSQL12.HOTH
I have tried this:
http://serverfault.com/questions/447808/sql-server-express-service-is-not-starting
But it doesn't return any information:
1> SELECT name, physical_name, state_desc FROM sys.master_files ORDER BY databas
e_id;
2> go
name
.physical_name
.state_desc
--------------------------------------------------------------------------------
------------------------------------------------.-------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
---------------------------------------------------------------------.----------
--------------------------------------------------
(0 rows affected)
I already have an instance of SQL working on the server so do not want to do a complete uninstall of SQL.
Can anyone help?
Thanks
alamb200