August 13, 2018 at 4:56 am
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?
Window Application Event Log:Error Message No 1:
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 tableError 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]
Thanks in advance.
August 13, 2018 at 8:22 am
krishnp92 - Monday, August 13, 2018 4:56 AMI'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?Window Application Event Log:
Error Message No 1:
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 tableError 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]Thanks in advance.
Any changes with the service account for SQL Server Agent recently? Or changes to the service account without using SQL Server Configuration Manager?
It looks like it could be permissions for the Agent account. If you arent sure if there were changes, you can always retype of account and password, apply in SQL Server Configuration Manager for the service account.
Sue
August 13, 2018 at 8:28 am
Sue_H - Monday, August 13, 2018 8:22 AMkrishnp92 - Monday, August 13, 2018 4:56 AMI'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?Window Application Event Log:
Error Message No 1:
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 tableError 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]Thanks in advance.
Any changes with the service account for SQL Server Agent recently? Or changes to the service account without using SQL Server Configuration Manager?
It looks like it could be permissions for the Agent account. If you arent sure if there were changes, you can always retype of account and password, apply in SQL Server Configuration Manager for the service account.Sue
Hi Sue,
Thanks for your reply, I think the permissions issue is more to do with restarting the Agent service. I have now altered our monitoring software so it alerts us and restarts in the event that the service goes down. But to answer your question, there have been no changes to the permissions for the account running the agent service.
August 13, 2018 at 9:32 am
Comms link failure / semaphore timeout - is the server starved of resources at that point? What jobs are running at the point of failure? Anything really heavy duty?
Is it a virtual server? If so, what else is running on that host that might deprive your SQL Server of the memory / CPU it needs?
Is it a dedicated SQL Server, or are there other things on it?
Have you got any SQL Server monitoring software on that server? If so, what are the waits at / around the time of failure?
Thomas Rushton
blog: https://thelonedba.wordpress.com
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply