Return
-
Title
Are there any errors in the logs would indicate the Coordinator has lost its connection to the database? -
Description
Can the Coordinator log be used to determine if the Coordinator no longer has a connection to the database? -
Resolution
The Coordinator logs will show warnings and errors similar to the following when the Coordinator looses connection to the SQL server:- A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
- Attempting to reconnect to the database (1)
- SQL error(-2146232060): 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
- Database inactive
The CA Client, if open, may also crash with the exception:- Database inactive
Once the Coordinator re-establishes the connection to the SQL server you will see the following logged:- Retrying SQL connection
- Opening ChangeAuditor database: Data Source=<SQLServerName>;Initial Catalog=changeauditor;Integrated Security=True;User ID=<AccountName>;Connect Timeout=30;Encrypt=False;Application Name="ChangeAuditor Coordinator on <ServerName>"
- SQL connection re-established successfully