none
Error -2061893606 during installation of SQL Server 2016 w/ SP1

    Question

  • I am trying to install SQL Server 2016 with SP1 for an undergraduate class.  I am not familiar with SQL.  The error description says "Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes."

    The error log says:

    2017-03-13 13:05:58.06 Server      Microsoft SQL Server 2016 (SP1) (KB3182545) - 13.0.4001.0 (X64)
        Oct 28 2016 18:17:30
        Copyright (c) Microsoft Corporation
        Enterprise Evaluation Edition (64-bit) on Windows 10 Home 6.3 <X64> (Build 14393: )

    2017-03-13 13:05:58.07 Server      UTC adjustment: -5:00
    2017-03-13 13:05:58.07 Server      (c) Microsoft Corporation.
    2017-03-13 13:05:58.07 Server      All rights reserved.
    2017-03-13 13:05:58.07 Server      Server process ID is 6956.
    2017-03-13 13:05:58.07 Server      System Manufacturer: 'Hewlett-Packard', System Model: 'HP Pavilion dv6 Notebook PC'.
    2017-03-13 13:05:58.07 Server      Authentication mode is WINDOWS-ONLY.
    2017-03-13 13:05:58.07 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2017-03-13 13:05:58.07 Server      The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
    2017-03-13 13:05:58.07 Server      Registry startup parameters:
         -d C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA\master.mdf
         -e C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Log\ERRORLOG
         -l C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2017-03-13 13:05:58.07 Server      Command Line Startup Parameters:
         -s "MSSQLSERVER"
         -m "SqlSetup"
         -Q
         -q "SQL_Latin1_General_CP1_CI_AS"
         -T 4022
         -T 4010
         -T 3659
         -T 3610
         -T 8015
         -T 902
    2017-03-13 13:05:58.12 Server      SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
    2017-03-13 13:05:58.12 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2017-03-13 13:05:58.12 Server      Detected 8139 MB of RAM. This is an informational message; no user action is required.
    2017-03-13 13:05:58.12 Server      Using conventional memory in the memory manager.
    2017-03-13 13:05:58.30 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
    2017-03-13 13:05:58.36 Server      Buffer pool extension is already disabled. No action is necessary.
    2017-03-13 13:05:58.40 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2017-03-13 13:05:58.42 Server      InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
    2017-03-13 13:05:58.42 Server      Implied authentication manager initialization failed. Implied authentication will be disabled.
    2017-03-13 13:05:58.43 Server      The maximum number of dedicated administrator connections for this instance is '1'
    2017-03-13 13:05:58.44 Server      This instance of SQL Server last reported using a process ID of 1308 at 3/13/2017 1:05:52 PM (local) 3/13/2017 6:05:52 PM (UTC). This is an informational message only; no user action is required.
    2017-03-13 13:05:58.44 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff: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-03-13 13:05:58.45 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-03-13 13:05:58.45 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-03-13 13:05:58.49 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2017-03-13 13:05:58.50 Server      Query Store settings initialized with enabled = 1,
    2017-03-13 13:05:58.50 spid5s      Warning ******************
    2017-03-13 13:05:58.50 spid5s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2017-03-13 13:05:58.50 spid5s      Starting up database 'master'.
    2017-03-13 13:05:58.54 Server      Software Usage Metrics is disabled.
    2017-03-13 13:05:58.55 Server      CLR version v4.0.30319 loaded.
    2017-03-13 13:05:58.63 spid5s      2 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
    2017-03-13 13:05:58.65 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2017-03-13 13:05:58.73 spid5s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
    2017-03-13 13:05:58.77 spid5s      CreateSMKInMetadata in CSECServiceMasterKey::Initialize failed with ESECCryptoError code: 16
    2017-03-13 13:05:58.77 spid5s      Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
    2017-03-13 13:05:58.77 spid5s      An error occurred during Service Master Key initialization. SQLErrorCode=x_cse_CannotEncryptSMK, State=1, LastWindowsError=2.
    2017-03-13 13:05:58.83 spid5s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2017-03-13 13:05:58.84 spid5s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2017-03-13 13:05:58.99 spid5s      SQL Trace ID 1 was started by login "sa".
    2017-03-13 13:05:59.00 spid5s      Server name is 'LAPTOP'. This is an informational message only. No user action is required.
    2017-03-13 13:05:59.01 spid14s     Error: 17190, Severity: 16, State: 1.
    2017-03-13 13:05:59.01 spid14s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2017-03-13 13:05:59.01 spid14s     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-03-13 13:05:59.01 spid14s     Error: 17182, Severity: 16, State: 1.
    2017-03-13 13:05:59.01 spid14s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
    2017-03-13 13:05:59.02 spid14s     Error: 17182, Severity: 16, State: 1.
    2017-03-13 13:05:59.02 spid14s     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-03-13 13:05:59.02 spid14s     Error: 17826, Severity: 18, State: 3.
    2017-03-13 13:05:59.02 spid14s     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-03-13 13:05:59.02 spid14s     Error: 17120, Severity: 16, State: 1.
    2017-03-13 13:05:59.02 spid14s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

    Tuesday, March 14, 2017 3:16 AM

Answers

All replies