Shulou(Shulou.com)06/01 Report--

Environment:

2 SQL Server 2012 Always ON servic

Phenomenon:

Always ON service is normal, synchronization is normal, and application is normal.

Second Server Server Agent stops automatically after it starts for a few seconds.

Process:

1. View the Windows system log and display the following information:

2. View the current Error Log in SQL Studio

Date,Source,Severity,Message

09According 25Universe 2018 13ore54move07Regery Information, [098] SQLServerAgent terminated (normally)

09According 25Universe 2018 13ore54move07Magi error, Logon to server 'domain\ SQLInstance' failed (DisableAgentXPs)

09/25/2018 13:54:07,Error, [165] ODBC Error: 0 Data source name not found and no default driver specified [SQLSTATE IM002]

09/25/2018 13:54:07,Error, [165] ODBC Error: 0 Data source name not found and no default driver specified [SQLSTATE IM002]

09/25/2018 13:54:07,Error, [165] ODBC Error: 0 Data source name not found and no default driver specified [SQLSTATE IM002]

09/25/2018 13:54:07,Error, [165] ODBC Error: 0 Data source name not found and no default driver specified [SQLSTATE IM002]

09/25/2018 13:54:07,Error, [165] ODBC Error: 0 Data source name not found and no default driver specified [SQLSTATE IM002]

09According 25Universe 2018 13ore54move07Magi error, [000] Unable to connect to server 'domain\ SQLInstance'; SQLServerAgent cannot start

09According to 25Universe 2018 13 to 5407 SQL Server does not accept the connection error, [15] to (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.

09According to 25Universe 2018 1315 / 53 / 37 SQL Server does not accept the connection SQL Server does not accept the connection (2010: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.

09According 25Universe 2018 131553 SQL Server does not accept the connection 07Magneol error, [150] Universe (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.

09According 25Universe 2018 1315 52 SQL Server does not accept the connection 37 legendary error, [150] Universe (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.

09According 25Universe 2018 131452 SQL Server does not accept the connection 07legendary error (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.

09According 25Universe 2018 13 The SQL Server Agent startup service account is domain 5215 07 recorder Information, [495] dbadmin.

09x25 unicode retail build: Process ID 1008. 09According to 25Universe 2018 13purl 52purl 07Jronomy Information,

3. Combined with the above errors, it seems to point to ODBC, open ODBC, and find that Driver in ODBC 64bit is empty.

Normally, there should be SQL Server and SQL Native Client 11 drivers.

4. Find sqlncli.msi in the SQL Server 2012 installation package to reinstall SQL Native Client 11 (be careful to reinstall rather than repair).

5. Check in ODBC again. SQL Native Client 11 is already available.

6. Restart SQL Agent and observe that there is no automatic stop after a few minutes, and the problem is solved.

Later, I saw an article about the loss of ODBC drivers: http://www.cnblogs.com/chinalantian/archive/2016/06/13/5581644.html.

Knowing that some drivers in ODBC may be removed when uninstalling some software, consulting customers said that some software has been deleted recently.

It is hereby recorded!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.