Error 22022: SQLServerAgent Is Not Currently Running, or Does Not Exist

Fix it now

Something asked SQL Server Agent to act and Agent was not there to act. Two very different situations produce the same message: the service is installed and stopped, which is a five-minute fix, or the instance is Express, where Microsoft’s editions tables list SQL Server Agent as not supported at all. Establish which before rebuilding anything.

SELECT SERVERPROPERTY('Edition') AS Edition, SERVERPROPERTY('ProductVersion') AS Version;
EXEC sp_configure 'show advanced options', 1;
RECONFIGURE;
EXEC sp_configure 'Agent XPs';

1. Read the edition. If it returns an Express edition, Agent is not part of it and no configuration produces one. Stop here and read the licensing section.
2. On any other edition, open SQL Server Configuration Manager. The Agent service is named for the instance and should be Running with a start mode of Automatic.
3. If it is stopped, start it there. If it refuses, or starts and stops within seconds, the Agent error log and the Windows Application log say why.
4. Agent XPs enables itself when Agent starts, so a run value of 0 while the service claims to be running points at a start-up problem rather than a configuration one.

Agent XPs is an advanced option, so show advanced options has to be 1 first or sp_configure returns error 15123 and you will think you have found something.

If the job or maintenance plan runs, you are done. If the edition check returned Express, the next section explains what that means and what it does not.

Why it happens

This message comes from msdb rather than from the engine. Starting a job, running a maintenance plan, and every scheduled part of replication and log shipping goes through Agent, and each of those asks msdb to talk to the service. If the service is not running, the caller gets the refusal back. Nothing ran, nothing failed, and nothing is corrupt.

One thing worth knowing before you go looking it up: the number is not in Microsoft’s published error catalogue with this meaning. Message 22022 in sys.messages is an unrelated internal message whose text differs between releases. The “SQLServerAgent is not currently running” text you are looking at is produced by the Agent extended stored procedures rather than by a catalogued message, which is why searching Microsoft’s error tables for 22022 returns something that has nothing to do with Agent. Diagnose it by what it is telling you, not by the number.

Error 14258 is the polite relative and it is catalogued: cannot perform this operation while SQL Server Agent is starting, try again later. It clears within seconds, and seeing it repeatedly means Agent is failing in a loop rather than merely being slow.

The edition fact matters more than any of the troubleshooting. Microsoft’s editions tables for SQL Server 2022 and SQL Server 2025 both list SQL Server Agent as not supported on Express. There is no separate download and no optional component in setup that adds one. Scheduled jobs, maintenance plans, operators, alerts and the multi-step job model belong to the paid editions, and so does the scheduling that log shipping and replication depend on.

Full reference

Which situation you are in

What Express gives you instead, and what it costs

Task Scheduler with sqlcmd genuinely works for single-step work such as a nightly backup script, and it costs nothing. What it cannot do is anything that has to be scheduled by SQL Server itself, which is why log shipping and replication are not on the table at all on Express rather than being merely inconvenient.

Where to look

The msdb roles, and what each is for

• SQLAgentUserRole: the most restricted. Members work with jobs they own.
• SQLAgentReaderRole: adds visibility of jobs owned by others.
• SQLAgentOperatorRole: the broadest of the three, for people who need to act on jobs generally.
• Members of any of the three can only use proxies they have been granted specific access to, so a step that needs another credential needs that grant as well as the role.
• Members of sysadmin have access regardless, which is exactly why testing as yourself proves nothing.

Scheduling work on Express without Agent

Where the edition is Express and buying is not on the table today, the practical substitute is the operating system’s own scheduler driving sqlcmd against a script file. It is not Agent and it does not pretend to be, but for a nightly backup or an index maintenance script it does the job and costs nothing. Keep the T-SQL in a file under source control rather than inline in the task, so the thing being scheduled is reviewable.

sqlcmd -S .\SQLEXPRESS -E -b -i "C:\Scripts\nightly-backup.sql" -o "C:\Logs\nightly-backup.log"

• Use -b so a failing batch returns a non-zero exit code, otherwise the task reports success whatever happened.
• Redirect output to a file with -o and keep the files, because you have no job history to fall back on.
• Run the task under an account that has the rights the script needs on the instance, not under whichever account happened to create it.
• Have the task itself alert on failure. Nothing in SQL Server will do it for you on Express, because operators and alerts are part of Agent.

Event IDs, honestly

Event IDs 103 and 208 are widely quoted for the SQLSERVERAGENT event source in the Windows Application log – 103 for a service that could not start, 208 for a scheduled job that failed. No current Microsoft documentation publishes those event IDs, so treat them as a landmark rather than a specification: filter the Application log by the SQLSERVERAGENT source and read the message bodies, which carry the reason, rather than matching on a number nobody documents.

Every code this article covers

Confirm the fix worked

1. The Agent service shows Running in SQL Server Configuration Manager with a start mode of Automatic.
2. EXEC sp_configure 'Agent XPs'; returns a run value of 1, with show advanced options set first.
3. A test job runs to completion and its history appears in job history.
4. The user who reported the problem can start their own job, not just you.
5. Reboot the machine and confirm Agent starts on its own without intervention.

Questions people ask about this