Ошибка 22022 sql server

June 8 2012, 15:04

Category:

  • IT
  • Cancel

Настраиваем бэкап баз SQL.

Открываем SQL Studio, добавляем план обслуживания, выбираем резервное копирование, прописываем папку для бэкапов, настраиваем расписание.

Вот хорошая инструкция: http://howknow1c.ru/nastroika-1c/backup-sql.html

Сохраняем план обслуживания, встаем на него и говорим «Выполнить».

Ошибка. Ругается на незапущенный агент SQL.

«Ошибка 22022: SQLServerAgent не запущен, не может получать уведомления об этой операции.»

Стартуем Агент SQL Server вручную. Не стартует.

Решение: меняем учетную запись, от которой запускается служба Агент SQL Server с sa на системную учетную запись.

Тип запуска: ставим автоматический.

Запускаем. Все работает.

Вроде бы все тривиально, но мало ли, вдруг кому пригодится…

Источник

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 22022 occurs due to the SQL Agent cannot connect to the SQL Server database engine.

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:

  1.  We click on >> Start >> click  >>Run, then we type>> Services.msc, and then click >> OK.
  2. Then in the Services window, we locate the SQL Server Agent service.
  3. After this, we make sure that the value of the Status column of the SQL Server Agent service.
  4. The SQL Server Agent was not running.
  5.  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 occurs due to the SQL Agent cannot connect to the SQL Server database engine. Today, we saw how our Support Engineers sort out the SQL server error.

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»;

Источник

RRS feed

  • 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

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 ServiceSQLSERVERAGENT.
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 AUTHORITYSYSTEM'. 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

  • Thank you sir! I will check it out and get back with you.

Источник

RRS feed

  • 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

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 ServiceSQLSERVERAGENT.
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 AUTHORITYSYSTEM'. 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

  • Thank you sir! I will check it out and get back with you.

Источник

……………………………………………………………………………………………………………………………………………………………………………….

 Error 22022: SQLServerAgent is not currently running 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

Источник

Понравилась статья? Поделить с друзьями:
  • Ошибка 2202 форд фокус 2
  • Ошибка 22 митсубиси лансер 9 srs
  • Ошибка 2202 kyocera при сканировании на почту
  • Ошибка 22 митсубиси аутлендер акпп
  • Ошибка 22008 postgresql