2

I did an in place upgrade for host OS from Windows server 2012 R2 to windows server 2022. After this move, I noticed the SQL server 2017 enterprise edition instance therein does not start automatically across reboots; but picks up when manually started from services. Any possible cause for this? This is a box purely dedicated to the SQL server.

Improve this question
0

1 Answer 1

Reset to default
2

I was using a gMSA account for the SQL service. To resolve this, I went to the windows pane of the OS event logon and noticed an error from NETLOGON hinting that the domain controller was unavailable or could not be contacted and a subsequent error from the Service Control Manager tagged the SQL username or password could be unavailable. I went to the registry editor's HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLSERVER and on the key DependOnService I added W32Time and Netlogon as shown in the image below. sql depencies

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.