locked
Unable to install SQL Server (setup.exe). Exit code (Decimal) -2061893607 RRS feed

  • Question

  • Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2061893607
      Start time:                    2017-08-12 18:48:38
      End time:                      2017-08-12 18:58:32
      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:                  
      Machine processor count:       4
      OS version:                    Microsoft Windows 10 Enterprise (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

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

      Slipstream:                    True
      SP Level                       1

    Product Update Status:
      User selected not to include product updates.

    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:         Disabled
      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\20170812_184832\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:              true
      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:                         true
      QUIETSIMPLE:                   false
      ROLE:                          
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
      SQLSVCINSTANTFILEINIT:         true
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           GLOBAL\I316655
      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:                 false
      UpdateSource:                  Slipstream
      USEMICROSOFTUPDATE:            false
      X86:                           false

      Configuration file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20170812_184832\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:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      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=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

      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\20170812_184832\SystemConfigurationCheck_Report.htm

    Unable to start the Service also. Same Error Code: 2061893607 pop up show in the dialog box. As shown below.

    I tried uninstall and install again several times same. Facing same issue.

    Any help mostly appreciated. 


    • Edited by S_R_B Saturday, August 12, 2017 1:48 PM Added few more ponits
    Saturday, August 12, 2017 1:46 PM

All replies

  • Can you please look, if any sql server error log created on LOG folder

    If not please review the bootstrap log folder and needs to review the logs, can you please share the bootstrap logs using onedrive.

    https://blog.sqlauthority.com/2016/07/22/sql-server-install-error-not-find-database-engine-startup-handle/

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


    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

    Saturday, August 12, 2017 2:14 PM
  • This error means mostly means SQL Server services are installed but somehow due to some error or other reasons it is not able to come online. The reason would be in errorlog you can refer to my article shared in previous reply for more details.

    Normally a workaround is to go to SQL Server configuration manager and try starting SQL Server service with NT Authority\system account.

    Please let me know if you still face the issue


    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

    Sunday, August 13, 2017 5:54 PM
  • Hi Satish, Thanks for the response. Please find the error log file in the following link. https://1drv.ms/u/s!AgAkfRmyFb44jwPBsw5SJvvJ2Jkh Thanks, Smrutiranjan
    Monday, August 14, 2017 3:02 AM
  • Hi Satish, Thanks for the response. Please find the error log file in the following link. https://1drv.ms/u/s!AgAkfRmyFb44jwPBsw5SJvvJ2Jkh Thanks, Smrutiranjan

    The reason for which SQL Server is not coming online is

    2017-08-14 08:27:10.43 spid3s      Starting up database 'msdb'.
    2017-08-14 08:27:10.43 spid7s      Starting up database 'mssqlsystemresource'.
    2017-08-14 08:27:10.44 spid11s     Error: 17190, Severity: 16, State: 1.
    2017-08-14 08:27:10.44 spid11s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2017-08-14 08:27:10.44 spid11s     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-08-14 08:27:10.44 spid11s     Error: 17182, Severity: 16, State: 1.
    2017-08-14 08:27:10.44 spid11s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 
    2017-08-14 08:27:10.44 spid11s     Error: 17182, Severity: 16, State: 1.
    2017-08-14 08:27:10.44 spid11s     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. 

    I believe there can be 2 solution 

    1. Go to SQL Server configuration manager and change Service account of SQl Server to ANt Authority\system and restart the service do let me know if this brings service online

    2. Open the SQL Server configuration manager Under "SQL Server Network Configuration" right click on "Protocols for MSSQLSERVER" and select properties. On the certificate tab change to a certificate that exists, or if you aren't trying to encrypt the network traffic don't select any certificate. Click OK and then try starting the SQL Server Service. You may be using some certificate to encrypt SQL Server traffic and that cannot be found so this error message


    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

    Monday, August 14, 2017 6:44 AM
  • Hi Smrutiranjan,

    Can you please confirm on which account the SQL Services are running

    1) Domain Account or Local Account

    try to start the services with local system account., if the services are running with domain account.

    try to start the some other local account, for which account having admin priviliges on this box.

    For my the same kind of errors received while 2-3 years back. my case is services is running with domain account, started the services with local account but customer wants the service in domain account only. below is the fix for me

    https://support.microsoft.com/en-in/help/2023869/sql-server-fails-to-start-with-error-17182-tdssniclient-initialization

    Please let us know


    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)


    Monday, August 14, 2017 8:28 AM
  • Hi Satish,

    Earlier I was trying to start with NT account. Now I changed to Local System and the SQL service is starting. But the same is not working with SQL server Agent, still its given error as with following error logs.

    2017-08-14 14:48:02.11 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-14 14:48:02.11 Logon       Login failed for user 'GLOBAL\INLN50910206A$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2017-08-14 14:48:02.13 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-14 14:48:02.13 Logon       Login failed for user 'GLOBAL\INLN50910206A$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2017-08-14 14:55:28.66 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-14 14:55:28.66 Logon       Login failed for user 'GLOBAL\INLN50910206A$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2017-08-14 14:55:28.68 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-14 14:55:28.68 Logon       Login failed for user 'GLOBAL\INLN50910206A$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]

    Just to mention one activity I did earlier, after un-installation of SQL Server, I deleted the Microsoft SQL Server folder from c:/program files folder.  I am suspecting this error is related to that activity. Could you please let me know, IS there a way to completely remove the SQL instance and related files from system and freshly install it.

    Thanks again for the response. Will be eagerly waiting on the solution.

    -Smrutiranjan


    • Edited by S_R_B Monday, August 14, 2017 9:33 AM corrected few statements
    Monday, August 14, 2017 9:30 AM
  • Hi Shashank,

    I tried with both the option and it didn't worked.

    Thanks,

    Smrutiranjan

    Monday, August 14, 2017 9:31 AM
  • Hi Shashank,

    I tried with both the option and it didn't worked.

    Thanks,

    Smrutiranjan

    S_R_B you are contradicting your own statement to Satish you said System account is working and to me you said it is not ? BTW NT Authority\System and Local System both are same account.

    >>Login failed for user 'GLOBAL\INLN50910206A$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]

    Now did you also tried starting Agent with NT Authority\System account ? I believe you did not because of above message in italics


    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

    Monday, August 14, 2017 10:06 AM
  • Hi Shashank,

    As you provided below two solution:

    1. Go to SQL Server configuration manager and change Service account of SQl Server to ANt Authority\system and restart the service do let me know if this brings service online

    -Action -  With this the service it self is not starting.

    2. Open the SQL Server configuration manager Under "SQL Server Network Configuration" right click on "Protocols for MSSQLSERVER" and select properties. On the certificate tab change to a certificate that exists, or if you aren't trying to encrypt the network traffic don't select any certificate. Click OK and then try starting the SQL Server Service. You may be using some certificate to encrypt SQL Server traffic and that cannot be found so this error message

    -Action- Here no certificate is visible in the properties tab. The option is blank.

    That is the reason I said its not working. I am not contradicting with my statement. In the above comments Satish has mentioned to try with Local System option. which is working only for SQL Server (MSSQLSERVER). There is another service called "SQL Server Agent (MSSQLSERVER)" which is not starting up with same change. Hope this will clear the confusion. 

    Thanks,

    Smrutiranjan

    Monday, August 14, 2017 12:11 PM
  •  I am not contradicting with my statement. In the above comments Satish has mentioned to try with Local System option. which is working only for SQL Server (MSSQLSERVER). There is another service called "SQL Server Agent (MSSQLSERVER)" which is not starting up with same change. Hope this will clear the confusion. 

    Thanks,

    Smrutiranjan

    Well NT Authority\system is same as Local System account that is what I am trying to say so how can it work with Local System and not with NT Authority\system.

    Now can you tell me about account GLOBAL\INLN50910206A$. So dooes you have Global domain and INLSN50910206A$ is virtual account can you confirm you have this account in windows. Normally you can resolve this my adding this account in security and logins as new login but I doubt you would find the account GLOBAL\INLN50910206A$ can you please let me know if you can add this account into SQL Server logins giving admin privileges.

    PLease see below thread about same issue

    https://stackoverflow.com/questions/2806438/login-failed-for-user-domain-machinename


    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



    • Edited by Shanky_621MVP Monday, August 14, 2017 12:31 PM added link
    Monday, August 14, 2017 12:24 PM
  • Hi Smruthiranjan,

    Based on the error message below

    2017-08-14 14:55:28.68 Logon       Login failed for user 'GLOBAL\INLN50910206A$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]

    Can you please add this login to local admin group " GLOBAL\INLN50910206A$"

    The login name ending with dollar sign, the account belongs to systems account.

    Please try to add " 'GLOBAL\INLN50910206A$'. both Admin of box and SQL Server and let us know.


    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

    Monday, August 14, 2017 1:55 PM
  • Facing same Issue, Lots of confusion in the replies, can you finally tell me the end solution, how did you solve it?
    PLEASE HELP GUYSSSSS! URGENTLY REQUIRED

    Tuesday, August 11, 2020 5:48 AM
  • Facing same Issue, Lots of confusion in the replies, can you finally tell me the end solution, how did you solve it?
    PLEASE HELP GUYSSSSS! URGENTLY REQUIRED

    If your problem is urgent, you shoulf start a new thread describing your problem from start to end and not post in a three year old thread.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Tuesday, August 11, 2020 9:32 PM