Our sql server cluster contains a primary and secondary replica on two separate servers. (Operating system is Windows Server 2012 R2 Standard.)Normally, the MSSQLSERVER service starts automatically after either of the servers are restarted; however, both servers restart simultaneously, often the MSSQLSERVER service on the machine hosting the primary replica fails to start (I’m seeing 7009 /7000/7001 messages in the system logs. 7009: A timeout was reached (3000 milliseconds) while waiting for the SqlServer (MSSQLSERVER) service to connect). Is there a way to ensure that the service control manager retries to start the service when this happens, or should I set the timeout to something higher? I did actually look in the registry for the ServicesPipeTimeout entry in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control subkey, but didn't see it.
↧