MSSQL Failover Cluster - Failed instance installation

[Chris-1992]

Goedenavond Tweakers,

Ik ben een failover Cluster voor SQL aan het proberen opzetten maar bij het installeren van de eerste instance loopt het fout.
Waar door de andere dependencies ook niet geïnstalleerd kunnen worden.


Software:

Vmware om alles te virtualiseren
FreeNAS voor iSCSI
Windows 2019 (DC)
Windows 2019 (SQL Node 1) (MSSQL 14.0)
Windows 2019 (SQL Node 2) (MSSQL 14.0)

Ik heb SQL Node 1 & 2 in een windows failover cluster hangen met de naam SQL-Cluster en een ISCSI cluster disk.(Quorum disk & Data Disk)
(Valt ene uit gaat de disk naar de andere, dit werkt correct)

Dan begin ik met de SQL Installatie (Standaard evaluatie licentie):




Daar gaat hij vlekkeloos door tot op het laatste hij de Instance effectief moet installeren (Onderweg geen errors of warnings bij checks)




De instance service account is een Domain Admin waaronder hij geïnstalleerd wordt.
Een repair lukt niet dan geeft hij de foutmelding dat er geen repair kan uitgevoerd worden op een instance dat nog nooit gewerkt heeft.

Heeft iemand enige ideetjes?
Error logs volgen nog maar hier staat vooral in: Ga naar de microsoft website of installeer de instance opnieuw
Ik heb onderstaande "handleiding" gevolgd:
YouTube: SQL Server 2012 Failover Cluster Installation & Configuration Step B...


Logging: (Logging is van een 2e test met Windows 2016)
Dit geeft juist de zelfde issues.

Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068774911
Start time: 2019-02-13 23:28:20
End time: 2019-02-13 23:48:47
Requested action: InstallFailoverCluster

Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.


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

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

Machine Properties:
Machine name: SRV2016-SQL-02
Machine processor count: 8
OS version: Microsoft Windows Server 2016 Standard Evaluation (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 2017
ProductName: SQL Server 2017
Type: RTM
Version: 14
SPLevel: 0
Installation location: C:\Users\SQLadmin\Downloads\Tools\x64\setup\
Installation edition: Evaluation

Product Update Status:
User selected not to include product updates.
Error message:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented

Exception type: Microsoft.SqlServer.Configuration.SmartSetupExtension.MuAddServerException
Message:
SQL Server Setup failed to register the Microsoft Update service. This may indicate that the Windows Update service does not have online access to the Microsoft Update server or Windows Server Update Services.
HResult : 0x85190002
FacilityCode : 1305 (519)
ErrorCode : 2 (0002)
Data:
WatsonData = Microsoft.SqlServer.Configuration.SmartSetupExtension.MuAddServerException@2
Stack:
at Microsoft.SqlServer.Configuration.SmartSetupExtension.MuSetupSearchEngine.SelectServer()
at Microsoft.SqlServer.Configuration.SmartSetupExtension.MuSetupSearchEngine.SearchUpdates()
at Microsoft.SqlServer.Configuration.SmartSetupExtension.SearchUpdatesAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
Inner exception type: Microsoft.SqlServer.Configuration.SmartSetupExtension.WuaAddServiceException
Message:
Failed to register service '7971f918-a847-4430-9279-4a52d1efe18d' with Windows Update Agent. Error: Exception from HRESULT: 0x80072EE2
HResult : 0x85170002
FacilityCode : 1303 (517)
ErrorCode : 2 (0002)
Data:
ServiceID = 7971f918-a847-4430-9279-4a52d1efe18d
ErrorMessage = Exception from HRESULT: 0x80072EE2
WatsonData = Microsoft.SqlServer.Configuration.SmartSetupExtension.WuaAddServiceException@2
Stack:
at Microsoft.SqlServer.Configuration.SmartSetupExtension.WuaUpdateServiceManager.AddService(String serviceID)
at Microsoft.SqlServer.Configuration.SmartSetupExtension.MuSearchUtility.GetManagedOrWuService(ServiceContainer context)
Inner exception type: System.Runtime.InteropServices.COMException
Message:
Exception from HRESULT: 0x80072EE2
HResult : 0x80072ee2
Stack:
at Microsoft.SqlServer.Interop.WUApiLib.UpdateServiceManagerClass.AddService2(String ServiceID, Int32 flags, String authorizationCabPath)
at Microsoft.SqlServer.Configuration.SmartSetupExtension.WuaUpdateServiceManager.AddService(String serviceID)


User Input Settings:
ACTION: InstallFailoverCluster
AGTDOMAINGROUP: <empty>
AGTSVCACCOUNT: DIGITALKEY\SQLadmin
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\140\Setup Bootstrap\Log\20190213_232812\ConfigurationFile.ini
ENU: true
FAILOVERCLUSTERDISKS: Cluster Disk 1
FAILOVERCLUSTERGROUP: SQL Server (ADSOLUT)
FAILOVERCLUSTERIPADDRESSES: IPv4;172.10.10.234;VRT;255.255.255.0
FAILOVERCLUSTERNETWORKNAME: ADSCluster2016
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$ADSOLUT
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTPYTHONLICENSETERMS: false
IACCEPTROPENLICENSETERMS: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: E:\
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: ADSOLUT
INSTANCENAME: ADSOLUT
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: false
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: DIGITALKEY\SQLadmin
SQLSVCINSTANTFILEINIT: false
SQLSVCPASSWORD: *****
SQLSYSADMINACCOUNTS: DIGITALKEY\SQLadmin
SQLTEMPDBDIR: <empty>
SQLTEMPDBFILECOUNT: 8
SQLTEMPDBFILEGROWTH: 64
SQLTEMPDBFILESIZE: 8
SQLTEMPDBLOGDIR: <empty>
SQLTEMPDBLOGFILEGROWTH: 64
SQLTEMPDBLOGFILESIZE: 8
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SUPPRESSPRIVACYSTATEMENTNOTICE: false
UIMODE: Normal
UpdateEnabled: false
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false

Configuration file: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190213_232812\ConfigurationFile.ini

Detailed results:
Feature: Data Quality Services
Status: Failed
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: https://go.microsoft.com/...%400x4BDAF9BA%401306%4026

Feature: Full-Text and Semantic Extractions for Search
Status: Failed
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: https://go.microsoft.com/...%400x4BDAF9BA%401306%4026

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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: https://go.microsoft.com/...%400x4BDAF9BA%401306%4026

Feature: SQL Server Replication
Status: Failed
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: https://go.microsoft.com/...%400x4BDAF9BA%401306%4026

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:

There are no scenario-specific rules.

Rules report file: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190213_232812\SystemConfigurationCheck_Report.htm

[ Voor 91% gewijzigd door Chris-1992 op 14-02-2019 00:44 ]

[flashback1989]

heeft de machine geen internet toegang?. ik zie dat je check for updates uit hebt staan. zou hem aanvinken . wellicht is er al een bugfix voor de install media die je zo binnenhaalt

sowieso na de instal even de laatste updates binnen halen ( zie sqlserverupdates.com voor welke dat nu zijn)

[Chris-1992]

@flashback1989
Toestel heeft wel internet toegang, heb de updates bewust uitgeschakeld.

Ik ge het zaterdag even testen en post ik het resultaat!

-edit-
@flashback1989
Ik heb SQL 2016 geïnstalleerd met windows update, zelfde foutmelding.

[ Voor 25% gewijzigd door Chris-1992 op 17-02-2019 14:06 ]

[Chris-1992]

Nog iemand een ideetje?

[Henkje.doc]

Uitsluiten of het aan de clusterconfigurafie ligt. Kun je binnen de clustermanager een validatie doen?

SQL versies hebben niet perse internet toegang nodig, maar wel gek dat hij dat aangeeft.

Lukt installatie van een losse SQL instance op beide nodes wel zonder problemen?

[Chris-1992]

@Henkje.doc
Ik weet niet hoe ik het rapport hier kan posten maar hij gaf hier een warning: (Windows update)
Die zijn ondertussen gebeurd maar probleem blijft zich voordoen.






KB Article

Title

Support

Security Bulletins


3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [lt-LT] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [ms-MY] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [ta-IN] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [te-IN] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [bn-BD] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [hu-HU] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [id-ID] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [ml-IN] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [gl-ES] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [sk-SK] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [bn-IN] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [he-IL] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [en-GB] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [pa-IN] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [zh-TW] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [it-IT] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [el-GR] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [ar-SA] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [ru-RU] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [th-TH] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [fr-FR] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [is-IS] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [bg-BG] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [es-ES] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [eu-ES] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [uk-UA] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [hr-HR] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [nl-NL] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [pt-PT] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [fi-FI] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [mr-IN] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [sl-SI] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [gu-IN] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [ja-JP] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [pl-PL] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [ca-ES] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [es-MX] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [ko-KR] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [pt-BR] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [lv-LV] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [zh-CN] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [sv-SE] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [nb-NO] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [tr-TR] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [ro-RO] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [da-DK] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [et-EE] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [vi-VN] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [zh-HK] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [cs-CZ] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [en-US] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [de-DE] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [hi-IN] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [nn-NO] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [ur-PK] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [sr-Latn-RS] http://support.microsoft.com/kb/3193497
3193497 LanguageFeatureOnDemand - Windows Server 2016 for AMD64-based Systems - (KB3193497) [kn-IN] http://support.microsoft.com/kb/3193497

[Henkje.doc]

Heb verder in de logfile zitten spitten:

SQLSVCACCOUNT: DIGITALKEY\SQLadmin

Je gebruikt hetzelfde account voor de sql server service als voor je sysadmininistratos.
Krijg je eenzelfde soort foutmelding als je een ander soort account configureert?.

[ Voor 28% gewijzigd door Henkje.doc op 20-02-2019 11:31 . Reden: aanpassing in werkwijze ]

[Chris-1992]

@Henkje.doc
Testen met een gewone domain user dan?
Ik ga de installatie nu uitvoeren en post het resultaat hier.

-EDIT-

Komt met zelfde foutmelding.

)Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068774911
Start time: 2019-02-20 21:05:53
End time: 2019-02-20 21:25:18
Requested action: InstallFailoverCluster

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.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.


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

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

Machine Properties:
Machine name: SRV2016-SQL-02
Machine processor count: 8
OS version: Microsoft Windows Server 2016 Standard Evaluation (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 2016
ProductName: SQL Server 2016
Type: RTM
Version: 13
Installation location: C:\Data_Adsolut\Adsolut\Tools\SQL_Srv_Std_2016SP2-CU4\x64\setup\
Installation edition: Evaluation

Slipstream: True
SP Level 2

Product Update Status:
Success: KB 4052908

Product Updates Selected for Installation:
Title: Microsoft SQL Server 2016 with SP2
Knowledge Based Article: KB 4052908
Version: 13.2.5026.0
Architecture: x64
Language: 1033

Update Source: Slipstream


User Input Settings:
ACTION: InstallFailoverCluster
AGTDOMAINGROUP: <empty>
AGTSVCACCOUNT: DIGITALKEY\Test.u
AGTSVCPASSWORD: *****
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>
ASTEMPDIR: Temp
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20190220_210548\ConfigurationFile.ini
ENU: true
FAILOVERCLUSTERDISKS: Cluster Disk 1
FAILOVERCLUSTERGROUP: SQL Server (MSSQLSERVER)
FAILOVERCLUSTERIPADDRESSES: IPv4;172.10.10.234;VRT;255.255.255.0
FAILOVERCLUSTERNETWORKNAME: ADSCluster
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
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: E:\
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: 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: false
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: DIGITALKEY\Test.u
SQLSVCINSTANTFILEINIT: false
SQLSVCPASSWORD: *****
SQLSYSADMINACCOUNTS: DIGITALKEY\SQLadmin
SQLTEMPDBDIR: <empty>
SQLTEMPDBFILECOUNT: 8
SQLTEMPDBFILEGROWTH: 64
SQLTEMPDBFILESIZE: 8
SQLTEMPDBLOGDIR: <empty>
SQLTEMPDBLOGFILEGROWTH: 64
SQLTEMPDBLOGFILESIZE: 8
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SUPPRESSPRIVACYSTATEMENTNOTICE: false
UIMODE: Normal
UpdateEnabled: true
UpdateSource: Slipstream
USEMICROSOFTUPDATE: false
X86: false

Configuration file: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20190220_210548\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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/f...%400x4BDAF9BA%401306%4026

Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/f...%400x4BDAF9BA%401306%4026

Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/f...%400x4BDAF9BA%401306%4026

Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/f...%400x4BDAF9BA%401306%4026

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:

There are no scenario-specific rules.

Rules report file: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20190220_210548\SystemConfigurationCheck_Report.htm

Logging van manueel starten.

2019-02-20 21:35:03.08 Server Microsoft SQL Server 2016 (SP2) (KB4052908) - 13.0.5026.0 (X64)
Mar 18 2018 09:11:49
Copyright (c) Microsoft Corporation
Enterprise Evaluation Edition (64-bit) on Windows Server 2016 Standard Evaluation 10.0 <X64> (Build 14393: ) (Hypervisor)

2019-02-20 21:35:03.08 Server UTC adjustment: 1:00
2019-02-20 21:35:03.08 Server (c) Microsoft Corporation.
2019-02-20 21:35:03.11 Server All rights reserved.
2019-02-20 21:35:03.11 Server Server process ID is 7680.
2019-02-20 21:35:03.11 Server System Manufacturer: 'VMware, Inc.', System Model: 'VMware7,1'.
2019-02-20 21:35:03.12 Server Authentication mode is MIXED.
2019-02-20 21:35:03.12 Server Logging SQL Server messages in file 'E:\MSSQL13.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2019-02-20 21:35:03.12 Server The service account is 'DIGITALKEY\SQLadmin'. This is an informational message; no user action is required.
2019-02-20 21:35:03.12 Server Registry startup parameters:
-d E:\MSSQL13.MSSQLSERVER\MSSQL\DATA\master.mdf
-e E:\MSSQL13.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l E:\MSSQL13.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2019-02-20 21:35:03.12 Server SQL Server detected 2 sockets with 4 cores per socket and 4 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2019-02-20 21:35:03.12 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-02-20 21:35:03.12 Server Detected 8190 MB of RAM. This is an informational message; no user action is required.
2019-02-20 21:35:03.12 Server Using conventional memory in the memory manager.
2019-02-20 21:35:03.34 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2019-02-20 21:35:03.43 Server Buffer pool extension is already disabled. No action is necessary.
2019-02-20 21:35:03.53 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2019-02-20 21:35:03.56 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2019-02-20 21:35:03.60 Server The maximum number of dedicated administrator connections for this instance is '1'
2019-02-20 21:35:03.61 Server This instance of SQL Server last reported using a process ID of 6572 at 20/02/2019 21:32:52 (local) 20/02/2019 20:32:52 (UTC). This is an informational message only; no user action is required.
2019-02-20 21:35:03.61 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2019-02-20 21:35:03.65 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.
2019-02-20 21:35:03.66 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.
2019-02-20 21:35:03.69 Server Query Store settings initialized with enabled = 1,
2019-02-20 21:35:03.71 spid2s Starting up database 'master'.
2019-02-20 21:35:03.72 Server In-Memory OLTP initialized on lowend machine.
2019-02-20 21:35:03.77 spid2s There have been 256 misaligned log IOs which required falling back to synchronous IO. The current IO is on file E:\MSSQL13.MSSQLSERVER\MSSQL\DATA\master.mdf.
2019-02-20 21:35:03.77 Server CLR version v4.0.30319 loaded.
2019-02-20 21:35:03.78 spid2s Unable to create stack dump file due to stack shortage (ex_terminator - Last chance exception handling)
2019-02-20 21:35:03.78 spid2s Stack Signature for the dump is 0x0000000000000000
2019-02-20 21:35:03.92 spid2s DumpCallbackHk::InitializePaths: at 2714 failed at wcsrchr with error: 0x00000000
2019-02-20 21:35:03.93 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2019-02-20 21:35:05.84 Server Software Usage Metrics is disabled.

[ Voor 126% gewijzigd door Chris-1992 op 20-02-2019 21:40 ]

[Henkje.doc]

Ok dus als het ik het goed begrijp werkt een standalone installatie ook niet.
Heb zelf ook nog even gekeken met een Windows 2019 virtualbox machine met daarop SQL 2016 SP1 en dat werkte standalone zonder problemen.

Aan de foutmeldingen te zien lijkt er wel iets met het storage deel aan de hand te zijn. Mocht je met de failover clustering aan de slag zijn. Ziet je failover cluster wel de disken?

[Chris-1992]

Henkje.doc schreef op donderdag 21 februari 2019 @ 20:12:
Ok dus als het ik het goed begrijp werkt een standalone installatie ook niet.
Heb zelf ook nog even gekeken met een Windows 2019 virtualbox machine met daarop SQL 2016 SP1 en dat werkte standalone zonder problemen.

Aan de foutmeldingen te zien lijkt er wel iets met het storage deel aan de hand te zijn. Mocht je met de failover clustering aan de slag zijn. Ziet je failover cluster wel de disken?

Standalone lukt zonder problemen.

De storage zie ik en kan ik data op plaatsen.
deze kan ik ook switchen tussen de nodes

[Henkje.doc]

Ok rechten technisch op node niveau in orde. Bij een SQL cluster wordt er voor de SQL clusternaam een eigen ip en naam aangemaakt in de ad. Dat moet natuurlijk wel kunnen.

Foutmelding in de setuplog is nog hetzelfde als in het begin van deze post?

Wist:

Enige wat opvalt is de i/o melding.
MSDN: Message misaligned log IOs which required falling back to synchronous I...

Blocksize van de disken in orde?

[ Voor 49% gewijzigd door Henkje.doc op 22-02-2019 06:47 ]

[Chris-1992]

Ik heb de installatie helaas niet meer staan en kan het niet controleren.
Maar mogelijks heb ik de SQL en DC samen geïnstalleerd, dit heb ik vandaag gevonden:

https://docs.microsoft.co...l-server-ver15#DC_support

SQL Server failover cluster instances are not supported where cluster nodes are domain controllers.

[sl0w]

Ha Chris,

Ik zag dat je nog vrij recent had geageerd. Ik liep met een identieke opstelling tegen hetzelfde probleem aan, alhoewel ik de SQL niet combineerde met een DC.

Bij mij was de oplossing het uitschakelen van de physical block size reporting op het ISCI volume op Freenas:


Hopelijk heb je er nog wat aan in een eventuele toekomstige opzet.

[Gé Brander]

Als overweging voor de toekomst als je een geclusterde/hoogbeschikbare database omgeving wil gaan bouwen probeer dan vooral Availability Groups te gebruiken en niet meer de cluster shared storage optie. Met dat eerste heb je een single point of failure minder.

[Question Mark]

Nadeel is wel dat je met een Standard editie van SQL maximaal één database kunt gebruiken. Wil je meer dan moet je naar de prijzige Enterprise calls.

Vandaar dat ik eigenlijk ten alle tijde SQL mirroring prefereer, mits de applicatie daar ondersteuning voor heeft.

[Gé Brander]

Question Mark schreef op maandag 5 oktober 2020 @ 08:08:
Nadeel is wel dat je met een Standard editie van SQL maximaal één database kunt gebruiken. Wil je meer dan moet je naar de prijzige Enterprise calls.

Vandaar dat ik eigenlijk ten alle tijde SQL mirroring prefereer, mits de applicatie daar ondersteuning voor heeft.

Het is één database per AG binnen Standard. Je kan dus prima meerdere AG's hebben met ieder hun eigen database. Dat is prima te doen zolang je geen afhankelijkheden hebt tussen databases, anders moet je inderdaad naar Enterprise.

[Question Mark]

Gé Brander schreef op maandag 5 oktober 2020 @ 09:10:
[...]

Het is één database per AG binnen Standard.

Goede aanvulling, thx.