Event 7022 - SQL Agent hung on starting

Question

Event 7022 - SQL Agent hung on starting

druidia

Mr or Mrs. 500

Points: 551
More actions
May 19, 2006 at 8:37 am

#112916

We're having a problem that is happening on a handful of SQL servers; not all of them. We've had a case open with MS for a few weeks, but they are stumped and are not really helping.
We upgraded all of our SQL servers to Outlook 2003 SP2 from Outlook 2000 for SQL Mail. On some of the servers, we began getting an error in the System event log upon reboot:
"Error 7022: The SQLSERVERAGENT service hung on starting."
It is consistently delayed behind the reboot for 1 min, 50 secs; then it starts.
The servers are SQL 2000 SP4, Outlook 2003 SP2, using domain accounts for both services.
There are no errors in the SQL agent error log. It shows it trying to load the SQL Mail profile, and 1:50 later, it successfully starts the MAPI session.
It also works successfully with no delays when we put it back to Outlook 2000, so it is clearly related to Outlook 2003.
We've tried pulling off Outlook and deleting profiles, reinstalling...and we still have the error.
We've tried disabling and booting services one at a time and booting the server and have not been able to successfully and consistently narrow it down to any particular service it is contending with.
I've checked Google groups, TechNet and random web searches to no avail.
Wondering if anyone has experienced anything similar.
TIA.
~JDP

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

SQLBill SSC Guru Points: 51440 More actions · Answer 1

Look at dependancies......did something get changed where SQLServerAgent is dependant upon Outlook services starting first?

Can you try setting Outlook's services to be dependant upon SQLServerAgent service (I think that will make Outlook wait until SQLServerAgent is running).

-SQLBill

druidia Mr or Mrs. 500 Points: 551 More actions · Answer 2

The only dependency is SQL Agent is dependent upon SQL Server, and that starts normally.

Outlook does not run as a service.

Thanks.

~JDP

MVDBA (Mike Vessey) SSC-Insane Points: 21797 More actions · Answer 3

we have a similar problem in that a few of our outlook 2003 installations take a long time to initialise. this causes sql agent to hang.

interestingly enough - these 2003 installations also take a long time to synchronise with the mail server and quite often i can send an internal mail to the sql server and walk to the server room , sit at the desk and wait 3 or 4 minutes before i get the email..

i can't offer a fix other than not to use outlook 2003 in fact we have alternate methods of monitoring now that involve using sql 2005 as a messaging relay server for our production boxes.

or alternatlively upgrade to 2005 if you can

MVDBA

druidia Mr or Mrs. 500 Points: 551 More actions · Answer 4

Interesting to know someone is having a similar problem.

How do you know that they are taking a long time to synchronize with the mail server? Have you done network traces?

Unfortunately we aren't really prepared to put 2005 in our environment right now.

I just don't understand why it is happeneing on a handful of servers. It's very frustrating.

~jdp

MVDBA (Mike Vessey) SSC-Insane Points: 21797 More actions · Answer 5

the problem we're seeing with 2003 is not a network issue, it's a casae of outlook 2003 jsut not behaving the way 2000 used to.

the problem is really evident when you have 2 laptops in front of you, with outlook 2000 on one and 2003 on the other - send an email from 2003 to 2000 and it's there straight away, do it the other way round and you're actually quicker hitting "send and receive" rather than waiting for the email.

it's quite annoying as you often get someone saying "did you get that email i just sent you" - and the answer is usually no, followed by "send and receive" and oh - yes there it is!!

MVDBA