SQL Server Agent Jobs not running 'SQL Server Agent is not currently running so it cannot be notified of this action. (Microsoft SQL Server, Error: 22022)'
Question
Wednesday, January 16, 2013 1:13 PM
Hello All,
We have sql 2008 R2 SP1 A/P cluster running on VM.
SQL Server Agent jobs are not running. If I manually try to run the job it gives below error
'SQL Server Agent is not currently running so it cannot be notified of this action. (Microsoft SQL Server, Error: 22022)'
I checked SQL server Agent service is running, and the service account under it is running has 'sa' access to sql server.
'Agent Xps' has been set to 1.
If I browse to SQLagent.out file. it is completely blank.
Any help on this will be appreciated. Thank You.
-Kranp.
All replies (10)
Wednesday, January 16, 2013 1:41 PM
Was there any restart happened for SQL Agent? See SQL error log and see if MSDB is up and online, some times if the MSDB is not recovered properly, SQL Agent shows as started but doesnt really come up online till MSDB is recovered properly.
Is the SQL Server Agent resource running? Do you see any errors in the Application event logs?
Wednesday, January 16, 2013 1:42 PM
did you check the startup account used to start the agent services
Ramesh Babu Vavilla MCTS,MSBI
Wednesday, January 16, 2013 9:37 PM
This is most likely this issue (even though it refrences SQL 2000, Agent has not changed):
http://support.microsoft.com/kb/911841
This probably means SQL Agent is not installed correctly on your cluster. Is your SQL Agent in the same cluster group as the SQL Server?
Please see:
http://msdn.microsoft.com/en-us/library/ms179530(v=sql.105).aspx
Wednesday, January 16, 2013 10:39 PM
HI there,
Have you tried to run any of the existing jobs to make sure Agent is working. If you can not do it Ashwin may be correct.
Try restarting your agent. problem still exists do a server restart. if problem still exists i am sure you will find the root cause.
Server restart will fix your problem (or) will let you know the problem.
good luck
kumar
Wednesday, January 23, 2013 6:21 PM
yes SQL Agent is in the same cluster group as SQL Server.
I verified SQL service is running fine. Event log is not showing any specifics that correlate with this error.
Everything I tried is not working.
Thanks,
Kranp.
Wednesday, January 23, 2013 6:28 PM
Hi Kranp,
This occurs when any of the database on the SQL server instance is in recovry mode after the SQL Server Recycle. Check in the errorlog if any of the database is still in recovering mode. If so, once that database get recovered completely, your SQL Server Agent will work properly.
Thanks,
Mayur Yelpale
Wednesday, January 23, 2013 6:37 PM
Mayur, There are no databases in recovery mode. SQL Server has started clean. Thanks.
Thursday, January 24, 2013 5:04 PM
Inside SQL Server Network Configuration,
For TCP/IP, if I changeTCP Dynamic Ports to '1433', SQL Server agent job start running.
Not sure why it is not working for updated port value.
Apart from SQL server Configuration Manager, any where else do I need to update the port changes?
Thanks,
Kranp.
Thursday, January 24, 2013 6:55 PM
HI
By any chance any other app configured on 1434( ideal dynamic port) jsut to check
ramakrishna
Sunday, January 27, 2013 6:22 AM
There is no reply on this thread?????
any updates\ ideas please help....thanks.