none
SQL Server 2016 - Wait on the Database Engine... - now Object reference not set to an instance of an object.

    Question

  • I'm trying to install Microsoft SQL Server 2016 Developer edition on my home computer for educational purposes. At first, the Database Engine Services would not install. Five days later, I've tried much to no avail, including the instructions found in:

    http://social.technet.microsoft.com/wiki/contents/articles/24364.sql-server-troubleshooting-could-not-find-database-engine-startup-handle-error-during-installation.aspx

    Following multiple installs/uninstalls, and now a registry key deletion, I've gotten various errors including (1) "Wait on the Database Engine recovery handle failed", and (2) "Object reference not set to an instance of an object."


    How much more of this before I must go onto suicide watch? Any help is appreciated.


    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2147467261
      Start time:                    2016-11-23 04:30:07
      End time:                      2016-11-23 04:41:17
      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:                  XPS
      Machine processor count:       4
      OS version:                    Microsoft Windows 10 Home (10.0.14393)
      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
      SQL Server 2016                                                          SSMS                                     1033                                      13.0.16000.28   No         Yes       
      SQL Server 2016                                                          Adv_SSMS                                 1033                                      13.0.16000.28   No         Yes       
    
    Package properties:
      Description:                   Microsoft SQL Server 2016 
      ProductName:                   SQL Server 2016
      Type:                          RTM
      Version:                       13
      Installation location:         E:\x64\setup\
      Installation edition:          Developer
    
      Slipstream:                    True
      SP Level                       1
    
    Product Update Status:
      Success: KB 3182545
    
    Product Updates Selected for Installation:
      Title:                         Microsoft SQL Server 2016  with SP1
      Knowledge Based Article:       KB 3182545
      Version:                       13.1.4001.0
      Architecture:                  x64
      Language:                      1033
    
      Update Source:                 Slipstream
    
    
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      false
      AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      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:         Automatic
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161123_042941\ConfigurationFile.ini
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    false
      ENU:                           true
      EXTSVCACCOUNT:                 <empty>
      EXTSVCPASSWORD:                <empty>
      FEATURES:                      SQLENGINE, CONN
      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:                          
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  SQL
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      SQLSVCINSTANTFILEINIT:         false
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           XPS\Joseph
      SQLTELSVCACCT:                 NT Service\SQLTELEMETRY
      SQLTELSVCPASSWORD:             <empty>
      SQLTELSVCSTARTUPTYPE:          Automatic
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBFILECOUNT:            4
      SQLTEMPDBFILEGROWTH:           64
      SQLTEMPDBFILESIZE:             8
      SQLTEMPDBLOGDIR:               <empty>
      SQLTEMPDBLOGFILEGROWTH:        64
      SQLTEMPDBLOGFILESIZE:          8
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SUPPRESSPRIVACYSTATEMENTNOTICE: false
      TCPENABLED:                    0
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  Slipstream
      USEMICROSOFTUPDATE:            false
      X86:                           false
    
      Configuration file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161123_042941\ConfigurationFile.ini
    
    Detailed results:
      Feature:                       Client Tools Connectivity
      Status:                        Passed
    
      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:          -2147467261
      Error description:             Object reference not set to an instance of an object.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.4001.0&EvtType=0x9C8C9C81%400x44A889F9&EvtType=0x9C8C9C81%400x44A889F9
    
      Feature:                       SQL Browser
      Status:                        Passed
    
      Feature:                       SQL Writer
      Status:                        Passed
    
      Feature:                       SQL Client Connectivity
      Status:                        Passed
    
      Feature:                       SQL Client Connectivity SDK
      Status:                        Passed
    
    Rules with failures:
    
    Global rules:
    
    Scenario specific rules:
    
    Rules report file:               C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161123_042941\SystemConfigurationCheck_Report.htm
    




    Wednesday, November 23, 2016 11:22 AM

All replies

  • Can you go and check in Services.msc and can you check whether SQL Server services are listed their or not ?

    Can you share me LATEST details text file, This link would help you locate it. I would suggest you to upload the details file on shared drive and then share the link here. The content is big so dont post it here

    When the very first "could not find DB engine handle" error came did you made sure you followed the article completely, because it also talks about looking into errorlog file did you looked into that


    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, November 23, 2016 12:48 PM
    Moderator
  • Looking at Services.msc, yes, SLQ Server, Agent, and Browser are present; Server and Browser are running. 

    I placed my Details file to my Google Drive: https://drive.google.com/open?id=0B7UlNrRj0mgHVnZvSUhyTUZ6aTg

    When the very first error came, I did not have these instructions. I went through several installation attempts, uninstallation attempts (including deletion of file folders).

    I'm have the Errorlog but I don't know what to look for.

    Wednesday, November 23, 2016 8:45 PM
  • I'm have the Errorlog but I don't know what to look for.

    We might, so please share it.

    Then again, the first errors that occurs in the log is this Arithmetic operation resulted in an overflow and this is something that occurs in .Net code. I have not a single idea what might be causing this.

    The error Object reference not set to an instance of an object comes after this error, and could possible indicate a problem in the error handling. In any case, this is a quite generic error in .NET which means that the program is trying to use a null pointer.

    I'm afraid that I don't have very many good ideas to help you. The arithmetic overflow is a bit like things are going from bad to worse.

    Wednesday, November 23, 2016 10:30 PM
  • Here's the Errorlog:

    2016-11-23 04:40:16.53 Server      Microsoft SQL Server 2016 (SP1) (KB3182545) - 13.0.4001.0 (X64) 
    	Oct 28 2016 18:17:30 
    	Copyright (c) Microsoft Corporation
    	Developer Edition (64-bit) on Windows 10 Home 6.3 <X64> (Build 14393: )
    
    2016-11-23 04:40:16.53 Server      UTC adjustment: -6:00
    2016-11-23 04:40:16.53 Server      (c) Microsoft Corporation.
    2016-11-23 04:40:16.53 Server      All rights reserved.
    2016-11-23 04:40:16.53 Server      Server process ID is 2264.
    2016-11-23 04:40:16.53 Server      System Manufacturer: 'Dell Inc.', System Model: 'XPS L521X'.
    2016-11-23 04:40:16.53 Server      Authentication mode is MIXED.
    2016-11-23 04:40:16.53 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2016-11-23 04:40:16.53 Server      The service account is 'WORKGROUP\XPS$'. This is an informational message; no user action is required.
    2016-11-23 04:40:16.53 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
    2016-11-23 04:40:16.53 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
    2016-11-23 04:40:16.54 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.
    2016-11-23 04:40:16.54 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2016-11-23 04:40:16.54 Server      Detected 6046 MB of RAM. This is an informational message; no user action is required.
    2016-11-23 04:40:16.54 Server      Using locked pages in the memory manager.
    2016-11-23 04:40:16.58 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
    2016-11-23 04:40:16.62 Server      Buffer pool extension is already disabled. No action is necessary. 
    2016-11-23 04:40:16.67 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2016-11-23 04:40:16.74 Server      InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
    2016-11-23 04:40:16.74 Server      Implied authentication manager initialization failed. Implied authentication will be disabled.
    2016-11-23 04:40:16.76 Server      The maximum number of dedicated administrator connections for this instance is '1'
    2016-11-23 04:40:16.76 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-11-23 04:40:16.76 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-11-23 04:40:16.76 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-11-23 04:40:16.77 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2016-11-23 04:40:16.77 spid5s      Warning ******************
    2016-11-23 04:40:16.77 spid5s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2016-11-23 04:40:16.77 Server      Query Store settings initialized with enabled = 1, 
    2016-11-23 04:40:16.77 spid5s      Starting up database 'master'.
    2016-11-23 04:40:16.80 Server      Software Usage Metrics is disabled.
    2016-11-23 04:40:16.89 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.MSSQLSERVER\MSSQL\DATA\mastlog.ldf will be written.
    2016-11-23 04:40:16.99 Server      CLR version v4.0.30319 loaded.
    2016-11-23 04:40:17.24 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2016-11-23 04:40:17.29 spid5s      Converting database 'master' from version 836 to the current version 852.
    2016-11-23 04:40:17.29 spid5s      Database 'master' running the upgrade step from version 836 to version 837.
    2016-11-23 04:40:17.32 spid5s      Database 'master' running the upgrade step from version 837 to version 838.
    2016-11-23 04:40:17.34 spid5s      Database 'master' running the upgrade step from version 838 to version 839.
    2016-11-23 04:40:17.34 spid5s      Database 'master' running the upgrade step from version 839 to version 840.
    2016-11-23 04:40:17.35 spid5s      Database 'master' running the upgrade step from version 840 to version 841.
    2016-11-23 04:40:17.35 spid5s      Database 'master' running the upgrade step from version 841 to version 842.
    2016-11-23 04:40:17.41 spid5s      Database 'master' running the upgrade step from version 842 to version 843.
    2016-11-23 04:40:17.41 spid5s      Database 'master' running the upgrade step from version 843 to version 844.
    2016-11-23 04:40:17.41 spid5s      Database 'master' running the upgrade step from version 844 to version 845.
    2016-11-23 04:40:17.41 spid5s      Database 'master' running the upgrade step from version 845 to version 846.
    2016-11-23 04:40:17.42 spid5s      Database 'master' running the upgrade step from version 846 to version 847.
    2016-11-23 04:40:17.42 spid5s      Database 'master' running the upgrade step from version 847 to version 848.
    2016-11-23 04:40:17.43 spid5s      Database 'master' running the upgrade step from version 848 to version 849.
    2016-11-23 04:40:17.43 spid5s      Database 'master' running the upgrade step from version 849 to version 850.
    2016-11-23 04:40:17.44 spid5s      Database 'master' running the upgrade step from version 850 to version 851.
    2016-11-23 04:40:17.45 spid5s      Database 'master' running the upgrade step from version 851 to version 852.
    2016-11-23 04:40:17.61 spid5s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2016-11-23 04:40:17.63 spid5s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2016-11-23 04:40:17.68 spid5s      SQL Trace ID 1 was started by login "sa".
    2016-11-23 04:40:17.68 spid5s      Server name is 'XPS'. This is an informational message only. No user action is required.
    2016-11-23 04:40:17.68 spid14s     Password policy update was successful.
    2016-11-23 04:40:17.69 spid5s      Starting up database 'msdb'.
    2016-11-23 04:40:17.69 spid6s      Starting up database 'mssqlsystemresource'.
    2016-11-23 04:40:17.79 spid6s      The resource database build version is 13.00.4001. This is an informational message only. No user action is required.
    2016-11-23 04:40:18.00 spid5s      The tail of the log for database msdb is being rewritten to match the new sector size of 4096 bytes.  3584 bytes at offset 49664 in file C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA\MSDBLog.ldf will be written.
    2016-11-23 04:40:18.19 spid5s      Converting database 'msdb' from version 836 to the current version 852.
    2016-11-23 04:40:18.19 spid5s      Database 'msdb' running the upgrade step from version 836 to version 837.
    2016-11-23 04:40:18.49 spid6s      Starting up database 'model'.
    2016-11-23 04:40:18.51 spid5s      Database 'msdb' running the upgrade step from version 837 to version 838.
    2016-11-23 04:40:18.59 spid14s     A self-generated certificate was successfully loaded for encryption.
    2016-11-23 04:40:18.59 spid14s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    2016-11-23 04:40:18.60 spid14s     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-11-23 04:40:18.60 spid14s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2016-11-23 04:40:18.60 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-11-23 04:40:18.66 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/XPS ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. 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-11-23 04:40:18.69 spid5s      Database 'msdb' running the upgrade step from version 838 to version 839.
    2016-11-23 04:40:18.73 spid6s      The tail of the log for database model is being rewritten to match the new sector size of 4096 bytes.  1024 bytes at offset 72704 in file C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA\modellog.ldf will be written.
    2016-11-23 04:40:18.74 spid5s      Database 'msdb' running the upgrade step from version 839 to version 840.
    2016-11-23 04:40:18.75 spid5s      Database 'msdb' running the upgrade step from version 840 to version 841.
    2016-11-23 04:40:18.75 spid5s      Database 'msdb' running the upgrade step from version 841 to version 842.
    2016-11-23 04:40:18.84 spid6s      Converting database 'model' from version 836 to the current version 852.
    2016-11-23 04:40:18.84 spid6s      Database 'model' running the upgrade step from version 836 to version 837.
    2016-11-23 04:40:18.85 spid5s      Database 'msdb' running the upgrade step from version 842 to version 843.
    2016-11-23 04:40:18.85 spid5s      Database 'msdb' running the upgrade step from version 843 to version 844.
    2016-11-23 04:40:18.87 spid5s      Database 'msdb' running the upgrade step from version 844 to version 845.
    2016-11-23 04:40:18.87 spid5s      Database 'msdb' running the upgrade step from version 845 to version 846.
    2016-11-23 04:40:18.88 spid5s      Database 'msdb' running the upgrade step from version 846 to version 847.
    2016-11-23 04:40:18.89 spid6s      Database 'model' running the upgrade step from version 837 to version 838.
    2016-11-23 04:40:18.89 spid5s      Database 'msdb' running the upgrade step from version 847 to version 848.
    2016-11-23 04:40:18.91 spid6s      Database 'model' running the upgrade step from version 838 to version 839.
    2016-11-23 04:40:18.91 spid6s      Database 'model' running the upgrade step from version 839 to version 840.
    2016-11-23 04:40:18.92 spid6s      Database 'model' running the upgrade step from version 840 to version 841.
    2016-11-23 04:40:18.92 spid5s      Database 'msdb' running the upgrade step from version 848 to version 849.
    2016-11-23 04:40:18.93 spid6s      Database 'model' running the upgrade step from version 841 to version 842.
    2016-11-23 04:40:18.93 spid5s      Database 'msdb' running the upgrade step from version 849 to version 850.
    2016-11-23 04:40:18.96 spid6s      Database 'model' running the upgrade step from version 842 to version 843.
    2016-11-23 04:40:18.97 spid6s      Database 'model' running the upgrade step from version 843 to version 844.
    2016-11-23 04:40:18.98 spid6s      Database 'model' running the upgrade step from version 844 to version 845.
    2016-11-23 04:40:18.98 spid6s      Database 'model' running the upgrade step from version 845 to version 846.
    2016-11-23 04:40:18.99 spid6s      Database 'model' running the upgrade step from version 846 to version 847.
    2016-11-23 04:40:19.00 spid6s      Database 'model' running the upgrade step from version 847 to version 848.
    2016-11-23 04:40:19.07 spid6s      Database 'model' running the upgrade step from version 848 to version 849.
    2016-11-23 04:40:19.08 spid6s      Database 'model' running the upgrade step from version 849 to version 850.
    2016-11-23 04:40:19.09 spid5s      Database 'msdb' running the upgrade step from version 850 to version 851.
    2016-11-23 04:40:19.09 spid5s      Database 'msdb' running the upgrade step from version 851 to version 852.
    2016-11-23 04:40:19.12 spid6s      Database 'model' running the upgrade step from version 850 to version 851.
    2016-11-23 04:40:19.13 spid6s      Database 'model' running the upgrade step from version 851 to version 852.
    2016-11-23 04:40:19.27 spid6s      Polybase feature disabled.
    2016-11-23 04:40:19.27 spid6s      Clearing tempdb database.
    2016-11-23 04:40:20.26 spid6s      Starting up database 'tempdb'.
    2016-11-23 04:40:20.69 spid6s      The tempdb database has 1 data file(s).
    2016-11-23 04:40:20.80 spid5s      Recovery is complete. This is an informational message only. No user action is required.
    

    Wednesday, November 23, 2016 10:35 PM
  • The log file shared does not have any concrete information as to why SQL Server is down. Can you go to sql server services locate SQL Server service. Change startup account to NT Authority\System and then start the SQL Server, if it fails go to eventviewer or the log file(latest) and both would have reason why it failed. I believe SQL Server is started but somehow failed to bring it online

    (01) 2016-11-23 04:40:20 Slp: Sco: Attempting to initialize script
    (01) 2016-11-23 04:40:20 Slp: Sco: Attempting to initialize default connection string
    (01) 2016-11-23 04:40:21 Slp: Sco: Attempting to set script connection protocol to NotSpecified
    (01) 2016-11-23 04:40:21 Slp: Sco: Attempting to set script connection protocol to NamedPipes
    (01) 2016-11-23 04:40:21 SQLEngine: --SqlDatabaseServiceConfig: Connection String: Data Source=\\.\pipe\SQLLocal\MSSQLSERVER;Initial Catalog=master;Integrated Security=True;Pooling=False;Connect Timeout=300;Network Library=dbnmpntw;Application Name=SqlSetup
    (01) 2016-11-23 04:40:21 SQLEngine: : Checking Engine checkpoint 'ServiceConfigConnect'
    (01) 2016-11-23 04:40:21 SQLEngine: --SqlDatabaseServiceConfig: Connecting to SQL....
    (01) 2016-11-23 04:40:21 Slp: Sco: Attempting to connect script
    (01) 2016-11-23 04:40:21 Slp: Connection string: Data Source=\\.\pipe\SQLLocal\MSSQLSERVER;Initial Catalog=master;Integrated Security=True;Pooling=False;Connect Timeout=300;Network Library=dbnmpntw;Application Name=SqlSetup
    (01) 2016-11-23 04:40:21 Slp: Prompting user if they want to retry this action due to the following failure:
    (01) 2016-11-23 04:40:21 Slp: ----------------------------------------
    (01) 2016-11-23 04:40:21 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    (01) 2016-11-23 04:40:21 Slp: Inner exceptions are being indented
    (01) 2016-11-23 04:40:21 Slp: 
    (01) 2016-11-23 04:40:21 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
    (01) 2016-11-23 04:40:21 Slp:     Message: 
    (01) 2016-11-23 04:40:21 Slp:         Arithmetic operation resulted in an overflow.
    (01) 2016-11-23 04:40:21 Slp:     HResult : 0x84bb0001
    (01) 2016-11-23 04:40:21 Slp:         FacilityCode : 1211 (4bb)
    (01) 2016-11-23 04:40:21 Slp:         ErrorCode : 1 (0001)
    (01) 2016-11-23 04:40:21 Slp:     Data: 
    (01) 2016-11-23 04:40:21 Slp:       DisableRetry = true
    (01) 2016-11-23 04:40:21 Slp:     Inner exception type: System.OverflowException
    (01) 2016-11-23 04:40:21 Slp:         Message: 
    (01) 2016-11-23 04:40:21 Slp:                 Arithmetic operation resulted in an overflow.
    (01) 2016-11-23 04:40:21 Slp:         HResult : 0x80131516
    (01) 2016-11-23 04:40:21 Slp:         Stack: 
    (01) 2016-11-23 04:40:21 Slp:                 at SNIOpenSyncExWrapper(SNI_CLIENT_CONSUMER_INFO* , SNI_ConnWrapper** )
    


    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, November 24, 2016 4:49 AM
    Moderator
  • Do you mean "NT Authority\System"? I'm not able to select (under Built-in account) or type in (under "This account") using that phrase. When I select "Local System" under Built-in account I am able to proceed and Start the service, making it running. However, it does not show up under Browse for servers in Microsoft SQL Server Management Studio.

    I also tried a new installation using "NT Authority\System" as the user for Database Engine Server, but when I do this I get error "Object reference not set to an instance of an object" and the installation fails. Keep in mind, at no point have I successfully installed Database Engine Server using the installation.

    This is the summary of the most recent attempt:

    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2147467261
      Start time:                    2016-11-24 03:51:53
      End time:                      2016-11-24 04:26:58
      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:                  XPS
      Machine processor count:       4
      OS version:                    Microsoft Windows 10 Home (10.0.14393)
      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
      SQL Server 2016      MSSQLSERVER          MSSQL13.MSSQLSERVER            Database Engine Services                 1033                 Developer Edition    13.1.4001.0     No         Yes       
      SQL Server 2016      JOSEPH1              MSSQL13.JOSEPH1                Database Engine Services                 1033                 Developer Edition    13.1.4001.0     No         Yes       
      SQL Server 2016                                                          SSMS                                     1033                                      13.0.16000.28   No         Yes       
      SQL Server 2016                                                          Client Tools Connectivity                1033                                      13.0.14500.10   No         Yes       
    
    Package properties:
      Description:                   Microsoft SQL Server 2016 
      ProductName:                   SQL Server 2016
      Type:                          RTM
      Version:                       13
      Installation location:         E:\x64\setup\
      Installation edition:          Developer
    
      Slipstream:                    True
      SP Level                       1
    
    Product Update Status:
      Success: KB 3182545
    
    Product Updates Selected for Installation:
      Title:                         Microsoft SQL Server 2016  with SP1
      Knowledge Based Article:       KB 3182545
      Version:                       13.1.4001.0
      Architecture:                  x64
      Language:                      1033
    
      Update Source:                 Slipstream
    
    
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      false
      AGTSVCACCOUNT:                 NT Service\SQLAgent$JOSEPH2
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      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:         Automatic
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161124_035131\ConfigurationFile.ini
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    false
      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:                    JOSEPH2
      INSTANCENAME:                  JOSEPH2
      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:                          
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  SQL
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT Authority\System
      SQLSVCINSTANTFILEINIT:         false
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           XPS\Joseph
      SQLTELSVCACCT:                 NT Service\SQLTELEMETRY$JOSEPH2
      SQLTELSVCPASSWORD:             <empty>
      SQLTELSVCSTARTUPTYPE:          Automatic
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBFILECOUNT:            4
      SQLTEMPDBFILEGROWTH:           64
      SQLTEMPDBFILESIZE:             8
      SQLTEMPDBLOGDIR:               <empty>
      SQLTEMPDBLOGFILEGROWTH:        64
      SQLTEMPDBLOGFILESIZE:          8
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SUPPRESSPRIVACYSTATEMENTNOTICE: false
      TCPENABLED:                    0
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  Slipstream
      USEMICROSOFTUPDATE:            false
      X86:                           false
    
      Configuration file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161124_035131\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:          -2147467261
      Error description:             Object reference not set to an instance of an object.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.4001.0&EvtType=0x9C8C9C81%400x44A889F9&EvtType=0x9C8C9C81%400x44A889F9
    
    Rules with failures:
    
    Global rules:
    
    Scenario specific rules:
    
    Rules report file:               C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161124_035131\SystemConfigurationCheck_Report.htm
    
    In the Detail file, I see that there are several "Failed when querying buffer size" in my most recent installation attempt. Could this be an issue? Also I see "Error: Action "SqlEngineDBStartConfigAction_install_configrc_Cpu64" failed during execution."
    Thursday, November 24, 2016 10:34 AM
  • Do you mean "NT Authority\System"? I'm not able to select (under Built-in account) or type in (under "This account") using that phrase. When I select "Local System" under Built-in account I am able to proceed and Start the service, making it running. However, it does not show up under Browse for servers in Microsoft SQL Server Management Studio.

    Local System and NT Authority\system both are same. As you said you can being online database engine by selecting local system I guess issue is resolved here.

    Now what is not shown in browse for servers in SSMS. You can just put . which means local server and connect to sql server. 


    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, November 24, 2016 11:20 AM
    Moderator
  • Thanks for the help.

    In SSMS I am unable to connect to any SQL servers, even using "." I get the following message: "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)", also, "The semaphore timeout period has expired."

    Friday, November 25, 2016 3:45 AM
  • Thanks for the help.

    In SSMS I am unable to connect to any SQL servers, even using "." I get the following message: "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)", also, "The semaphore timeout period has expired."

    This is because you might be giving wrong name for SQL Server instance. You have two instances

    1. MSSQLSERVER which I am not sure whether running or not, you can check that from services.msc. Make sure it is started and then open SSMS and in servername put MSSQLSERVER and connect

    2. JOSEPH1, make sure this instance is running. Now to connect to this instance use Hostname\JOSEPH1 and connect.

    The error says either you are entering name incorrectly or instance is stopped


    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

    Friday, November 25, 2016 5:19 AM
    Moderator
  • I have tried both Server instances and am unable to log in using SSMS. The same error as above always appears. Both Servers are running and I've tried restarting the services. I've tried logging in as both Windows Authentication and as "sa" to no avail.
    Saturday, November 26, 2016 5:26 AM
  • I reformatted my computer and now I was able to install MS SQL Server 2016 Developer.

    This suppose this issue remains unresolved, like the many Windows 10 bugs I've experienced since being forced to upgrade to 10.

    Wednesday, December 7, 2016 9:49 AM