hey all! I've got an issue with SQL instance I setup for an on-prem CVAD deployment. The SQL Server 2022 latest version and patched running on Server 2022. Each month, the server receives windows updates, on reboot, the MSSQLService fails to start, i've got it running in a service account (GMSA) is not used, it's just a regular account. Event ID 7000. The fix is odd, 1 - we just take the existing password from our password manager 2- Open active directory users and computers 3 - Reset password > paste in the existing password 4 - Start the service on the SQL Server 5 - Issue is resolved We want to add additional automation to our monthly windows updates, but this is blocking us. I've been deploying MS SQL server for Citrix/WEM/PVS/VEEAM/etc for years, never had this Any idea what might be causing it?

is the user allowed to "run as service" ?

Yep! 👍

May I ask why service account is used and not just using the SQL standard local accounts built-in during installation? We did see that occur occasionally when we used svc accounts but when switched to the machine accounts, we have not seen the issue

Just habit ! I’ve always done it this way , but , I’d be amiable to changing it

I have found the machine accounts are very stable and take less maintenance with password changes. MS performs all their testing for upgrades/patches with the machine accounts these days. Also, MS touts it is a more secure implementation

Thank you! I’ll look into making the change next week

Is the SQL service trying to start before the server has established communication with the domain? You could try making it Automatic (delayed start) or dependent on netlogon.

hey Scott! It's set to the default of 'auto - delayed'. I'll be amending it to use the MSQLService to use the local machine account as the next step