none
Error Encountered When Installing Additional SQL Server Express Instance

    Question

  • When attempting to install an additional instance of SQL Server Express (in this case, 2016) on my laptop, which already has an instance of SQL Server Express insalled, the following error arises:

    Unable to install SQL Server (setup.exe).

    Exit code (Decimal)
    -2061893606
    Error description
    Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.

    . . .

    When looking inside the error log file specified, namely C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20170403_223502\SQLServer_ERRORLOG_2017-04-03T22.36.22.txt, the first error message encountered says:

    CreateSMKInMetadata in CSECServiceMasterKey::Initialize failed with ESECCryptoError code: 16

    I know that one is supposed to be able to install  multiple instances of SQL Server Express on the same machine. Any suggestions would be greatly appreciated.

    . . .

    Thanks for any assistance


    Tallisfan

    Tuesday, April 4, 2017 4:19 AM

All replies

  • Did you referred to below link and specially the errorlog section. 

    Wait on DB engine recovery handle failed

    Go ahead locate the errorlog using the link and post its content here. This will have reason why SQL Server is not starting.

    You can also locate SQL Server configuration manager and first change SQL Server account to NT Authority\System and now try starting. Hopefully it will come online. If not look for errorlog and post its content here


    Cheers,

    Shashank

    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles

    MVP


    Tuesday, April 4, 2017 5:37 AM
    Moderator
  • The following is from file SQLServer_ERRORLOG_2017-04-03T22.36.22.txt, which is the file specified by the installation wizard:

    2017-04-03 22:36:21.18 Server      Microsoft SQL Server 2016 (RTM) - 13.0.1601.5 (X64)
        Apr 29 2016 23:23:58
        Copyright (c) Microsoft Corporation
        Express Edition (64-bit) on Windows 10 Home 6.3 <X64> (Build 14393: )

    2017-04-03 22:36:21.18 Server      UTC adjustment: -5:00
    2017-04-03 22:36:21.18 Server      (c) Microsoft Corporation.
    2017-04-03 22:36:21.18 Server      All rights reserved.
    2017-04-03 22:36:21.18 Server      Server process ID is 4212.
    2017-04-03 22:36:21.18 Server      System Manufacturer: 'ASUSTeK COMPUTER INC.', System Model: 'X555LAB'.
    2017-04-03 22:36:21.18 Server      Authentication mode is WINDOWS-ONLY.
    2017-04-03 22:36:21.18 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS01\MSSQL\Log\ERRORLOG'.
    2017-04-03 22:36:21.18 Server      The service account is 'NT Service\MSSQL$SQLEXPRESS01'. This is an informational message; no user action is required.
    2017-04-03 22:36:21.18 Server      Registry startup parameters:
         -d C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS01\MSSQL\DATA\master.mdf
         -e C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS01\MSSQL\Log\ERRORLOG
         -l C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS01\MSSQL\DATA\mastlog.ldf
    2017-04-03 22:36:21.18 Server      Command Line Startup Parameters:
         -s "SQLEXPRESS01"
         -m "SqlSetup"
         -Q
         -q "SQL_Latin1_General_CP1_CI_AS"
         -T 4022
         -T 4010
         -T 3659
         -T 3610
         -T 8015
         -d "C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS01\MSSQL\Template Data\master.mdf"
         -l "C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS01\MSSQL\Template Data\mastlog.ldf"
    2017-04-03 22:36:21.20 Server      SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
    2017-04-03 22:36:21.20 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2017-04-03 22:36:21.20 Server      Detected 8095 MB of RAM. This is an informational message; no user action is required.
    2017-04-03 22:36:21.20 Server      Using conventional memory in the memory manager.
    2017-04-03 22:36:21.27 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
    2017-04-03 22:36:21.29 Server      Buffer pool extension is already disabled. No action is necessary.
    2017-04-03 22:36:21.29 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2017-04-03 22:36:21.30 Server      InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
    2017-04-03 22:36:21.30 Server      Implied authentication manager initialization failed. Implied authentication will be disabled.
    2017-04-03 22:36:21.32 Server      The maximum number of dedicated administrator connections for this instance is '1'
    2017-04-03 22:36:21.32 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2017-04-03 22:36:21.33 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2017-04-03 22:36:21.33 Server      Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
    2017-04-03 22:36:21.36 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2017-04-03 22:36:21.36 Server      Query Store settings initialized with enabled = 1,
    2017-04-03 22:36:21.36 spid5s      Warning ******************
    2017-04-03 22:36:21.36 spid5s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2017-04-03 22:36:21.36 Server      Software Usage Metrics is disabled.
    2017-04-03 22:36:21.36 spid5s      [INFO] HkHostDbCtxt::Initialize(): Database ID: [1] 'master'. XTP Engine version is 0.0.
    2017-04-03 22:36:21.36 spid5s      Starting up database 'master'.
    2017-04-03 22:36:21.37 spid5s      [INFO] HkHostDbCtxt::Initialize(): Database ID: [1] 'master'. XTP Engine version is 0.0.
    2017-04-03 22:36:21.38 spid5s      [INFO] HkHostDbCtxt::Initialize(): Database ID: [1] 'master'. XTP Engine version is 0.0.
    2017-04-03 22:36:21.41 spid5s      The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes.  3072 bytes at offset 111616 in file C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS01\MSSQL\Template Data\mastlog.ldf will be written.
    2017-04-03 22:36:21.47 Server      CLR version v4.0.30319 loaded.
    2017-04-03 22:36:21.53 spid5s      CreateSMKInMetadata in CSECServiceMasterKey::Initialize failed with ESECCryptoError code: 16
    2017-04-03 22:36:21.53 spid5s      Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
    2017-04-03 22:36:21.53 spid5s      An error occurred during Service Master Key initialization. SQLErrorCode=x_cse_CannotEncryptSMK, State=1, LastWindowsError=2.
    2017-04-03 22:36:21.53 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2017-04-03 22:36:21.53 spid5s      Converting database 'master' from version 836 to the current version 852.
    2017-04-03 22:36:21.53 spid5s      Database 'master' running the upgrade step from version 836 to version 837.
    2017-04-03 22:36:21.63 spid5s      Database 'master' running the upgrade step from version 837 to version 838.
    2017-04-03 22:36:21.66 spid5s      Database 'master' running the upgrade step from version 838 to version 839.
    2017-04-03 22:36:21.66 spid5s      Database 'master' running the upgrade step from version 839 to version 840.
    2017-04-03 22:36:21.66 spid5s      Database 'master' running the upgrade step from version 840 to version 841.
    2017-04-03 22:36:21.66 spid5s      Database 'master' running the upgrade step from version 841 to version 842.
    2017-04-03 22:36:21.69 spid5s      Database 'master' running the upgrade step from version 842 to version 843.
    2017-04-03 22:36:21.74 spid5s      Database 'master' running the upgrade step from version 843 to version 844.
    2017-04-03 22:36:21.74 spid5s      Database 'master' running the upgrade step from version 844 to version 845.
    2017-04-03 22:36:21.74 spid5s      Database 'master' running the upgrade step from version 845 to version 846.
    2017-04-03 22:36:21.74 spid5s      Database 'master' running the upgrade step from version 846 to version 847.
    2017-04-03 22:36:21.74 spid5s      Database 'master' running the upgrade step from version 847 to version 848.
    2017-04-03 22:36:21.75 spid5s      Database 'master' running the upgrade step from version 848 to version 849.
    2017-04-03 22:36:21.75 spid5s      Database 'master' running the upgrade step from version 849 to version 850.
    2017-04-03 22:36:21.76 spid5s      Database 'master' running the upgrade step from version 850 to version 851.
    2017-04-03 22:36:21.76 spid5s      Database 'master' running the upgrade step from version 851 to version 852.
    2017-04-03 22:36:21.97 spid5s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2017-04-03 22:36:21.97 spid5s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2017-04-03 22:36:22.06 spid5s      SQL Trace ID 1 was started by login "sa".
    2017-04-03 22:36:22.07 spid5s      Server name is 'OLIN-PC\SQLEXPRESS01'. This is an informational message only. No user action is required.
    2017-04-03 22:36:22.09 spid12s     Password policy update was successful.
    2017-04-03 22:36:22.10 spid12s     Error: 17190, Severity: 16, State: 1.
    2017-04-03 22:36:22.10 spid12s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2017-04-03 22:36:22.10 spid12s     Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
    2017-04-03 22:36:22.10 spid12s     Error: 17182, Severity: 16, State: 1.
    2017-04-03 22:36:22.10 spid12s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
    2017-04-03 22:36:22.10 spid5s      [INFO] HkHostDbCtxt::Initialize(): Database ID: [4] 'msdb'. XTP Engine version is 0.0.
    2017-04-03 22:36:22.10 spid12s     Error: 17182, Severity: 16, State: 1.
    2017-04-03 22:36:22.10 spid12s     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.
    2017-04-03 22:36:22.10 spid5s      Starting up database 'msdb'.
    2017-04-03 22:36:22.10 spid12s     Error: 17826, Severity: 18, State: 3.
    2017-04-03 22:36:22.10 spid12s     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.
    2017-04-03 22:36:22.10 spid8s      [INFO] HkHostDbCtxt::Initialize(): Database ID: [32767] 'mssqlsystemresource'. XTP Engine version is 0.0.
    2017-04-03 22:36:22.10 spid12s     Error: 17120, Severity: 16, State: 1.
    2017-04-03 22:36:22.10 spid12s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
    2017-04-03 22:36:22.10 spid8s      Starting up database 'mssqlsystemresource'.
    Cannot close event log because there are still event handle users active.


    Tallisfan

    Tuesday, April 4, 2017 11:34 PM
  • So did you changed SQL Server service account to NT Authority\System from SQL server config manager ?

    Cheers,

    Shashank

    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles

    MVP

    Wednesday, April 5, 2017 4:41 AM
    Moderator
  • Yes, I've tried several times to change the account, but it always responds with a WMI Provider Error of 0x800703b1.

    . . .

    But I've never been able to get to the finish of a clean install anyway. Does the above Log listing provide any clues?

    . . .

    Thanks again for any ideas


    Tallisfan

    Thursday, April 6, 2017 12:06 AM
  • see Lydia answer

    https://social.msdn.microsoft.com/Forums/azure/en-US/0a9161c1-1a97-4c66-94de-76eab67a7384/sql-express-2012-error-starting-instance?forum=sqlexpress


    Please Mark it as Answered if it answered your question OR mark it as Helpful if it help you to solve your problem.

    Thursday, April 6, 2017 4:37 PM
  • UNbelievable! Yes, I have indeed encountered a myriad of problems when I upgraded to Windows 10, but THIS is ABSURD, no make that OUTRAGEOUS.  Now I am attempting to follow Lydia's suggestions. However, yet again, I am running into the never-ending problems due to the foolish lack of planning and attention to potential problems by Microsoft. When I attempted to create a new local account (I have never needed to do so before), I was confronted with what is apparently a very common problem with the Windows 10 upgrade. "The User Profile Service service failed the sign-in. User profile cannot be loaded."  This is simply UNACCEPTABLE! I am now forced to try various suggested solutions; right now, I'm following the suggested fixes at http://www.techbout.com/user-profile-cannot-be-loaded-error-in-windows-10-9115/. Unfortunately, so far, I have not managed to create a usable second account, i.e., I cannot sign on to a new local account. UNbelievable! I will press on until I can do so, and then I will see if Lydia's suggestions work.

    . . .

    Thanks again for your help.


    Tallisfan

    Friday, April 7, 2017 4:00 AM