May 18, 2017 at 12:44 pm
There has been an intermittent issue with SQL Services not auto restarting after windows patches and rebooting.
I am considering changing all of the SQL Services to ‘Automatic (Delayed Start)’.
Has anyone done this, and if so how did that work out for you?
I see there are many references to a Vaidhy Mohan who said do not do this but that seems to be the only reference I can find of anyone trying it.
Normally I will not have this happen on the same machine for a year.
But it has happened on the same machine for two months in a row.
This is one error I get:
“The description for Event ID 0 from source SQLISService130 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.”
Source: SQLISService130
The other error:
“None”
Source: MSSQLSERVER
All of the services start when I try them manually.
SQL Server 2016 SP1 on a VM, Windows 2012 R2
Thanks,
Amy
May 18, 2017 at 1:23 pm
Yes - haven't had any problems with that. Read the comments in the post since neither of the respondents agreed. He had problems with Windows starting up, it wasn't an issue with the services on automatic delayed startup. The boot process hadn't even gotten that far.
You can find a lot of people using automatic or automatic delayed. Usually I've seen people go to automatic delayed due to having timeout issues when the services tried to start.
If your services are on automatic, I'd still look through things more to find out why they didn't start automatically. Event logs, SQL error log, Agent log.
Sue
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply