You may receive an "Error 22022: SQLServerAgent is not currently running so it cannot be notified of this action" error message when you run a SQL Server Agent job in SQL Server 2000 (911841)


The information in this article applies to:

  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
Bug #: 474786 (SQL Server 8.0)

Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

SYMPTOMS

When you run a SQL Server Agent job in Microsoft SQL Server 2000, you may receive the following error message:
Error 22022: SQLServerAgent is not currently running so it cannot be notified of this action."

CAUSE

If you receive this error message, first make sure that the SQL Server Agent service is running. To do this, look in the SQL Server 2005 Services list in SQL Server Configuration Manager. Make sure that the value of the state column of the SQL Server Agent service is Running. If the SQL Server Agent service is running, this problem occurs because the SQL Server Agent service cannot interpret the dot mark (.) that represents the local computer in the ObjectName registry entry under the following registry subkey. For a default instance, the registry subkey is as follows:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLSERVER\

For a named instance, the registry subkey is as follows:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQL$InstanceName\

Note InstanceName is a placeholder for the instance of SQL Server.

RESOLUTION

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To resolve this problem, modify the registry entry that is mentioned in the "Cause" section by replacing the dot mark with the computer name.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type:MajorLast Reviewed:2/15/2006
Keywords:kbExpertiseAdvanced kbsql2005engine kbprb KB911841 kbAudDeveloper kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.