Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Agent stopped when Job running


Agent stopped when Job running

Author
Message
Sql Junkie-204042
Sql Junkie-204042
Old Hand
Old Hand (360 reputation)Old Hand (360 reputation)Old Hand (360 reputation)Old Hand (360 reputation)Old Hand (360 reputation)Old Hand (360 reputation)Old Hand (360 reputation)Old Hand (360 reputation)

Group: General Forum Members
Points: 360 Visits: 168

We frequently stop SQL Server Agent whenever Exchange server is rebooted because of this

Last night the Exchange server was rebooted and the Agent was stopped when one of the Sync Job was running. This job usually takes 2 hours to run and is scheduled to run at night when there are no users. The Network Admin. failed to notice that this job was running. The job log shows this error 'The job was stopped prior to completion by Shutdown Sequence 0'

On a normal run, when this job fails email is sent to all Admins. Since this job was stopped manually (by the Agent) no email was sent.

It would be nice if the Agent pops a message that Jobs are running before a Stop request is sent.

Is there any preventive steps that can be taken ?

TIA


philcart
philcart
SSCrazy
SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)

Group: General Forum Members
Points: 2752 Visits: 1434

That is precisely why I switched from using MAPI based SQL Agent Mail to xp_smtp_sendmail from www.sqldev.net

Once setup, you can bounce the Exchange server as much as you like and email from SQL Server still works.

As for preventive steps. You could try putting together a VBScript of some description to check for running jobs and then stop the Agent.



Hope this helps
Phill Carter
--------------------
Colt 45 - the original point and click interface

Australian SQL Server User Groups - My profile
Phills Philosophies
Murrumbeena Cricket Club
Vik Nat
Vik Nat
Old Hand
Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)

Group: General Forum Members
Points: 342 Visits: 68
I agree with Phil using SQL Mail in SQL 2000 sucks. Looking forward to SQL 2005 which uses SMTP mail.



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search