unable to install sql server 2022 developer edition

Question

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068052377
  Start time:                    2023-04-24 12.53.43
  End time:                      2023-04-24 12:54:10
  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, and then try the setup process again.


Machine Properties:
  Machine name:                  GAUTAM
  Machine processor count:       8
  OS version:                    Microsoft Windows 11 Home Single Language (10.0.22621)
  OS service pack:               
  OS region:                     India
  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 2022 
  ProductName:                   SQL Server 2022
  Type:                          RTM
  Version:                       16
  SPLevel:                       0
  Installation location:         C:\SQL2022\Developer_ENU\x64\setup\
  Installation edition:          Developer

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

Notice: Please read Microsoft SQL Server Software License Terms at aka.ms/useterms.

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:                  TABULAR
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTELSVCACCT:                  <empty>
  ASTELSVCPASSWORD:              <empty>
  ASTELSVCSTARTUPTYPE:           0
  ASTEMPDIR:                     Temp
  AZUREARCPROXYSERVER:           <empty>
  AZUREBILLEDEDITION:            
  AZUREREGION:                   <empty>
  AZURERESOURCEGROUP:            <empty>
  AZURESERVICEPRINCIPAL:         <empty>
  AZURESERVICEPRINCIPALSECRET:   <empty>
  AZURESUBSCRIPTIONID:           <empty>
  AZURETENANTID:                 <empty>
  BROWSERSVCSTARTUPTYPE:         Disabled
  CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20230424_125342\ConfigurationFile.ini
  ENABLERANU:                    false
  ENU:                           true
  EXTSVCACCOUNT:                 <empty>
  EXTSVCPASSWORD:                <empty>
  FEATURES:                      SQLENGINE
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTSQLSERVERLICENSETERMS:  true
  IACKNOWLEDGEENTCALLIMITS:      false
  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
  ISMASTERSVCACCOUNT:            NT AUTHORITY\Network Service
  ISMASTERSVCPASSWORD:           <empty>
  ISMASTERSVCPORT:               8391
  ISMASTERSVCSSLCERTCN:          <empty>
  ISMASTERSVCSTARTUPTYPE:        Automatic
  ISMASTERSVCTHUMBPRINT:         <empty>
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  ISTELSVCACCT:                  <empty>
  ISTELSVCPASSWORD:              <empty>
  ISTELSVCSTARTUPTYPE:           0
  ISWORKERSVCACCOUNT:            NT AUTHORITY\Network Service
  ISWORKERSVCCERT:               <empty>
  ISWORKERSVCMASTER:             <empty>
  ISWORKERSVCPASSWORD:           <empty>
  ISWORKERSVCSTARTUPTYPE:        Automatic
  NPENABLED:                     0
  PBDMSSVCACCOUNT:               <empty>
  PBDMSSVCPASSWORD:              <empty>
  PBDMSSVCSTARTUPTYPE:           0
  PBENGSVCACCOUNT:               <empty>
  PBENGSVCPASSWORD:              <empty>
  PBENGSVCSTARTUPTYPE:           0
  PBPORTRANGE:                   <empty>
  PID:                           *****
  PRODUCTCOVEREDBYSA:            false
  QUIET:                         true
  QUIETSIMPLE:                   false
  ROLE:                          
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLMAXDOP:                     8
  SQLMAXMEMORY:                  2147483647
  SQLMINMEMORY:                  0
  SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
  SQLSVCINSTANTFILEINIT:         true
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           GAUTAM\gauta
  SQLTELSVCACCT:                 NT Service\SQLTELEMETRY
  SQLTELSVCPASSWORD:             <empty>
  SQLTELSVCSTARTUPTYPE:          Automatic
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBFILECOUNT:            8
  SQLTEMPDBFILEGROWTH:           64
  SQLTEMPDBFILESIZE:             8
  SQLTEMPDBLOGDIR:               <empty>
  SQLTEMPDBLOGFILEGROWTH:        64
  SQLTEMPDBLOGFILESIZE:          8
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SUPPRESSPAIDEDITIONNOTICE:     false
  SUPPRESSPRIVACYSTATEMENTNOTICE: false
  TCPENABLED:                    0
  UIMODE:                        Normal
  UpdateEnabled:                 false
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  USESQLRECOMMENDEDMEMORYLIMITS: false

  Configuration file:            C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20230424_125342\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          1639
  Component log file:            C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20230424_125342\sql_engine_core_inst_Cpu64_1.log
  Error description:             Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=16.0.1000.6&EvtType=sql_engine_core_inst.msi%400x162A16FE%400x1639

  Feature:                       SQL Browser
  Status:                        Passed

  Feature:                       SQL Writer
  Status:                        Passed

  Feature:                       Setup Support Files
  Status:                        Passed

Rules with failures or warnings:

Global rules:
Warning    IsFirewallEnabled                The Windows Firewall is enabled. Make sure the appropriate ports are open to enable remote access. See the rules documentation at https://go.microsoft.com/fwlink/?linkid=2162127 for information about ports to open for each feature.

Rules report file:               C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20230424_125342\SystemConfigurationCheck_Report.htm

Answer 1

Hi @Gautam Kumar Behera

Based on your error code, I found this link for you. If these methods don't work, please provide a detailed .txt so we can learn more about the error. https://bobcares.com/blog/sql-server-error-1639/

Best regards,

Aniya

Answer 2

this path was not there after reinstalling, C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER

I was apparently overly optimistic there. Apparently SQL Server was never installed. Which is logical given the slew of errors. The log you found is for Analysis Services. Here is a tip: unless you actually know what that is, and you plan to use it, don't select it for the installation. It's a bit specialised feature. (I don't know it myself.)

OK, we have to go to the first exception: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.

It's certainly not the first time I've seen this in the forums, but alas I still don't know how to deal with it. It sounds like there is a more general Windows problem. (WMI is a Windows component.) But when I googled on the message, all hits seemed to be related to SQL Server.

Many of the hits were about as confused as we are over the error, but this one seemed to be from someone who was able to deal with it: https://mikerodionov.com/unable-to-install-sql-server-2019-sql-install-error-the-mof-compiler-could-not-connect-with-the-wmi-server/ This one also suggests a solution: https://developer.milestonesys.com/s/article/MOF-compiler-could-not-connect-with-the-WMI-server but I cannot vouch for it will work.

As you may understand, you may have to work quite a bit to get things in order. You may get past this error, and then it may fail on the next. It is not really tenable to ask in the forum for every case, but you will need to read the logs yourself. (The reason it is not tenable is that we are not really much more clueful that you are.) If you come as far as actually having an ERRORLOG file, and things still fail, we are more on our home ground, that is SQL Server and can help better.

Another alternative might be to create a virtual machine and have SQL Server running on the VM.