none
SQL Server Agent is getting stopped after latest update RRS feed

  • Question

  • Dear Team,

    After  latest  patch update on Windows server SQL server agent got stopped.It gives below error logs .

    2019-12-03 10:24:59 - ? [100] Microsoft SQLServerAgent version 11.0.5058.0 (X64 unicode retail build) : Process ID 8284
    2019-12-03 10:24:59 - ? [495] The SQL Server Agent startup service account is NT SERVICE\SQLAgent$SP2013.
    2019-12-03 10:24:59 - ! [150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
    2019-12-03 10:25:29 - ! [150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
    2019-12-03 10:25:59 - ! [150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
    2019-12-03 10:26:29 - ! [150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
    2019-12-03 10:26:59 - ! [150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
    2019-12-03 10:26:59 - ! [000] Unable to connect to server 'SHAREPOINTDB\SP2013'; SQLServerAgent cannot start
    2019-12-03 10:26:59 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002] 
    2019-12-03 10:26:59 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002] 
    2019-12-03 10:26:59 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002] 
    2019-12-03 10:26:59 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002] 
    2019-12-03 10:26:59 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002] 
    2019-12-03 10:26:59 - ! [382] Logon to server 'SHAREPOINTDB\SP2013' failed (DisableAgentXPs)
    2019-12-03 10:26:59 - ? [098] SQLServerAgent terminated (normally)

    Kindly suggest how to overcome this problem. If it not get resolved we will revert the patches on Production.

    Regards,

    Shushant

    Tuesday, December 3, 2019 5:33 AM

All replies

  • Can you please try below options ,it may helps you.

    >> Changed the SQL SEVER agent user to a new service account and start the services.

    >>look at the permissions to the directory where the SQLAgent.exe is stored.

    >>add virtual server's name as value in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\SQLServerAgent\ServerHost.


    Please click "Mark as Answer" if it solved your issue and/or "Vote as helpful" if it helped. This can be beneficial to other community members reading this thread.

    Tuesday, December 3, 2019 12:45 PM
  • We have tried all mentioned approach, when trying to start the service, but still getting the same series of errors.

    Message

    [150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.

    Tuesday, December 3, 2019 1:49 PM
  • Can you access SQL Server by other means?

    Are there any messages in the SQL Server error log that can be correlated to the attempts to start Agent?


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Tuesday, December 3, 2019 10:33 PM
  • Hi, 

    There is a similar posting . Please check .

    After Upgrade to 2016, SQL Server Agent can't connect to Instance

    Best Regards,

    Rachel 


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, December 4, 2019 7:35 AM
  • Hi Rachel,

    We have not upgraded SQL server its only a windows security update.

    You can refer the errors log collected  from the system.

    Event Viewer  1:

    Event Viewer 2:

    SQL server Agent Error Log:

    Date,Source,Severity,Message
    12/05/2019 09:52:26,,Information,[098] SQLServerAgent terminated (normally)
    12/05/2019 09:52:26,,Error,[382] Logon to server 'SHAREPOINTDB\SP2013' failed (DisableAgentXPs)
    12/05/2019 09:52:26,,Error,[165] ODBC Error: 0<c/> Data source name not found and no default driver specified [SQLSTATE IM002]
    12/05/2019 09:52:26,,Error,[165] ODBC Error: 0<c/> Data source name not found and no default driver specified [SQLSTATE IM002]
    12/05/2019 09:52:26,,Error,[165] ODBC Error: 0<c/> Data source name not found and no default driver specified [SQLSTATE IM002]
    12/05/2019 09:52:26,,Error,[165] ODBC Error: 0<c/> Data source name not found and no default driver specified [SQLSTATE IM002]
    12/05/2019 09:52:26,,Error,[165] ODBC Error: 0<c/> Data source name not found and no default driver specified [SQLSTATE IM002]
    12/05/2019 09:52:26,,Error,[000] Unable to connect to server 'SHAREPOINTDB\SP2013'; SQLServerAgent cannot start
    12/05/2019 09:52:26,,Error,[150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
    12/05/2019 09:51:56,,Error,[150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
    12/05/2019 09:51:26,,Error,[150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
    12/05/2019 09:50:56,,Error,[150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
    12/05/2019 09:50:26,,Error,[150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
    12/05/2019 09:50:26,,Information,[495] The SQL Server Agent startup service account is Domain\dbadmin.
    12/05/2019 09:50:26,,Information,[100] Microsoft SQLServerAgent version 11.0.5058.0 (X64 unicode retail build) : Process ID 11568

    Apart from that we have observed in ODBC 64 bit drivers are missing. Ideally sql server drivers are present in ODBC

    For your information I have  attached all the observation. Let me know if you have any solution.

    Regards,

    Shushant  


    Thursday, December 5, 2019 4:54 AM
  • Hi , 

    Please check following articles .

    [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

    Unable to start SQL Server Agent

    Can't start sql server Agent

    Also , it might be related to Windows Update . Please check . 

    Best Regards,

    Rachel 


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, December 5, 2019 7:26 AM