Link to home
Start Free TrialLog in
Avatar of Wayne Barron
Wayne BarronFlag for United States of America

asked on

Server 2016 CORE - Install SQL Server 2019 - Issues.

Hello all;
Windows 2016 Server CORE
Installing = SQL Server 2019

Windows Installer was not running - started it

I took the configuration.ini file from the SQL Server setup I did earlier.
I edited it to work with Server Core.
Here is the following edit.
;SQL Server 2019 Configuration File
[OPTIONS]

; By specifying this parameter and accepting Microsoft R Open and Microsoft R Server terms, 
; you acknowledge that you have read and understood the terms of use. 

IACCEPTSQLSERVERLICENSETERMS=true

; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter. 

ACTION="InstallFailoverCluster"

; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. 
; This parameter is required when installing the SQL Server Database Engine (SQL), or Analysis Services (AS). 

INSTANCENAME="SQL2019"

; The default is Windows Authentication. Use "SQL" for Mixed Mode Authentication. Remove ; to switch on mixed mode
SECURITYMODE="SQL"

; Specify the root installation directory for shared components.  
; This directory remains unchanged after shared components are already installed. 

INSTALLSHAREDDIR="D:\SQLShared64"

; Specify the root installation directory for the WOW64 shared components.  
; This directory remains unchanged after WOW64 shared components are already installed. 

INSTALLSHAREDWOWDIR="D:\SQLSharedx86"

; Specify the Instance ID for the SQL Server features you have specified. 
; SQL Server directory structure, registry structure, 
; and service names will incorporate the instance ID of the SQL Server instance. 

INSTANCEID="SQL2019"

; Specify the installation directory. 

INSTANCEDIR="D:\SQLInstance"

; Specifies a cluster shared disk to associate with the SQL Server failover cluster instance. 

FAILOVERCLUSTERDISKS="2 - Data" "3 - Logs" "4 - Temp" "5 - Backup"

; Specifies the name of the cluster group for the SQL Server failover cluster instance. 

FAILOVERCLUSTERGROUP="SQL Server (SQL2019)"

; Specifies an encoded IP address. The encodings are semicolon-delimited (;), 
; and follow the format <IP Type>;<address>;<network name>;<subnet mask>. Supported IP types include DHCP, IPV4, and IPV6. 

FAILOVERCLUSTERIPADDRESSES="IPv4;192.168.2.44;SQLCluster;255.255.255.0"

; Specifies the name of the SQL Server failover cluster instance.  
; This name is the network name that is used to connect to SQL Server services. 

FAILOVERCLUSTERNETWORKNAME="SQLCluster"

; Agent account name 

AGTSVCACCOUNT="domain.name.local\sqlagent"
AGTSVCPASSWORD=************

; The max degree of parallelism (MAXDOP) server configuration option. 

SQLMAXDOP="2"

; Specifies a Windows collation or an SQL collation to use for the Database Engine. 

SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS"

; Account for SQL Server service: Domain\User or system account. 

SQLSVCACCOUNT="domain.name.local\sqlengine"
SQLSVCPASSWORD=************

; Supposed to set at Developer Edition???
PID=22222-00000-00000-00000-00000

; Set to "True" to enable instant file initialization for SQL Server service. 
; f enabled, Setup will grant Perform Volume Maintenance Task privilege to the Database Engine Service SID. 
; This may lead to information disclosure as it could allow deleted content to be accessed by an unauthorized principal. 

SQLSVCINSTANTFILEINIT="False"

; Windows account(s) to provision as SQL Server system administrators. 

SQLSYSADMINACCOUNTS="domain.name.local\sqlmaster01"

; The default is Windows Authentication. Use "SQL" for Mixed Mode Authentication. 

SECURITYMODE="SQL"

; The number of Database Engine TempDB files. 

SQLTEMPDBFILECOUNT="2"

; Specifies the initial size of a Database Engine TempDB data file in MB. 

SQLTEMPDBFILESIZE="8"

; Specifies the automatic growth increment of each Database Engine TempDB data file in MB. 

SQLTEMPDBFILEGROWTH="64"

; Specifies the initial size of the Database Engine TempDB log file in MB. 

SQLTEMPDBLOGFILESIZE="8"

; Specifies the automatic growth increment of the Database Engine TempDB log file in MB. 

SQLTEMPDBLOGFILEGROWTH="64"

; The Database Engine root data directory. 

INSTALLSQLDATADIR="F:\SQLDB"

; Default directory for the Database Engine backup files. 

SQLBACKUPDIR="I:\SQLBackup"

; Default directory for the Database Engine user databases. 

SQLUSERDBDIR="F:\SQLData"

; Default directory for the Database Engine user database logs. 

SQLUSERDBLOGDIR="G:\SQLLog"

; Directories for Database Engine TempDB files. 

SQLTEMPDBDIR="H:\SQLData"

; Directory for the Database Engine TempDB log files. 

SQLTEMPDBLOGDIR="H:\SQLLog"

; Add description of input argument FTSVCACCOUNT 

FTSVCACCOUNT="NT Service\MSSQLFDLauncher$SQL2019"

; Use SQLMAXMEMORY to minimize the risk of the OS experiencing detrimental memory pressure. 

SQLMAXMEMORY="2147483647"

; Use SQLMINMEMORY to reserve a minimum amount of memory available to the SQL Server Memory Manager. 

SQLMINMEMORY="0"

; Detailed help for command line argument ENU has not been defined yet. 

ENU="True"

; Parameter that controls the user interface behavior. 
; Valid values are Normal for the full UI,AutoAdvance for a simplied UI, 
; and EnableUIOnServerCore for bypassing Server Core setup GUI block. 

;UIMODE="Normal"

; Setup will not display any user interface. 

QUIET="False"

; Setup will display progress only, without any user interaction. 

QUIETSIMPLE="False"

; Displays the command line parameters usage 

HELP="False"

; Specifies that the detailed Setup log should be piped to the console. 

INDICATEPROGRESS="False"

; Specifies that Setup should install into WOW64. 
; This command-line argument is not supported on an IA64 or a 32-bit system. 

X86="False"

Open in new window


 Now, I run it like so.

PS N:\> ./Setup.exe /Q /ConfigurationFile=D:\Files\CoreSQLInstall.INI

Open in new window


 It runs for a few minutes, and then it spits out this error into the SQLSetup.log.

03/30/2020 21:19:43.898 ======================================================================
03/30/2020 21:19:44.023 Setup launched
03/30/2020 21:19:44.069 Attempting to determine media source
03/30/2020 21:19:44.132 Media source value not specified on command line argument.
03/30/2020 21:19:44.179 Setup is launched from media directly so default the value to the current folder.
03/30/2020 21:19:44.288 Media source: D:\SQL\
03/30/2020 21:19:44.351 Attempt to determine media layout based on file 'D:\SQL\mediainfo.xml'.
03/30/2020 21:19:44.444 Media layout is detected as: Full
03/30/2020 21:19:44.491 Not a slip stream media, so continuing to run setup.exe from media.
03/30/2020 21:19:44.554 /? or /HELP or /ACTION=HELP specified: false
03/30/2020 21:19:44.632 Help display: false
03/30/2020 21:19:44.663 Server-Gui-Mgmt: 0, Server-Gui-Shell: 0
03/30/2020 21:19:44.726 .Net version 4.6 is installed
03/30/2020 21:19:44.757 Local setup.exe not found, so continuing to run setup.exe from media.
03/30/2020 21:19:44.851 Name verification using runtime version v4.0.30319
03/30/2020 21:19:44.960 Strong name verification disabling is not required
03/30/2020 21:19:45.054 /? or /HELP or /ACTION=HELP specified: false
03/30/2020 21:19:45.069 Help display: false
03/30/2020 21:19:45.163 Attempting to launch landing page workflow
03/30/2020 21:19:45.194 Attempting to set setup mutex
03/30/2020 21:19:45.241 Setup mutex has been set
03/30/2020 21:19:45.288 Attempting to launch user requested workflow from media
03/30/2020 21:19:45.335 Media source: D:\SQL\
03/30/2020 21:19:45.398 Install media path: D:\SQL\x64\setup\
03/30/2020 21:19:45.554 Media layout: Full
03/30/2020 21:19:45.773 Attempting to get execution timestamp
03/30/2020 21:19:45.882 Timestamp: 20200330_211943
03/30/2020 21:19:45.976 Attempting to run user requested action from media ScenarioEngine.exe
03/30/2020 21:19:46.038 Attempting to launch process D:\SQL\x64\ScenarioEngine.exe
03/30/2020 21:21:55.399 Process returned exit code: 0x84B30002
03/30/2020 21:21:55.524 Media ScenarioEngine.exe returned exit code: 0x84B30002
03/30/2020 21:21:55.556 Attempting to release setup mutex
03/30/2020 21:21:55.618 Setup mutex has been released
03/30/2020 21:21:55.696 Setup closed with exit code: 0x84C40013
03/30/2020 21:21:55.806 ======================================================================

Open in new window


The next step I took was to copy the contents from the Virtual CD to my D:\SQL
And it ran for the same amount of time, and then produced that same error.

Any assistance on this would be great.
I am not going to let this SQL Core Server beat me.

Wayne
Avatar of arnold
arnold
Flag of United States of America image

If not mistaken, you

Did you mean to install as a cluster?

The error follows the run of Attempting to launch process D:\SQL\x64\ScenarioEngine.exe
In a core, I think you should run in quiete mode, you currently have that optio set to false, I also did not notice the euaaccept.
See if the following helps.

https://docs.microsoft.com/en-us/sql/database-engine/install-windows/configure-sql-server-on-a-server-core-installation?view=sql-server-ver15

iaccept............sqlicence

Double check your references for storage ...
Avatar of Wayne Barron

ASKER

I removed these lines from the script.

; Setup will not display any user interface. 

QUIET="False"

; Setup will display progress only, without any user interaction. 

QUIETSIMPLE="False"

Open in new window


I have in my line I run.
/Q
PS N:\> ./Setup.exe /Q /ConfigurationFile=D:\Files\CoreSQLInstall.INI

Open in new window


Line 7
IACCEPTSQLSERVERLICENSETERMS=true

>>> Double check your references for storage
If you are referring to the location (drives) I am installing to.
I just checked to make sure this server core still has the Virtual disks assigned to it, and it does.

I still get the same error when I try to install.
So, I got my hands on the summary.txt file.
It does actually exist.

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068643838
  Exit facility code:            1203
  Exit error code:               2
  Exit message:                  The state of your SQL Server installation was not changed after the setup execution. Please review the summary.txt logs for further details.
  Start time:                    2020-03-31 04:50:12
  End time:                      2020-03-31 04:52:58
  Requested action:              InstallFailoverCluster

Cluster properties:
  Machine name: SQLCORE-02
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered  Configured

  Machine name: SQLCORE-01
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered  Configured

Machine Properties:
  Machine name:                  SQLCORE-01
  Machine processor count:       2
  OS version:                    Microsoft Windows Server 2016 Datacenter Evaluation - ServerCore (10.0.14393)
  OS service pack:               
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  Yes

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

Package properties:
  Description:                   Microsoft SQL Server 2019 
  ProductName:                   SQL Server 2019
  Type:                          RTM
  Version:                       15
  SPLevel:                       0
  Installation location:         N:\x64\setup\
  Installation edition:          Developer

Product Update Status:
  None discovered.

User Input Settings:
  ACTION:                        InstallFailoverCluster
  AGTDOMAINGROUP:                <empty>
  AGTSVCACCOUNT:                 domain.name.local\sqlagent
  AGTSVCPASSWORD:                *****
  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>
  ASTEMPDIR:                     Temp
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20200331_045005\ConfigurationFile.ini
  ENU:                           true
  EXTSVCACCOUNT:                 <empty>
  EXTSVCPASSWORD:                <empty>
  FAILOVERCLUSTERDISKS:          2 - Data, 3 - Logs, 4 - Temp, 5 - Backup
  FAILOVERCLUSTERGROUP:          SQL Server (SQL2019)
  FAILOVERCLUSTERIPADDRESSES:    IPv4;192.168.2.44;SQLCluster;255.255.255.0
  FAILOVERCLUSTERNETWORKNAME:    SQLCluster
  FEATURES:                      
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SQL2019
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTPYTHONLICENSETERMS:     false
  IACCEPTROPENLICENSETERMS:      false
  IACKNOWLEDGEENTCALLIMITS:      false
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              D:\SQLShared64
  INSTALLSHAREDWOWDIR:           D:\SQLSharedx86
  INSTALLSQLDATADIR:             F:\SQLDB
  INSTANCEDIR:                   D:\SQLInstance
  INSTANCEID:                    SQL2019
  INSTANCENAME:                  SQL2019
  ISMASTERSVCACCOUNT:            NT AUTHORITY\Network Service
  ISMASTERSVCPASSWORD:           <empty>
  ISMASTERSVCPORT:               8391
  ISMASTERSVCSSLCERTCN:          <empty>
  ISMASTERSVCSTARTUPTYPE:        Automatic
  ISMASTERSVCTHUMBPRINT:         <empty>
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  ISWORKERSVCACCOUNT:            NT AUTHORITY\Network Service
  ISWORKERSVCCERT:               <empty>
  ISWORKERSVCMASTER:             <empty>
  ISWORKERSVCPASSWORD:           <empty>
  ISWORKERSVCSTARTUPTYPE:        Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  MRCACHEDIRECTORY:              
  PBDMSSVCACCOUNT:               <empty>
  PBDMSSVCPASSWORD:              <empty>
  PBDMSSVCSTARTUPTYPE:           0
  PBENGSVCACCOUNT:               <empty>
  PBENGSVCPASSWORD:              <empty>
  PBENGSVCSTARTUPTYPE:           0
  PBPORTRANGE:                   <empty>
  PBSCALEOUT:                    false
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   true
  RSINSTALLMODE:                 DefaultNativeMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  SQL
  SQLBACKUPDIR:                  I:\SQLBackup
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLJAVADIR:                    <empty>
  SQLMAXDOP:                     2
  SQLMAXMEMORY:                  2147483647
  SQLMINMEMORY:                  0
  SQLSVCACCOUNT:                 domain.name.local\sqlengine
  SQLSVCINSTANTFILEINIT:         false
  SQLSVCPASSWORD:                *****
  SQLSYSADMINACCOUNTS:           domain.name.local\sqlmaster01
  SQLTEMPDBDIR:                  H:\SQLData
  SQLTEMPDBFILECOUNT:            2
  SQLTEMPDBFILEGROWTH:           64
  SQLTEMPDBFILESIZE:             8
  SQLTEMPDBLOGDIR:               H:\SQLLog
  SQLTEMPDBLOGFILEGROWTH:        64
  SQLTEMPDBLOGFILESIZE:          8
  SQLUSERDBDIR:                  F:\SQLData
  SQLUSERDBLOGDIR:               G:\SQLLog
  SUPPRESSPAIDEDITIONNOTICE:     false
  SUPPRESSPRIVACYSTATEMENTNOTICE: false
  UIMODE:                        Normal
  UpdateEnabled:                 true
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  USESQLRECOMMENDEDMEMORYLIMITS: true
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20200331_045005\ConfigurationFile.ini

Rules with failures or warnings:

Global rules:
Warning    Cluster_VerifyForWarnings        The MSCS cluster has been validated but there are warnings in the MSCS cluster validation report, or some tests were skipped while running the validation. To continue, run validation from the Windows Cluster Administration tool to ensure that the MSCS cluster validation has been run and that the MSCS cluster validation report does not contain errors.
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=2094702 for information about ports to open for each feature.

Rules report file:               C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20200331_045005\SystemConfigurationCheck_Report.htm

Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented

Exception type: Microsoft.SqlServer.Setup.Chainer.Workflow.NoopWorkflowException
    Message: 
        The state of your SQL Server installation was not changed after the setup execution. Please review the summary.txt logs for further details.
    HResult : 0x84b30002
        FacilityCode : 1203 (4b3)
        ErrorCode : 2 (0002)

Open in new window


Warning    Cluster_VerifyForWarnings
I had already run the validation on the Clustered Nodes, and there were no errors.
Just the typical warnings.

Warning    IsFirewallEnabled
I have already opened the firewall ports prior.

SystemConfigurationCheck_Report.htm (View here)
http://ee.cffcs.com/SystemConfigurationCheck_Report.htm
ASKER CERTIFIED SOLUTION
Avatar of Wayne Barron
Wayne Barron
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Good job eh! :)
Thanks, Phillip.
I was very pleased with myself when I finally got that progress bar going across.
I know that it is best to have this on complete Silent mode.
But when you are testing and trying to get things to work right.
Being able to see WHERE it is at before it dumps, is a good thing.
So, /QS is a lifesaver on this part.

Have a good week.
Wayne