Ms Sql 2008 Error 22022
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Error 22022 : SQL server Agent is not curretnly running so it cannot be notified of this action appears in SQL 2008 SP1 in Windows 2008 R2 SQL Server > SQL Server Migration Question 0 Sign in to vote Hi We have SQL agent started. But still if we run any job, its giving a message "SQL server Agent is not currently running so it cannot be notified of this action Error 22022". OS is windows server 2008 & SQL server is SQL 2008 SP1(10.00.2531) Monday, June 07, 2010 4:34 PM Reply | Quote Answers 0 Sign in to vote Hello, Please see the following post by Chris Skorlinski for information on how to troubleshoot this issue: http://blogs.msdn.com/b/repltalk/archive/2010/05/31/sqlserveragent-is-not-currently-running-so-it-cannot-be-notified-of-this-action.aspx Hope this helps. Regards, Alberto Morillo SQLCoffee.com Proposed as answer by Keshav RamaraoMicrosoft employee Wednesday, June 09, 2010 1:19 AM Marked as answer by Keshav RamaraoMicrosoft employee Tuesday, June 15, 2010 9:43 PM Tuesday, June 08, 2010 3:19 AM Reply | Quote Moderator Microsoft is conducting an online survey to understand your opinion of the Msdn Web site. If you choose to participate, the online survey will be presented to you when you leave the Msdn Web site.Would you like to participate? Privacy statement © 2016 Microsoft. All rights reserved.Terms of Use|Trademarks|Privacy Statement|Site Feedback
SERVER - FIX: SQLServerAgent is not currently running so it cannot be notified of this action. (Microsoft SQL Server, Error: 22022) January 1, 2016Pinal DaveSQL, SQL Server, SQL Tips and Tricks3 commentsGetting error and finding the cause is something which I like. And off late over the blogs I have shared a number of such incidents that have helped me figure out stuffs all by myself. Of course, I do my research and more often than not make things complicated because there are a number of resolutions that I find. I also make it a point to check with a few friends from Microsoft to a https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9deb01ba-dfb5-4f99-bbc1-daba39a90aa8/error-22022-sql-server-agent-is-not-curretnly-running-so-it-cannot-be-notified-of-this-action?forum=sqlservermigration possible cause because it is easy to get help than walk the tough line of finding it myself. One fine day I restarted my virtual machine and then I wanted to take a full backup of all databases before formatting the machine. As soon as I hit on execute button, as shown below, I was welcomed with an error message.Here is the error which I http://blog.sqlauthority.com/2016/01/01/sql-server-fix-sqlserveragent-is-not-currently-running-so-it-cannot-be-notified-of-this-action-microsoft-sql-server-error-22022/ received.Complete text of the error message is below: TITLE: Execute Maintenance Plan -------------------- Execution failed. See the maintenance plan and SQL Server Agent job history logs for details. -------------------- ADDITIONAL INFORMATION: An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) -------------------- SQLServerAgent is not currently running so it cannot be notified of this action. (Microsoft SQL Server, Error: 22022) For help, click: https://www.microsoft.com/en-us/?ProdName=Microsoft+SQL+Server&ProdVer=12.00.2480&EvtSrc=MSSQLServer&EvtID=22022 -------------------- BUTTONS: OK --------------------Error message is very clear. SQL Server Agent service should be running before we can execute maintenance plan. If we notice the first screen shot, it’s clear that SQL Server Agent was not running. So solution looked very simple, start the SQL Server Agent Service. It was not started by its own because it was set to manual mode.To avoid such error in the future, I change the “Start Mode” of the service, to automatic by going to the properties of the service.I also found that sometimes you would get this error even if the SQL Server Agent is running. In those cases, you need to check SQLAgent.out file to check if it’s started completely.Something SQLAgent.out would show ONLY below messageWaiting for SQL Server to recover data
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 http://dba.stackexchange.com/questions/29662/agent-job-will-not-run about Stack Overflow the company Business Learn more about hiring developers or posting http://stackoverflow.com/questions/27746752/copy-database-fails-with-sql-agent-not-started-error-but-it-is-running 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 ms sql 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 ms sql 2008 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.7k11167267 asked Dec 2 '12 at 6:04 PokerPlayer23 1,06882844 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 Turns out I was connecting to a Load Balancer
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 Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Copy database fails with SQL Agent not started error, but it is running up vote 0 down vote favorite I'm trying to copy a database to another server. I've successfully done this with these two servers several times, the last time was just a few days ago. However, now when I try to execute it, I get an error: TITLE: Copy Database Wizard ------------------------------ Start failed for Job 'CDW_xxxx_SGSTG51DBA01_13_2'. ------------------------------ ADDITIONAL INFORMATION: An exception occurred while executing a Transact-SQL statement or batch (Microsoft.SqlServer.ConnectionInfo) ------------------------------ SQLServerAgent is not currently running so it cannot be notified of this action. (Microsoft SQL Server, Error: 22022) Base on this information, I immediately checked that SQL Agent was running. It wasn't, so I started it. I ran it again, but got the same error. I then double checked that the login information provided for both the source and destination servers was correct. It was. So I'm now getting this error with verified connection information and SQL agent is running. What else could be causing this problem? Does the account running SQL agent need access to both servers? sql-server-2012 share|improve this question asked Jan 2 '15 at 18:26 Greg McGuffey 1,03611533 2 Did you check SQL Server Agent on both machines? Sounds like you only checked one (and perhaps not the right one). You could also just consider performing a backup and restore, which doesn't require the wizard, SSI