locked
2016 SQL Server Express installation failed RRS feed

  • Question

  • Database Engine Services continuously fails on install. Firewall and Anitvirus is completely disabled. I have tried the 2016 version aswell as the 2014 version with the same outcome.

    Here is the error log:

    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2061893606
      Start time:                    2016-08-29 20:40:11
      End time:                      2016-08-29 20:53:15
      Requested action:              Install

    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.


    Machine Properties:
      Machine name:                  BASSPOD
      Machine processor count:       4
      OS version:                    Microsoft Windows 10 Home (10.0.10586)
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No

    Product features discovered:
      Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered  Configured

    Package properties:
      Description:                   Microsoft SQL Server 2016 
      ProductName:                   SQL Server 2016
      Type:                          RTM
      Version:                       13
      SPLevel:                       0
      Installation location:         C:\SQLServer2016Media\Express\x64\setup\
      Installation edition:          Express

    Product Update Status:
      None discovered.

    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      true
      AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Disabled
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTELSVCACCT:                  <empty>
      ASTELSVCPASSWORD:              <empty>
      ASTELSVCSTARTUPTYPE:           0
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    true
      ENU:                           true
      EXTSVCACCOUNT:                 <empty>
      EXTSVCPASSWORD:                <empty>
      FEATURES:                      SQLENGINE
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTROPENLICENSETERMS:      false
      IACCEPTSQLSERVERLICENSETERMS:  true
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\Network Service
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      ISTELSVCACCT:                  <empty>
      ISTELSVCPASSWORD:              <empty>
      ISTELSVCSTARTUPTYPE:           0
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      MRCACHEDIRECTORY:              
      NPENABLED:                     0
      PBDMSSVCACCOUNT:               <empty>
      PBDMSSVCPASSWORD:              <empty>
      PBDMSSVCSTARTUPTYPE:           0
      PBENGSVCACCOUNT:               <empty>
      PBENGSVCPASSWORD:              <empty>
      PBENGSVCSTARTUPTYPE:           0
      PBPORTRANGE:                   <empty>
      PBSCALEOUT:                    false
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  SQL
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
      SQLSVCINSTANTFILEINIT:         false
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           BASSPOD\Eric
      SQLTELSVCACCT:                 NT Service\SQLTELEMETRY
      SQLTELSVCPASSWORD:             <empty>
      SQLTELSVCSTARTUPTYPE:          Automatic
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBFILECOUNT:            1
      SQLTEMPDBFILEGROWTH:           64
      SQLTEMPDBFILESIZE:             8
      SQLTEMPDBLOGDIR:               <empty>
      SQLTEMPDBLOGFILEGROWTH:        64
      SQLTEMPDBLOGFILESIZE:          8
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SUPPRESSPRIVACYSTATEMENTNOTICE: false
      TCPENABLED:                    0
      UIMODE:                        AutoAdvance
      UpdateEnabled:                 true
      UpdateSource:                  MU
      USEMICROSOFTUPDATE:            false
      X86:                           false

      Configuration file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20160829_203957\ConfigurationFile.ini

    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1601.5&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026

      Feature:                       SQL Browser
      Status:                        Passed

      Feature:                       SQL Writer
      Status:                        Passed

      Feature:                       SQL Client Connectivity
      Status:                        Passed

      Feature:                       SQL Client Connectivity SDK
      Status:                        Passed

      Feature:                       Setup Support Files
      Status:                        Passed

    Rules with failures:

    Global rules:

    Scenario specific rules:

    Rules report file:               C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20160829_203957\SystemConfigurationCheck_Report.htm

    Tuesday, August 30, 2016 12:54 AM

Answers

  • Appreciate the response. Any possible steps I can take to try and see if it works?

    There can be two things here as Erland said it can be because the account running SQL server srevice does not have permission or can be because of something missing from profile. Can you go to SQL Server configuration manager and change the service account to Local System and start the service. If it fails follow this Blog it says about local profiles and backup profile on machine where this sql server is installed. You can delete backup profile based on issues if it has as per the article.

    Also check for Xio.min.Tan's answer in this thread


    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


    Thursday, September 1, 2016 4:18 AM

All replies

  • The link provided in the error log doesn't work either. :(. Please help, need this for school and have unable to do my work
    Tuesday, August 30, 2016 12:59 AM
  • Hi WhineyTTwins,

    I would suggest you uninstall existing SQL Server installation by following the instruction, and use LOCAL SYSTEM as SQL Server Service account during new installation see if it helps. Also, I would suggest you locate and post Details.txt by following the instruction so we can have a better understanding about the issue.

    I also found a similar blog for your reference.

    If you have any other questions, please let me know.

    Regards,
    Lin

    Tuesday, August 30, 2016 7:41 AM
  • You just need to follow below article, make sure you stick to all the points

    Could Not Find Database Engine Startup Handle Error During installation

    Please refer to section errorlog in the article. 


    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, August 30, 2016 8:48 AM
  • Ok, so I did all of this with no luck. How do I post the Details.txt log? Seems like it is excessively long to post. Any way to attach it?
    Wednesday, August 31, 2016 7:21 PM
  • ERRORLOG

    2016-08-31 14:40:10.93 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 10586: )

    2016-08-31 14:40:10.93 Server      UTC adjustment: -4:00
    2016-08-31 14:40:10.93 Server      (c) Microsoft Corporation.
    2016-08-31 14:40:10.93 Server      All rights reserved.
    2016-08-31 14:40:10.93 Server      Server process ID is 8264.
    2016-08-31 14:40:10.93 Server      System Manufacturer: 'Hewlett-Packard', System Model: 'HP ENVY 15 Notebook PC'.
    2016-08-31 14:40:10.93 Server      Authentication mode is MIXED.
    2016-08-31 14:40:10.93 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
    2016-08-31 14:40:10.93 Server      The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required.
    2016-08-31 14:40:10.93 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
    2016-08-31 14:40:10.93 Server      Command Line Startup Parameters:
    -s "SQLEXPRESS"
    -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.SQLEXPRESS\MSSQL\Template Data\master.mdf"
    -l "C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\Template Data\mastlog.ldf"
    2016-08-31 14:40:10.96 Server      SQL Server detected 1 sockets with 4 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.
    2016-08-31 14:40:10.96 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2016-08-31 14:40:10.96 Server      Detected 7386 MB of RAM. This is an informational message; no user action is required.
    2016-08-31 14:40:10.96 Server      Using conventional memory in the memory manager.
    2016-08-31 14:40:10.99 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
    2016-08-31 14:40:11.04 Server      Buffer pool extension is already disabled. No action is necessary. 
    2016-08-31 14:40:11.06 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2016-08-31 14:40:11.08 Server      InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
    2016-08-31 14:40:11.08 Server      Implied authentication manager initialization failed. Implied authentication will be disabled.
    2016-08-31 14:40:11.10 Server      The maximum number of dedicated administrator connections for this instance is '1'
    2016-08-31 14:40:11.10 Server      This instance of SQL Server last reported using a process ID of 3316 at 8/31/2016 2:40:08 PM (local) 8/31/2016 6:40:08 PM (UTC). This is an informational message only; no user action is required.
    2016-08-31 14:40:11.10 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.
    2016-08-31 14:40:11.12 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.
    2016-08-31 14:40:11.12 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.
    2016-08-31 14:40:11.13 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2016-08-31 14:40:11.13 Server      Query Store settings initialized with enabled = 1, 
    2016-08-31 14:40:11.13 spid5s      Warning ******************
    2016-08-31 14:40:11.13 spid5s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2016-08-31 14:40:11.13 Server      Software Usage Metrics is disabled.
    2016-08-31 14:40:11.13 spid5s      [INFO] HkHostDbCtxt::Initialize(): Database ID: [1] 'master'. XTP Engine version is 0.0.
    2016-08-31 14:40:11.13 spid5s      Starting up database 'master'.
    2016-08-31 14:40:11.15 spid5s      [INFO] HkHostDbCtxt::Initialize(): Database ID: [1] 'master'. XTP Engine version is 0.0.
    2016-08-31 14:40:11.18 spid5s      [INFO] HkHostDbCtxt::Initialize(): Database ID: [1] 'master'. XTP Engine version is 0.0.
    2016-08-31 14:40:11.22 Server      CLR version v4.0.30319 loaded.
    2016-08-31 14:40:11.23 spid5s      3 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
    2016-08-31 14:40:11.31 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2016-08-31 14:40:11.34 spid5s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
    2016-08-31 14:40:11.34 spid5s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2016-08-31 14:40:11.56 spid5s      CreateSMKInMetadata in CSECServiceMasterKey::Initialize failed with ESECCryptoError code: 16
    2016-08-31 14:40:11.56 spid5s      Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
    2016-08-31 14:40:11.56 spid5s      An error occurred during Service Master Key initialization. SQLErrorCode=x_cse_CannotEncryptSMK, State=1, LastWindowsError=2.
    2016-08-31 14:40:11.68 spid5s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2016-08-31 14:40:11.68 spid5s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2016-08-31 14:40:11.74 spid5s      SQL Trace ID 1 was started by login "sa".
    2016-08-31 14:40:11.76 spid5s      Server name is 'BASSPOD\SQLEXPRESS'. This is an informational message only. No user action is required.
    2016-08-31 14:40:11.77 spid12s     Error: 17190, Severity: 16, State: 1.
    2016-08-31 14:40:11.77 spid12s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2016-08-31 14:40:11.77 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.
    2016-08-31 14:40:11.77 spid12s     Error: 17182, Severity: 16, State: 1.
    2016-08-31 14:40:11.77 spid12s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 
    2016-08-31 14:40:11.77 spid12s     Error: 17182, Severity: 16, State: 1.
    2016-08-31 14:40:11.77 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. 
    2016-08-31 14:40:11.77 spid12s     Error: 17826, Severity: 18, State: 3.
    2016-08-31 14:40:11.77 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.
    2016-08-31 14:40:11.77 spid12s     Error: 17120, Severity: 16, State: 1.
    2016-08-31 14:40:11.77 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.

    Wednesday, August 31, 2016 7:30 PM
  • ERRORLOG 1

    2016-08-31 14:40:07.98 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 10586: )

    2016-08-31 14:40:07.98 Server      UTC adjustment: -4:00
    2016-08-31 14:40:07.98 Server      (c) Microsoft Corporation.
    2016-08-31 14:40:07.98 Server      All rights reserved.
    2016-08-31 14:40:07.98 Server      Server process ID is 3316.
    2016-08-31 14:40:07.98 Server      System Manufacturer: 'Hewlett-Packard', System Model: 'HP ENVY 15 Notebook PC'.
    2016-08-31 14:40:07.98 Server      Authentication mode is MIXED.
    2016-08-31 14:40:07.98 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
    2016-08-31 14:40:07.98 Server      The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required.
    2016-08-31 14:40:07.98 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
    2016-08-31 14:40:07.98 Server      Command Line Startup Parameters:
    -s "SQLEXPRESS"
    -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.SQLEXPRESS\MSSQL\Template Data\master.mdf"
    -l "C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\Template Data\mastlog.ldf"
    2016-08-31 14:40:08.01 Server      SQL Server detected 1 sockets with 4 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.
    2016-08-31 14:40:08.01 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2016-08-31 14:40:08.01 Server      Detected 7386 MB of RAM. This is an informational message; no user action is required.
    2016-08-31 14:40:08.01 Server      Using conventional memory in the memory manager.
    2016-08-31 14:40:08.04 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
    2016-08-31 14:40:08.10 Server      Buffer pool extension is already disabled. No action is necessary. 
    2016-08-31 14:40:08.12 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2016-08-31 14:40:08.13 Server      InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
    2016-08-31 14:40:08.13 Server      Implied authentication manager initialization failed. Implied authentication will be disabled.
    2016-08-31 14:40:08.15 Server      The maximum number of dedicated administrator connections for this instance is '1'
    2016-08-31 14:40:08.16 Server      This instance of SQL Server last reported using a process ID of 8308 at 8/31/2016 2:40:04 PM (local) 8/31/2016 6:40:04 PM (UTC). This is an informational message only; no user action is required.
    2016-08-31 14:40:08.16 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.
    2016-08-31 14:40:08.17 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.
    2016-08-31 14:40:08.17 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.
    2016-08-31 14:40:08.18 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2016-08-31 14:40:08.18 Server      Query Store settings initialized with enabled = 1, 
    2016-08-31 14:40:08.18 spid5s      Warning ******************
    2016-08-31 14:40:08.19 spid5s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2016-08-31 14:40:08.19 Server      Software Usage Metrics is disabled.
    2016-08-31 14:40:08.19 spid5s      [INFO] HkHostDbCtxt::Initialize(): Database ID: [1] 'master'. XTP Engine version is 0.0.
    2016-08-31 14:40:08.19 spid5s      Starting up database 'master'.
    2016-08-31 14:40:08.20 spid5s      [INFO] HkHostDbCtxt::Initialize(): Database ID: [1] 'master'. XTP Engine version is 0.0.
    2016-08-31 14:40:08.22 spid5s      [INFO] HkHostDbCtxt::Initialize(): Database ID: [1] 'master'. XTP Engine version is 0.0.
    2016-08-31 14:40:08.26 spid5s      5 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
    2016-08-31 14:40:08.28 Server      CLR version v4.0.30319 loaded.
    2016-08-31 14:40:08.28 spid5s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
    2016-08-31 14:40:08.28 spid5s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2016-08-31 14:40:08.37 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2016-08-31 14:40:08.57 spid5s      CreateSMKInMetadata in CSECServiceMasterKey::Initialize failed with ESECCryptoError code: 16
    2016-08-31 14:40:08.57 spid5s      Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
    2016-08-31 14:40:08.58 spid5s      An error occurred during Service Master Key initialization. SQLErrorCode=x_cse_CannotEncryptSMK, State=1, LastWindowsError=2.
    2016-08-31 14:40:08.75 spid5s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2016-08-31 14:40:08.78 spid5s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2016-08-31 14:40:08.82 spid5s      SQL Trace ID 1 was started by login "sa".
    2016-08-31 14:40:08.82 spid5s      Server name is 'BASSPOD\SQLEXPRESS'. This is an informational message only. No user action is required.
    2016-08-31 14:40:08.85 spid5s      [INFO] HkHostDbCtxt::Initialize(): Database ID: [4] 'msdb'. XTP Engine version is 0.0.
    2016-08-31 14:40:08.85 spid5s      Starting up database 'msdb'.
    2016-08-31 14:40:08.85 spid12s     Error: 17190, Severity: 16, State: 1.
    2016-08-31 14:40:08.85 spid12s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2016-08-31 14:40:08.85 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.
    2016-08-31 14:40:08.85 spid8s      [INFO] HkHostDbCtxt::Initialize(): Database ID: [32767] 'mssqlsystemresource'. XTP Engine version is 0.0.
    2016-08-31 14:40:08.85 spid12s     Error: 17182, Severity: 16, State: 1.
    2016-08-31 14:40:08.85 spid12s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 
    2016-08-31 14:40:08.85 spid8s      Starting up database 'mssqlsystemresource'.
    2016-08-31 14:40:08.85 spid12s     Error: 17182, Severity: 16, State: 1.
    2016-08-31 14:40:08.85 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. 
    2016-08-31 14:40:08.85 spid12s     Error: 17826, Severity: 18, State: 3.
    2016-08-31 14:40:08.85 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.
    2016-08-31 14:40:08.85 spid12s     Error: 17120, Severity: 16, State: 1.
    2016-08-31 14:40:08.85 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.

    Wednesday, August 31, 2016 7:32 PM
  • ERRORLOG 2

    2016-08-31 14:40:04.72 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 10586: )

    2016-08-31 14:40:04.72 Server      UTC adjustment: -4:00
    2016-08-31 14:40:04.72 Server      (c) Microsoft Corporation.
    2016-08-31 14:40:04.72 Server      All rights reserved.
    2016-08-31 14:40:04.72 Server      Server process ID is 8308.
    2016-08-31 14:40:04.72 Server      System Manufacturer: 'Hewlett-Packard', System Model: 'HP ENVY 15 Notebook PC'.
    2016-08-31 14:40:04.72 Server      Authentication mode is MIXED.
    2016-08-31 14:40:04.72 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
    2016-08-31 14:40:04.72 Server      The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required.
    2016-08-31 14:40:04.72 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
    2016-08-31 14:40:04.72 Server      Command Line Startup Parameters:
    -s "SQLEXPRESS"
    -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.SQLEXPRESS\MSSQL\Template Data\master.mdf"
    -l "C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\Template Data\mastlog.ldf"
    2016-08-31 14:40:04.75 Server      SQL Server detected 1 sockets with 4 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.
    2016-08-31 14:40:04.75 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2016-08-31 14:40:04.75 Server      Detected 7386 MB of RAM. This is an informational message; no user action is required.
    2016-08-31 14:40:04.75 Server      Using conventional memory in the memory manager.
    2016-08-31 14:40:04.79 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
    2016-08-31 14:40:04.85 Server      Buffer pool extension is already disabled. No action is necessary. 
    2016-08-31 14:40:04.87 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2016-08-31 14:40:04.89 Server      InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
    2016-08-31 14:40:04.89 Server      Implied authentication manager initialization failed. Implied authentication will be disabled.
    2016-08-31 14:40:04.93 Server      The maximum number of dedicated administrator connections for this instance is '1'
    2016-08-31 14:40:04.93 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.
    2016-08-31 14:40:04.94 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.
    2016-08-31 14:40:04.95 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.
    2016-08-31 14:40:04.95 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2016-08-31 14:40:04.96 Server      Query Store settings initialized with enabled = 1, 
    2016-08-31 14:40:04.96 spid5s      Warning ******************
    2016-08-31 14:40:04.96 spid5s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2016-08-31 14:40:04.96 Server      Software Usage Metrics is disabled.
    2016-08-31 14:40:04.96 spid5s      [INFO] HkHostDbCtxt::Initialize(): Database ID: [1] 'master'. XTP Engine version is 0.0.
    2016-08-31 14:40:04.96 spid5s      Starting up database 'master'.
    2016-08-31 14:40:04.98 spid5s      [INFO] HkHostDbCtxt::Initialize(): Database ID: [1] 'master'. XTP Engine version is 0.0.
    2016-08-31 14:40:05.00 spid5s      [INFO] HkHostDbCtxt::Initialize(): Database ID: [1] 'master'. XTP Engine version is 0.0.
    2016-08-31 14:40:05.04 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.SQLEXPRESS\MSSQL\Template Data\mastlog.ldf will be written.
    2016-08-31 14:40:05.13 Server      CLR version v4.0.30319 loaded.
    2016-08-31 14:40:05.24 spid5s      CreateSMKInMetadata in CSECServiceMasterKey::Initialize failed with ESECCryptoError code: 16
    2016-08-31 14:40:05.24 spid5s      Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
    2016-08-31 14:40:05.24 spid5s      An error occurred during Service Master Key initialization. SQLErrorCode=x_cse_CannotEncryptSMK, State=1, LastWindowsError=2.
    2016-08-31 14:40:05.24 spid5s      Converting database 'master' from version 836 to the current version 852.
    2016-08-31 14:40:05.24 spid5s      Database 'master' running the upgrade step from version 836 to version 837.
    2016-08-31 14:40:05.26 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2016-08-31 14:40:05.28 spid5s      Database 'master' running the upgrade step from version 837 to version 838.
    2016-08-31 14:40:05.29 spid5s      Database 'master' running the upgrade step from version 838 to version 839.
    2016-08-31 14:40:05.29 spid5s      Database 'master' running the upgrade step from version 839 to version 840.
    2016-08-31 14:40:05.30 spid5s      Database 'master' running the upgrade step from version 840 to version 841.
    2016-08-31 14:40:05.30 spid5s      Database 'master' running the upgrade step from version 841 to version 842.
    2016-08-31 14:40:05.38 spid5s      Database 'master' running the upgrade step from version 842 to version 843.
    2016-08-31 14:40:05.41 spid5s      Database 'master' running the upgrade step from version 843 to version 844.
    2016-08-31 14:40:05.41 spid5s      Database 'master' running the upgrade step from version 844 to version 845.
    2016-08-31 14:40:05.41 spid5s      Database 'master' running the upgrade step from version 845 to version 846.
    2016-08-31 14:40:05.41 spid5s      Database 'master' running the upgrade step from version 846 to version 847.
    2016-08-31 14:40:05.42 spid5s      Database 'master' running the upgrade step from version 847 to version 848.
    2016-08-31 14:40:05.42 spid5s      Database 'master' running the upgrade step from version 848 to version 849.
    2016-08-31 14:40:05.43 spid5s      Database 'master' running the upgrade step from version 849 to version 850.
    2016-08-31 14:40:05.45 spid5s      Database 'master' running the upgrade step from version 850 to version 851.
    2016-08-31 14:40:05.46 spid5s      Database 'master' running the upgrade step from version 851 to version 852.
    2016-08-31 14:40:05.63 spid5s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2016-08-31 14:40:05.63 spid5s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2016-08-31 14:40:05.66 spid5s      SQL Trace ID 1 was started by login "sa".
    2016-08-31 14:40:05.66 spid5s      Server name is 'BASSPOD\SQLEXPRESS'. This is an informational message only. No user action is required.
    2016-08-31 14:40:05.67 spid12s     Password policy update was successful.
    2016-08-31 14:40:05.67 spid12s     Error: 17190, Severity: 16, State: 1.
    2016-08-31 14:40:05.67 spid12s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2016-08-31 14:40:05.68 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.
    2016-08-31 14:40:05.68 spid12s     Error: 17182, Severity: 16, State: 1.
    2016-08-31 14:40:05.68 spid12s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 
    2016-08-31 14:40:05.68 spid12s     Error: 17182, Severity: 16, State: 1.
    2016-08-31 14:40:05.68 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. 
    2016-08-31 14:40:05.68 spid12s     Error: 17826, Severity: 18, State: 3.
    2016-08-31 14:40:05.68 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.
    2016-08-31 14:40:05.68 spid12s     Error: 17120, Severity: 16, State: 1.
    2016-08-31 14:40:05.68 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.

    Wednesday, August 31, 2016 7:32 PM
  • Hope this provides sufficient information. Thank you for help.
    Wednesday, August 31, 2016 7:34 PM
  • This is where it all goes wrong:

    2016-08-31 14:40:11.77 spid12s     Error: 17190, Severity: 16, State: 1.
    2016-08-31 14:40:11.77 spid12s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2016-08-31 14:40:11.77 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.
    2016-08-31 14:40:11.77 spid12s     Error: 17182, Severity: 16, State: 1.
    2016-08-31 14:40:11.77 spid12s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 

    I will have to admit that I don't know the cause for this, but it seems that something is not the way it should be with the certificate store. Possibly, the service account NT Service\MSSQL$SQLEXPRESS is lacking permissions, but this is something Setup should have catered for earlier.

    Wednesday, August 31, 2016 9:38 PM
  • Appreciate the response. Any possible steps I can take to try and see if it works?
    Wednesday, August 31, 2016 11:56 PM
    • Edited by AV111 Thursday, September 1, 2016 12:26 AM
    Thursday, September 1, 2016 12:20 AM
  • Appreciate the response. Any possible steps I can take to try and see if it works?

    There can be two things here as Erland said it can be because the account running SQL server srevice does not have permission or can be because of something missing from profile. Can you go to SQL Server configuration manager and change the service account to Local System and start the service. If it fails follow this Blog it says about local profiles and backup profile on machine where this sql server is installed. You can delete backup profile based on issues if it has as per the article.

    Also check for Xio.min.Tan's answer in this thread


    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


    Thursday, September 1, 2016 4:18 AM
  • check this link-

    http://www.sqldbadiaries.com/2013/01/01/service-does-not-start-tdssniclient-initialization-failed-with-error-0x80092004-status-code-0x80/


    Regards, S_NO "_"

    Thursday, September 1, 2016 4:41 AM
  • Hi WhineyTTwins,

    I’m writing to follow up with you on this post. Was the issue resolved? If you issue has resolved, I’d like to mark this issue as "Answered". Please also feel free to unmark the issue, with any new findings or concerns you may have.

    If you have any other questions, please let me know.

    Regards,
    Lin
    Saturday, September 10, 2016 2:01 PM
  • I had this issue. Uninstalling is not the answer.  I actually had to run a CUSTOM install, not the Basic install. Select New SQL Server stand-alone installation or add features to an existing installation.   This allowed me to name my instance. When It did, I called it SQLEXP, it also allowed me to specify how to login. I selected the Windows Login and then I chose User, Group, etc. Then I browsed to find my login in the list for my computer. Once I did that, I was able to type in my password.   It installed after I did that.    So, my issue appeared to be the password.  Once it was stored, It worked.   Sorry, I didn't take notes when I did this, but this should get you in the right direction for help.

    -E

    Wednesday, April 5, 2017 2:37 AM