unable to start SQL instance

Question

unable to start SQL instance

Computer Gladiator 446

Hello, we upgraded from SQL 2005 express to SQL 2014 Express. The existing database is working fine and is accessible. We needed to create another instance and we are able to complete the process but there were errors. I apologize but did not make note of them. We cannot start the services. Event log has the following errors.....
id 7024 -The SQL Server (ACE2014) service terminated with the following service-specific error:
Cannot find object or property.
id 17120 - SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
id 17826 - Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
id 17182 - TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
id 17190 - Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.

Any assistance appreciated. Thank you

Accepted answer

4 additional answers

Your answer

Answer 1

Hi, I did not notice that until now. This server originally has SQL 2005 express to run Microsoft RMS. last July we upgraded the 2005 SQL to 2014 SQL successfully and has been running fine ever since. We were installing the SQL 2014 64bit version and we cleaned up the 64 bit version. Attempted to install an instance with SQL 2014 x86 version and ran into the same problem except the error log was simpler. It stated to remove the "sql server database engine services instance features" with error 0x851a001a.
I google the this error and the solution was to set the Database Engine account to the Local Service account during the install. This did not work for me after the instance was created. Once I change the account on my next attempt it worked for me. Surprised that the 64 bit version installed at all.
Thanks for everyone's help.

Answer 2

Computer Gladiator 446

Update.... the error during instance install is Could not find database engine startup handle.

AmeliaGu-MSFT 14,006 Reputation points Microsoft External Staff

2020-12-18T02:36:25.377+00:00

Hi @Computer Gladiator ,

the error during instance install is Could not find database engine startup handle.

Is your new instance installed successfully?
If not, could you please check if there any error messages in setup log which is located at within %programfiles%\Microsoft SQL Server\120\Setup Bootstrap\Log?

Best Regards,
Amelia
Computer Gladiator 446 Reputation points

2020-12-18T16:26:18.847+00:00

IHello, there is no bootstrap folder just a log folder. The error file show the following......
What stands out I have no E: drive. I installed the instance from a folder on the D: drive.
2020-12-17 20:08:33.83 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/BPTSB-DC01.bpts-bell.local:ACE2020 ] for the SQL Server service. Windows return code: 0x2098, 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.
2020-12-17 20:08:33.93 spid7s Error: 17204, Severity: 16, State: 1.
2020-12-17 20:08:33.93 spid7s 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: 21(The device is not ready
Computer Gladiator 446 Reputation points

2020-12-18T16:28:46.963+00:00

Additianl errors
2020-12-17 20:08:33.93 spid7s Error: 5120, Severity: 16, State: 101.
2020-12-17 20:08:33.93 spid7s Unable to open the physical file "E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\MSDBData.mdf". Operating system error 21: "21(The device is not ready.)".
2020-12-17 20:08:34.02 spid12s Error: 17204, Severity: 16, State: 1.
2020-12-17 20:08:34.02 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: 21(The device is not ready.).
2020-12-17 20:08:34.02 spid12s Error: 5120, Severity: 16, State: 101.
2020-12-17 20:08:34.02 spid12s Unable to open the physical file "E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\model.mdf". Operating system error 21: "21(The device is not ready.)".
2020-12-17 20:08:34.15 spid7s Error: 17207, Severity: 16, State: 1.
Computer Gladiator 446 Reputation points

2020-12-18T16:30:18.54+00:00

Additional errors....
2020-12-17 20:08:34.15 spid7s 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.
2020-12-17 20:08:34.15 spid7s File activation failure. The physical file name "E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\MSDBLog.ldf" may be incorrect.
2020-12-17 20:08:34.18 spid12s Error: 17207, Severity: 16, State: 1.
2020-12-17 20:08:34.18 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.
Computer Gladiator 446 Reputation points

2020-12-18T16:30:48.1+00:00

Last of errors
2020-12-17 20:08:34.18 spid12s File activation failure. The physical file name "E:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\modellog.ldf" may be incorrect.
2020-12-17 20:08:34.18 spid12s Error: 945, Severity: 14, State: 2.
2020-12-17 20:08:34.18 spid12s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2020-12-17 20:08:34.18 spid12s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Answer 3

Ben Miller (DBAduck) 966

This sounds like something that happens when you disable TLS 1.0 and do not have the right updates installed for .NET Framework 3.5 SP1. Did you recently disable TLS 1.0?

Computer Gladiator 446 Reputation points

2020-12-18T16:31:28.847+00:00

Thank you for your reply Ben. We did not disable TLS 1.0.

Answer 4

Erland Sommarskog 121.5K MVP Volunteer Moderator

I have seen this error with paths that starts with E:, but I have never fully understand them. But they seem to relate to the machine where the Setup was built and some path replacement has for some reason not occurred.

But one thing struck my eyes: the path as x86 in it. Are you absolutely sure that you want install 32-bit SQL Server? SQL 2014 was the last version to support 32-bit, but from SQL 2012, the normal thing has been to install the 64-bit version.

Answer 5

Raymond Wei 1

we have SQL error problem. it happened our online CRM production instance only.

I was who may face the same difficulty.

Thanks,

Share via

unable to start SQL instance

4 additional answers

Your answer