Error 22022
Contents |
Refer to KB953748 or SQL server books online" Max
Sql Server Agent Does Not Start
size for the attachment size in msdb.dbo.sp_send_dbmail » Aug 31 ERROR: 22022 SQL Server Agent not running https://blogs.msdn.microsoft.com/repltalk/2010/05/30/sqlserveragent-is-not-currently-running-so-it-cannot-be-notified-of-this-action/ Categories: SQL Database by Deepak When you run a SQL Server Agent job in Microsoft SQL Server 2008, you may receive the following error message: ………………………………………………………………………………………………………………………………………………………………………………. Error 22022: SQLServerAgent is not currently running http://deepakdba.com/?p=255 so it cannot be notified of this action.” If you receive this error message, first make sure that the SQL Server Agent service is running. To do this, follow these steps: ………………………………………………………………………………………………………………………………………………………………………………. 1.Click Start, click Run, type Services.msc, and then click OK. 2.In the Services window, locate the SQL Server Agent service. 3.Make sure that the value of the Status column of the SQL Server Agent service is Running. then EXEC sp_configure ‘show advanced’, 1; RECONFIGURE; EXEC sp_configure ‘allow updates’, 0; RECONFIGURE; EXEC sp_configure ‘Agent XPs’, 1; RECONFIGURE; GO Incase still you are getting the same err
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 7,2000 » Administration » SQLServerAgent Error: 32. http://www.sqlservercentral.com/Forums/Topic639021-5-1.aspx [SQLSTATE 42000]... SQLServerAgent Error: 32. [SQLSTATE 42000] (Error 22022) Rate Topic Display Mode Topic http://dba.stackexchange.com/questions/29662/agent-job-will-not-run Options Author Message Ajay PrakashAjay Prakash Posted Sunday, January 18, 2009 1:59 PM Valued Member Group: General Forum Members Last Login: Friday, December 12, 2014 8:34 AM Points: 53, Visits: 237 Our maintenance job for recycling SQL Server Agent errorlog frequently fails with following error:-----------------------------------------------------------------------SQLServerAgent Error: 32. [SQLSTATE 42000] (Error 22022)-----------------------------------------------------------------------When ran manually ran sp_cycle_agent_errorlog : sql server below error gets reported.---------------------------------------Msg 22022, Level 16, State 1, Line 0SQLServerAgent Error: 32.--------------------------------------- Kindest Regards,Ajay Prakash Post #639021 MANU-J.MANU-J. Posted Tuesday, January 20, 2009 7:02 PM SSCommitted Group: General Forum Members Last Login: Thursday, May 22, 2014 7:04 AM Points: 1,688, Visits: 8,766 I think its typo it should be EXEC sp_cycle_errorlog. Also, is the account used to run the stored procedure is sysadmin or not? It should be a error 22022 sql member of sysadmin role.MJ Post #640331 Ajay PrakashAjay Prakash Posted Thursday, January 22, 2009 3:15 PM Valued Member Group: General Forum Members Last Login: Friday, December 12, 2014 8:34 AM Points: 53, Visits: 237 Yes the account name that runs is 'SA'. This is SQL Server 2005 with SP2. Kindest Regards,Ajay Prakash Post #642137 Ajay PrakashAjay Prakash Posted Sunday, February 1, 2009 8:08 AM Valued Member Group: General Forum Members Last Login: Friday, December 12, 2014 8:34 AM Points: 53, Visits: 237 Thank you all. Issue resolved. Just the restart of SQL Server Agent Service worked. Seems that Agent log file was either locked or corrupted. Each time the stored procedure was run it just overwritten the current agent log without renaming it and because of this only one SQLAGENTOUT file was left. Kindest Regards,Ajay Prakash Post #647704 JonrJonr Posted Thursday, November 13, 2014 4:57 AM SSC-Enthusiastic Group: General Forum Members Last Login: Friday, June 19, 2015 7:41 AM Points: 142, Visits: 65 Just to clarify, there are two stored procs being referred to here:sp_cycle_agent_errorlog - cycles the SQLAgent error logsp_cycle_errorlog - cycles the SQL Server database engine error log.Both of these stored procs reside in the msdb database, and both require sysadmin role membership, but not necessarily
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Agent job will not run up vote 4 down vote favorite I created a JOB to run a simple package that runs a query and saves the results to an Excel file. If I try to run the job In SQL Management Studio I get an error saying: SQLServerAgent is not currently running so it cannot be notified of this action. (Microsoft SQL Server, Error: 22022). I made sure that SQLServerAgent was in fact running and tried running the job again (from SQL Managment Studio) but still got the same message. I found this knowledge base article which is telling me that I have to edit the Registry in order to resolve the problem. Before I go in and start messing with the registry which is something I really don't want to do I was wondering if anyone else has experienced this problem and if they had to edit their registry to fix it? sql-server sql-server-2012 sql-server-agent jobs share|improve this question edited Dec 2 '12 at 6:23 Paul White♦ 29.5k11164263 asked Dec 2 '12 at 6:04 PokerPlayer23 1,05882844 3 Have you tried restarting the SQL Agent? –mrdenny Dec 2 '12 at 6:38 i haven't. I will give that a try and report back tommorow. Thanks. –PokerPlayer23 Dec 2 '12 at 6:58 4 Look in the SQL Server Agent's error log for any peculiar and indicative messages. –Thomas Stringer Dec 2 '12 at 13:05 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote accepted