Bobcares

Best way to fix – SQL Server Error 22022

by | Oct 22, 2019

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

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF