1

I've had back to back Saturdays where our SQLServerAgent (Test Instance) has stopped with an Event ID of 17052. The times do differ as the initial week was 21:00 and last Saturday was 19:00. Having checked the event log, I get the below messages. After checking the SQL Server Agent job history, there were no job failures logged. The Server hosts multiple instance and all other services on the instance were not affected. Please can someone suggest what would cause SQL Server Agent to stop based on the below?

Select @@version

Microsoft SQL Server 2014 (SP2-GDR) (KB4019093) - 12.0.5207.0 (X64) Jul 3 2017 02:25:44 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor)

Window Application Event Log:

Error Message No 1:
    The description for Event ID 17052 from source MSSQL$TEST cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event: 

    SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.

    the message resource is present but the message is not found in the string/message table

Error Message No 2:

    The description for Event ID 17052 from source MSSQL$TEST cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event: 

    SQLServerAgent Monitor failed to restart SQLServerAgent after SQLServerAgent terminated unexpectedly (reason: SQLSCMControl() returned error 5, 'Access is denied.').

    the message resource is present but the message is not found in the string/message table

SQL Server Error Log:

    Date        11/08/2018 19:00:19
    Log     SQL Server Agent (Archive #1 - 11/08/2018 19:00:00)

    Message
    [165] ODBC Error: 0, COUNT field incorrect or syntax error [SQLSTATE 07002] (ConnExecuteCachableOp)


    Date        11/08/2018 19:00:09
    Log     SQL Server Agent (Archive #1 - 11/08/2018 19:00:00)

    Message
    [298] SQLServer Error: 16389, Communication link failure [SQLSTATE 08S01]

    Date        11/08/2018 19:00:09
    Log     SQL Server Agent (Archive #1 - 11/08/2018 19:00:00)

    Message
    [298] SQLServer Error: 121, Communication link failure [SQLSTATE 08S01]


    Date        11/08/2018 19:00:09
    Log     SQL Server Agent (Archive #1 - 11/08/2018 19:00:00)

    Message
    [298] SQLServer Error: 121, TCP Provider: The semaphore timeout period has expired. [SQLSTATE 08S01]
  • Can you please also add the output of select @@version in the question. – Shanky Aug 13 '18 at 12:01
  • @Shanky Microsoft SQL Server 2014 (SP2-GDR) (KB4019093) - 12.0.5207.0 (X64) Jul 3 2017 02:25:44 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor) – Krishn Aug 13 '18 at 12:05
  • Is this standalone machine or cluster. Did you checked the service account of SQL server agent, that it has proper rights I can see the access denied message in the windows logs, is the account not locked ? – Shanky Aug 13 '18 at 12:10
  • It's a stand alone machine. I've logged onto the server itself using the service account which SQL Server Agent uses and restarted the SQL Server Agent Service and that restarted without any issues – Krishn Aug 13 '18 at 14:02
  • Seems like some AD policy issue to me. May be some rights are getting removed, triple check – Shanky Aug 13 '18 at 14:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.