Skip to content

Commit c8376e9

Browse files
haywoodsloanhaywoodsloan
committed
PR feedback
1 parent e7be0e2 commit c8376e9

1 file changed

Lines changed: 66 additions & 53 deletions

File tree

‎support/sql/database-engine/startup-shutdown/sql-server-agent-crashes-upon-start.md‎

Lines changed: 66 additions & 53 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
---
22
title: SQL Server agent crashes when you try to start it
3-
description: This article discusses the issues experienced by SQL Server agent service when you create multiple jobs in your SQL Server instance.
3+
description: Learn how to resolve SQL Server Agent crashes when starting, including troubleshooting multiple job entries and missing ODBC drivers.
44
ms.date: 12/03/2025
55
ms.reviewer: ramakoni1, v-jayaramanp, v-shaywood
66
ms.custom: sap:Startup, shutdown, restart issues (instance or database)
77
---
88

99
# SQL Server agent crashes when you try to start it
1010

11-
This article discusses the issues experienced by SQL Server agent service when you create multiple jobs in your SQL Server instance.
11+
This article provides troubleshooting guidance for an issue where the SQL Server agent service crashes or takes longer than expected when you try to start it.
1212

1313
_Original product version:_   SQL Server \
1414
_Original KB number:_   2795690
@@ -18,60 +18,61 @@ _Original KB number:_   2795690
1818
A SQL Server agent crashes when you try to start it or takes longer than expected to start. Additionally, you might experience one or more of the following scenarios:
1919

2020
- **Scenario 1**: The following error message is logged in the System event log:
21-
> The service didn't respond to the start or control request in a timely fashion.
21+
> The SQL Server Agent (MSSQLSERVER) service failed to start due to the following error:
22+
> The service didn't respond to the start or control request in a timely fashion.
2223
- **Scenario 2**: The status of the agent displays as "Starting" in the Control Panel, and the following error message is logged in the *SQLAgent.log* file:
23-
> An idle CPU condition has not been defined - OnIdle job schedules will have no effect.
24-
25-
Additionally, the following entries might be logged in the *SQLAgent.log* file:
26-
27-
```output
28-
<Time Stamp> - ? [431] Populating subsystems cache... \
29-
<Time Stamp> - ? [432] There are 7 subsystems in the subsystems cache \
30-
<Time Stamp> - ? [124] Subsystem 'ActiveScripting' successfully loaded (maximum concurrency: 40)\
31-
<Time Stamp> - ? [124] Subsystem 'ANALYSISCOMMAND' successfully loaded (maximum concurrency: 400)\
32-
<Time Stamp> - ? [124] Subsystem 'ANALYSISQUERY' successfully loaded (maximum concurrency: 400)\
33-
<Time Stamp> - ? [124] Subsystem 'CmdExec' successfully loaded (maximum concurrency: 40)\
34-
<Time Stamp> - ? [124] Subsystem 'PowerShell' successfully loaded (maximum concurrency: 2)\
35-
<Time Stamp> - ? [124] Subsystem 'SSIS' successfully loaded (maximum concurrency: 400)\
36-
<Time Stamp> - ? [124] Subsystem 'TSQL' successfully loaded (maximum concurrency: 80)\
37-
<Time Stamp> - ! [364] The Messenger service has not been started - NetSend notifications will not be sent\
38-
<Time Stamp> - ? [129] SQLSERVERAGENT starting under Windows NT service control\
39-
<Time Stamp> - + [396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect\
40-
<Time Stamp> - ? [110] Starting SQLServerAgent Monitor using '' as the notification recipient...\
41-
<Time Stamp> - ? [146] Request servicer engine started\
42-
<Time Stamp> - ? [133] Support engine started\
43-
<Time Stamp> - ? [167] Populating job cache...\
44-
<Time Stamp> - ? [131] SQLSERVERAGENT service stopping due to a stop request from a user, process, or the OS...\
45-
<Time Stamp> - ? [134] Support engine stopped\
46-
<Time Stamp> - ? [197] Alert engine stopped\
47-
<Time Stamp> - ? [168] There are 4731 job(s) [0 disabled] in the job cache\
48-
<Time Stamp> - ? [170] Populating alert cache...\
49-
<Time Stamp> - ? [171] There are 0 alert(s) in the alert cache\
50-
<Time Stamp> - ? [149] Request servicer engine stopped\
51-
<Time Stamp> - ? [248] Saving NextRunDate/Times for all updated job schedules...\
52-
<Time Stamp> - ? [249] 0 job schedule(s) saved\
53-
<Time Stamp> - ? [127] Waiting for subsystems to finish...\
54-
<Time Stamp> - ? [128] Subsystem 'ActiveScripting' stopped (exit code 1)\
55-
<Time Stamp> - ? [128] Subsystem 'ANALYSISCOMMAND' stopped (exit code 1)\
56-
<Time Stamp> - ? [128] Subsystem 'ANALYSISQUERY' stopped (exit code 1)\
57-
<Time Stamp> - ? [128] Subsystem 'CmdExec' stopped (exit code 1)\
58-
<Time Stamp> - ? [128] Subsystem 'PowerShell' stopped (exit code 1)\
59-
<Time Stamp> - ? [128] Subsystem 'SSIS' stopped (exit code 1)\
60-
<Time Stamp> - ? [175] Job scheduler engine stopped\
61-
```
62-
63-
- **Scenario 3**: The database engine server displays a SQL Server process ID (SPID) from the "SQLAgent - Generic Refresher" service. Additionally, the following job is displayed as running in the input buffer of the SPID:
64-
65-
```sql
66-
EXECUTE msdb.dbo.sp_sqlagent_refresh_job
67-
```
68-
69-
> [!NOTE]
70-
> The SPID is in the RUNNABLE state and regularly waits for the `PREEMPTIVE_OS_LOOKUPACCOUNTSID` wait type, or the SPID is in a waiting state for the `ASYNC_NETWORK_IO` wait type.
24+
> An idle CPU condition has not been defined - OnIdle job schedules will have no effect.
25+
26+
Additionally, the following entries might be logged in the *SQLAgent.log* file:
27+
28+
```output
29+
<Time Stamp> - ? [431] Populating subsystems cache... \
30+
<Time Stamp> - ? [432] There are 7 subsystems in the subsystems cache \
31+
<Time Stamp> - ? [124] Subsystem 'ActiveScripting' successfully loaded (maximum concurrency: 40)\
32+
<Time Stamp> - ? [124] Subsystem 'ANALYSISCOMMAND' successfully loaded (maximum concurrency: 400)\
33+
<Time Stamp> - ? [124] Subsystem 'ANALYSISQUERY' successfully loaded (maximum concurrency: 400)\
34+
<Time Stamp> - ? [124] Subsystem 'CmdExec' successfully loaded (maximum concurrency: 40)\
35+
<Time Stamp> - ? [124] Subsystem 'PowerShell' successfully loaded (maximum concurrency: 2)\
36+
<Time Stamp> - ? [124] Subsystem 'SSIS' successfully loaded (maximum concurrency: 400)\
37+
<Time Stamp> - ? [124] Subsystem 'TSQL' successfully loaded (maximum concurrency: 80)\
38+
<Time Stamp> - ! [364] The Messenger service has not been started - NetSend notifications will not be sent\
39+
<Time Stamp> - ? [129] SQLSERVERAGENT starting under Windows NT service control\
40+
<Time Stamp> - + [396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect\
41+
<Time Stamp> - ? [110] Starting SQLServerAgent Monitor using '' as the notification recipient...\
42+
<Time Stamp> - ? [146] Request servicer engine started\
43+
<Time Stamp> - ? [133] Support engine started\
44+
<Time Stamp> - ? [167] Populating job cache...\
45+
<Time Stamp> - ? [131] SQLSERVERAGENT service stopping due to a stop request from a user, process, or the OS...\
46+
<Time Stamp> - ? [134] Support engine stopped\
47+
<Time Stamp> - ? [197] Alert engine stopped\
48+
<Time Stamp> - ? [168] There are 4731 job(s) [0 disabled] in the job cache\
49+
<Time Stamp> - ? [170] Populating alert cache...\
50+
<Time Stamp> - ? [171] There are 0 alert(s) in the alert cache\
51+
<Time Stamp> - ? [149] Request servicer engine stopped\
52+
<Time Stamp> - ? [248] Saving NextRunDate/Times for all updated job schedules...\
53+
<Time Stamp> - ? [249] 0 job schedule(s) saved\
54+
<Time Stamp> - ? [127] Waiting for subsystems to finish...\
55+
<Time Stamp> - ? [128] Subsystem 'ActiveScripting' stopped (exit code 1)\
56+
<Time Stamp> - ? [128] Subsystem 'ANALYSISCOMMAND' stopped (exit code 1)\
57+
<Time Stamp> - ? [128] Subsystem 'ANALYSISQUERY' stopped (exit code 1)\
58+
<Time Stamp> - ? [128] Subsystem 'CmdExec' stopped (exit code 1)\
59+
<Time Stamp> - ? [128] Subsystem 'PowerShell' stopped (exit code 1)\
60+
<Time Stamp> - ? [128] Subsystem 'SSIS' stopped (exit code 1)\
61+
<Time Stamp> - ? [175] Job scheduler engine stopped\
62+
```
63+
64+
- **Scenario 3**: The database engine server displays a SQL Server process ID (SPID) from the "SQLAgent - Generic Refresher" service. Additionally, the following job is displayed as running in the input buffer of the SPID:
65+
66+
```sql
67+
EXECUTE msdb.dbo.sp_sqlagent_refresh_job
68+
```
69+
70+
> [!NOTE]
71+
> The SPID is in the RUNNABLE state and regularly waits for the `PREEMPTIVE_OS_LOOKUPACCOUNTSID` wait type, or the SPID is in a waiting state for the `ASYNC_NETWORK_IO` wait type.
7172
7273
## Cause 1: Multiple job entries
7374

74-
This issue occurs because there are multiple job entries in SQL Server.
75+
This issue can occur when there are multiple job entries in SQL Server.
7576

7677
> [!NOTE]
7778
> The issue can also occur if you unintentionally set up multiple subscriptions for your reports in the Reporting Services Configuration Manager.
@@ -147,7 +148,19 @@ For info on the ODBC driver requirements for different versions of SQL Server, s
147148
msiexec /i <ODBD_Driver_MSI> /qn
148149
```
149150
150-
1. After the driver installation completes, restart the SQL Server Agent and confirm the _SQL SERVER AGENT_ service is running.
151+
1. After the driver installation completes, restart the SQL Server Agent.
152+
1. Confirm the _SQL SERVER AGENT_ service is running.
153+
1. For an unnamed SQL Server instance run the following PowerShell command:
154+
155+
```powershell
156+
Get-Service -Name SQLSERVERAGENT
157+
```
158+
159+
1. For a named SQL Server instance run the following PowerShell command:
160+
161+
```powershell
162+
Get-Service -Name SQLAgent$<InstanceName>
163+
```
151164
152165
## More information
153166

0 commit comments

Comments
 (0)