Return
-
Title
Change Auditor coordinator not starting up after server reboot -
Description
when the coordinator servers reboot for their monthly patching, the coordinator service does not start up after the reboot and I have to go and start it manually. -
Cause
SQL server was being patched at the same time and when the coordinator attempt to connect with the database it failed.
2022-07-19 01:24:07.139 [12][INFO][Quest.Data.ExceptionSql.OnExceptionSqlEvent(0)] SQL error(1225): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - The remote computer refused the network connection.); command: sp_getapplock2022-07-19 01:24:07.139 [12][WARN][ChangeAuditor.Coordinator.SqlReconnectTask.ExceptionSql_ExceptionSqlEvent(0)] Attempting to reconnect to the database (1).2022-07-19 01:24:07.139 [12][ERROR][ChangeAuditor.Coordinator.Service.Initialize(0)] Database initialization not successful on ChangeAuditor. The ConnectionString property has not been initialized.2022-07-19 01:24:07.139 [12][INFO][ChangeAuditor.Service.Service.OnStop(0)] **** Service Stop2022-07-19 01:24:07.155 [12][INFO][Quest.ChangeAuditor.WebServices.EventWebhookService.OnServiceStopping(0)] Service stopping2022-07-19 01:24:07.155 [12][INFO][ChangeAuditor.Service.Service.CurrentDomainUnhandledException(0)] Unhandled exception caught in Service2022-07-19 01:24:07.155 [12][ERROR][ChangeAuditor.Service.Service.CurrentDomainUnhandledException(0)] Object reference not set to an instance of an object. -
Resolution
Change the patching times to make sure SQL server is available after coordinator server restarts.