- IT
- Cancel
Настраиваем бэкап баз SQL.
Открываем SQL Studio, добавляем план обслуживания, выбираем резервное копирование, прописываем папку для бэкапов, настраиваем расписание.
Вот хорошая инструкция: http://howknow1c.ru/nastroika-1c/backup-sql.html
Сохраняем план обслуживания, встаем на него и говорим «Выполнить».
Ошибка. Ругается на незапущенный агент SQL.
«Ошибка 22022: SQLServerAgent не запущен, не может получать уведомления об этой операции.»
Стартуем Агент SQL Server вручную. Не стартует.
Решение: меняем учетную запись, от которой запускается служба Агент SQL Server с sa на системную учетную запись.
Тип запуска: ставим автоматический.
Запускаем. Все работает.
Вроде бы все тривиально, но мало ли, вдруг кому пригодится…
- Remove From My Forums
-
Question
-
When trying to run a maintenance job I receive the error «SQLServerAgent is not currently running so it cannot be notified of this action. (Microsoft SQL Server, Error: 22022)». The agent starts and then stops. What would cause this?
Answers
-
-
Edited by
Tom Phillips
Monday, December 9, 2013 7:22 PM -
Proposed as answer by
Shanky_621MVP
Tuesday, December 10, 2013 5:26 AM -
Marked as answer by
Sofiya Li
Saturday, December 21, 2013 2:14 PM
-
Edited by
All replies
-
Please see the SQLAGENT.OUT in the LOG directory for the reason Agent is not running.
-
I rebooted like it says below but was trying to run the job before and after. I tried manually starting the agent a few times too.
2013-11-26 19:59:18 - ? [100] Microsoft SQLServerAgent version 11.0.3128.0 (X64 unicode retail build) : Process ID 4676 2013-11-26 19:59:18 - ? [495] The SQL Server Agent startup service account is NT Service\SQLSERVERAGENT. 2013-11-26 19:59:18 - ? [393] Waiting for SQL Server to recover database 'msdb'... 2013-11-26 19:59:18 - ? [000] 2013-11-26 19:59:18 - ? [101] SQL Server SERVER version 11.00.3128 (0 connection limit) 2013-11-26 19:59:18 - ? [102] SQL Server ODBC driver version 11.00.3000 2013-11-26 19:59:18 - ? [103] NetLib being used by driver is DBNETLIB; Local host server is 2013-11-26 19:59:18 - ? [310] 4 processor(s) and 6144 MB RAM detected 2013-11-26 19:59:18 - ? [339] Local computer is SERVER running Windows NT 6.1 (7601) Service Pack 1 2013-11-26 19:59:18 - ? [432] There are 12 subsystems in the subsystems cache 2013-11-26 19:59:34 - ! [364] The Messenger service has not been started - NetSend notifications will not be sent 2013-11-26 19:59:34 - ? [129] SQLSERVERAGENT starting under Windows NT service control 2013-11-26 19:59:34 - + [475] Database Mail is not enabled for agent notifications. 2013-11-26 19:59:34 - + [396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect 2013-11-26 20:00:32 - ? [130] SQLSERVERAGENT stopping because of Windows shutdown... 2013-11-26 20:00:33 - ! [359] The local host server is not running 2013-11-26 20:00:34 - ! [359] The local host server is not running 2013-11-26 20:00:34 - ? [098] SQLServerAgent terminated (normally)
-
Also seeing this in ERRORLOG.
2013-11-26 20:30:43.08 Logon Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'model'. [CLIENT: 10.x.x.x] 2013-11-26 20:30:43.09 Logon Error: 18456, Severity: 14, State: 38.
-
-
Edited by
Tom Phillips
Monday, December 9, 2013 7:22 PM -
Proposed as answer by
Shanky_621MVP
Tuesday, December 10, 2013 5:26 AM -
Marked as answer by
Sofiya Li
Saturday, December 21, 2013 2:14 PM
-
Edited by
-
Thank you sir! I will check it out and get back with you.
SQL Server Error 22022: SQL Server Agent is not currently running so it cannot be notified of this action.
Got stuck with this error when running a SQL server agent?
Basically, SQL server error
At Bobcares, we often get requests to fix SQL errors, as a part of our Server Management Services.
Today, let’s see how our Support Engineers fix the SQL server error 22022 for our customers.
Causes for the SQL Server Error 22022
Mainly 2 processes are required for the SQL Server to run properly. The two processes are the SQL server(MSSQLSERVER) and SQL Server Agent. This error occurs when the SQL Server Agent is not running.
The sample error message will look like.
How we fix SQL Server Error 22022?
Recently, one of our customers contacted us with the SQL Server Error 22022. The SQL server agent service was not running. Now let’s see how our Support Engineers fix this error for our customers by starting the service.
1. Make sure that the SQL Server Agent service running.
To resolve this error for our customers, we first check the SQL server agent service state and then start the service.
To do this, we follow these steps:
- We click on >> Start >> click >>Run, then we type>> Services.msc, and then click >> OK.
- Then in the Services window, we locate the SQL Server Agent service.
- After this, we make sure that the value of the Status column of the SQL Server Agent service.
- The SQL Server Agent was not running.
- Then we Right-click SQL Server Agent, we click the Start button. Finally, click Yes.
2. Make sure the SQL agent property as automatic.
If the SQL agent property already set as manual mode, if there is any chance to stop the service after a reboot.
So we make sure that the SQL service agent Start Mode is set as automatic.
To avoid such situations, our Support Engineers change the “Start Mode” of the service, to automatic by going to the properties of the service.
Sometimes we get this error even if the SQL Server Agent is running. In those cases, we check SQLAgent.out file to check if it’s started completely.
[Still having trouble in fixing SQL server errors? We’ll fix it for you.]
Conclusion
In short, the SQL server error 22022
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
GET STARTED
var google_conversion_label = «owonCMyG5nEQ0aD71QM»;
This is for very first time that I am trying to use SQL server Agent.
I get this error :
Msg 22022, Level 16, State 1, Line 0
SQLServerAgent is not currently running so it cannot be notified of this action.
I went to services to check if it was running. I tried to start it and got this immediately . The services then stopped ofcourse.:
Then I tried with SQL server configuration manager:
On trying to start the service there,
When I try to change the log on account via SQL server configuration manager:
How do I get this service started ?
asked Mar 22, 2015 at 15:27
It can happen as well that you have SQL Service Agent installed on your server with the database, but as the message says it is not running.
Go to Control Panel -> Administrative Tools -> Services and check if service SQL Service Agent is running.
answered Oct 16, 2018 at 8:49
HawlettHawlett
83616 silver badges23 bronze badges
0
The SQL Server Express editions does not include the SQL Server Agent component. If you want that you need to use any of the versions that includes it (Enterprise, Business Intelligence, Standard or Web).
Reference: Features Supported by the Editions of SQL Server 2014 (the same limits applies to earlier editions too).
answered Mar 22, 2015 at 16:29
jpwjpw
44.4k6 gold badges66 silver badges86 bronze badges
2
Getting 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 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 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 message
Waiting for SQL Server to recover databases…
If you are running in that issue, please have a look at https://support.microsoft.com/en-us/kb/2640027 to get a fix for the issue.
Have you even fixed such simple issues? The error messages over the ages have become obvious and very helpful too.
Reference: Pinal Dave (https://blog.sqlauthority.com)