In Part 1 of SharePoint 2016 installation in Azure, we started with installing SQL Server 2014. In this part we can see the common SQL Server mistakes while installing SharePoint 2016
In SharePoint 2016, there is no ‘standalone’ option during installation which installs SQL Express – SQL must be installed and running prior to installation.
SQL server didn’t complete successfully as the services wasn’t starting up automatically. Part 1 of this series can be found here
SQL Setup failed due to below error
(01) 2016-08-23 09:36:14 Slp: The configuration failure category of current exception is ConfigurationFailure
(01) 2016-08-23 09:36:14 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
(01) 2016-08-23 09:36:14 Slp: Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
(01) 2016-08-23 09:36:14 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart(Process processSql, Boolean withFailpoint)
(01) 2016-08-23 09:36:14 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceSCM.StartSqlServer(String[] parameters, Boolean withFailpoint)
(01) 2016-08-23 09:36:14 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerStartup.StartSQLServerForInstall(String sqlCollation, String masterFullPath, Boolean isConfiguringTemplateDBs, Boolean isSlipstreamRunning)
(01) 2016-08-23 09:36:14 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.ConfigSQLServerSystemDatabases(EffectiveProperties properties, Boolean isConfiguringTemplateDBs, Boolean useInstallInputs)
(01) 2016-08-23 09:36:14 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.DoCommonDBStartConfig(ConfigActionTiming timing)
(01) 2016-08-23 09:36:14 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2016-08-23 09:36:14 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2016-08-23 09:36:14 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2016-08-23 09:36:14 Slp: Inner exceptions are being indented
(01) 2016-08-23 09:36:14 Slp:
(01) 2016-08-23 09:36:14 Slp: Exception type: Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException
(01) 2016-08-23 09:36:14 Slp: Message:
(01) 2016-08-23 09:36:14 Slp: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
(01) 2016-08-23 09:36:14 Slp: HResult : 0x851a001a
· Checked ERRORLOG and found that Setup was unable to start SQL Services
· Tried below and SQL was able to start.
sqlservr.exe -mSqlSetup -Q -qSQL_Latin1_General_CP1_CI_AS -T4022 -T4010 -T3659 -T3610 -T8015 -T902
· Tried Net Start
net start mssqlserver /mSqlSetup /Q /qSQL_Latin1_General_CP1_CI_AS /T4022 /T4010 /T3659 /T3610 /T8015 /T902
· Above failed with Certificate error.
· This was because of the fact that Service SID don’t work on domain controller
· So, I changed service account to “LocalSystem”
· After that I was able to start SQL Services
· Agent was not starting. Below was the error in SQLAgent.out file.
2016-08-23 10:00:28 – ? [100] Microsoft SQLServerAgent version 12.0.5000.0 (X64 unicode retail build) : Process ID 5052
2016-08-23 10:00:28 – ? [495] The SQL Server Agent startup service account is DCC\SHAREPOINT2016$.
2016-08-23 10:00:28 – ! [150] SQL Server does not accept the connection (error: 18456). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
2016-08-23 10:00:28 – ! [000] Unable to connect to server ‘(local)’; SQLServerAgent cannot start
2016-08-23 10:00:28 – ! [298] SQLServer Error: 18456, Login failed for user ‘DCC\SHAREPOINT2016$’. [SQLSTATE 28000]
2016-08-23 10:00:28 – ! [382] Logon to server ‘(local)’ failed (DisableAgentXPs)
2016-08-23 10:00:28 – ? [098] SQLServerAgent terminated (normally)
· To fix this, I need to add that account as SQL Login
· I was not able to do so because dcc\dcc was not there in SQL Logins
· Started SQL with /mSQLCMD parameter
· Ran below command
USE [master]
GO
CREATE LOGIN [dccdcc] FROM WINDOWS WITH DEFAULT_DATABASE=[master]
GO
EXEC master..sp_addsrvrolemember @loginame = N'dccdcc', @rolename = N'sysadmin'
GO· Stopped SQL and logged in via SSMS.
· Added ‘DCC\SHAREPOINT2016$ account as Sysadmin
· Now I was able to start SQL Agent
· Performed Repair of SQL
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068578302
Start time: 2016-08-23 10:06:13
End time: 2016-08-23 10:08:53
Requested action: Repair
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.
Next step for FullText: Use the following information to resolve the error, and then try the setup process again.
Next step for Replication: Use the following information to resolve the error, and then try the setup process again.
…
…
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, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84B40002
Error description: The SQL Server feature ‘SQL_Engine_Core_Inst’ is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft SQL Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.5000.0&EvtType=0x2841E06E@1204@2&EvtType=0x2841E06E@1204@2
· Modified registry
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL12.MSSQLSERVER\ConfigurationState
· Changed values from 2 (failed) to 1 (success)
· Repair again and it worked
· SQL is installed successfully.
Leave a comment