We recently performed an installation of a SQL Server 2016 Failover Cluster Instance using the command line syntax similar to the one below:
setup.exe /Q /IACCEPTSQLSERVERLICENSETERMS /ACTION=installfailovercluster /INSTANCENAME=SUNGRD /INDICATEPROGRESS /UPDATESOURCE=C:\Installers /FEATURES=SQL,IS,RS,AS /SQLSVCACCOUNT="OMATECH\sqlserverkampala" /SQLSVCPASSWORD="********" /SQLSYSADMINACCOUNTS="OMATECH\MSSQLDBAdmins" /AGTSVCACCOUNT="OMATECH\sqlagentkampala" /AGTSVCPASSWORD="********" /FAILOVERCLUSTERNETWORKNAME="SVR-AVAYA-SQL" /FAILOVERCLUSTERDISKS="INST5_SysDB_Data_01" "Inst5_SysDB_Log" "INST5_AVAYA_Data_01" "INST5_AVAYA_Log" /FAILOVERCLUSTERIPADDRESSES="IPv4;188.8.131.52;Public;255.255.255.0" /FAILOVERCLUSTERGROUP="SQL Server (AVAYA)" /SQLBACKUPDIR=L:\INST5_AVAYA_LOG\BACKUP /RSSVCACCOUNT="OMATECH\sqlserverssrs" /RSSVCPASSWORD="********" /INSTALLSQLDATADIR=K:\INST5_SYSDB_DATA_01\DATA /SQLUSERDBDIR=K:\INST5_AVAYA_DATA_01\DATA /SQLUSERDBLOGDIR=L:\INST5_AVAYA_LOG\LOG /SQLTEMPDBDIR=K:\INST5_SYSDB_DATA_01\TEMP /SQLTEMPDBLOGDIR=L:\INST5_SYSDB_LOG\LOG /ASSVCACCOUNT="OMATECH\sqlserverssas" /ASSVCPASSWORD="********" /ASSYSADMINACCOUNTS="OMATECH\MSSQLDBAdmins" /ASCONFIGDIR=K:\INST5_SYSDB_DATA_01\SSAS /INDICATEPROGRESS /ASDATADIR=K:\INST5_AVAYA_DATA_01\DATA /ASLOGDIR=L:\INST5_AVAYA_LOG\LOG /ASTEMPDIR=K:\INST5_SYSDB_DATA_01\TEMP /ASBACKUPDIR=L:\INST5_AVAYA_LOG\BACKUP /ISSVCACCOUNT="OMATECH\sqlssisbigdata" /ISSVCPASSWORD="********"
This was not the first installation of this nature and in this manner we have done but in this case, we found that quite close to the end of the installation we noticed the Analysis Services component did not start on the and the installation failed effectively.
Note that Database Engine services had been installed and was up and running both on SQL Server Configuration Manager and on the Failover Cluster Manager. The error we got on the front end was this:
Unable to read parameters from registry for Service '(null)'. Error: 13, property in error is 'ServiceName'.
As part of troubleshooting we removed the /Q parameter and ran the command again. This gave the opportunity to view the GUI in detail for the error. We still got the error at the end of the installation and had to dig into the Windows Event Log where we found the error below after filtering for errors with MSOLAP$<Instance_Name> as Source:
The service cannot be started: File system error: The following error occurred during a file operation: Access is denied. . (\\?\K:\INST5_AVAYA_DATA_01\DATA\CryptKey.bin).
We were able to solve this by granting full control of the parent folder for this file Cryptkey.bin to the account NT SERVICE\MSOLAP$<Instance_Name>. As at now we do not knw whey the permissions were not automatically granted but once we retried the started on the installer (an option we had because we resorted to GUI), the installation completed successfully.