Agent stopped when Job running
-
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
-
That is precisely why I switched from using MAPI based SQL Agent Mail to xp_smtp_sendmail from http://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.
--------------------
Colt 45 - the original point and click interface
-
I agree with Phil using SQL Mail in SQL 2000 sucks. Looking forward to SQL 2005 which uses SMTP mail.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply