December 8, 2008 at 6:17 am
Ever since we upgraded from SP1 to SP2, all our Operators have stopped working. Or should I say, the notification from our jobs to the operators have stopped working.
We have jobs set to notify Operator when they fail. We've recreated the Operators, and created ones with new names, several times. We've tried single email addresses, an AD group email address, a list of individual email addresses strung together and a beeper number. All of which worked in SP1 but none of which seem to work now.
Has anyone else seen this problem? Does anyone have a solution?
Thanks,
December 8, 2008 at 7:29 am
Brandie,
Does anything from Database Mail work? The only issue I know of when applying SP2 was that the setting the Reply TO email did not work.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
December 9, 2008 at 12:45 am
Hi Brandie,
I am having the same problem. I wanted to play around with the notification possibilities and tried doing the same things as you, but to no avail.
I was testing by adding a notification for when a logfile is more than 50% used. It should have sent me an email, but nothing happened. I made sure to pump the logfile up, but it flat refused to send anything.
Its not too critical at the moment, but it has stopped me from investigating this avenue of automation further.
Any info/tips would be greatly accepted from me too!
Regards
GermanDBA
Regards,
WilliamD
December 10, 2008 at 1:56 am
What are the results of using
exec msdb.dbo.sp_notify_operator @name = '<operator>'
a) in query window of SQL Server Mgt Studio
b) as the code in a job step of an SQL Agent
1. If both fail, you have not enabled either Database Mail or SQL Mail stored procedures (I doubt this)
2. If executes successfully in (a), but not (b), have you defined properties within the Alert System tab within the SQL Agent Properties to specify which mail system and mail profile to be used?
This latter option assumes you have configured a public mail profile for Database Mail.
3. If both of these method of manually initiating an operator work, I do not have any other suggestions where it could be failing.
------
Robert
December 10, 2008 at 4:12 am
Jack,
We don't usually use the ReplyTo functionality of the DatabaseMail. Most of our stuff is general DBA Team alerts on failed jobs (non-repliable emails).
Rcavill, Yes, the procs were enabled and yes, the Alert Tab was set up correctly. I did your test and both tests worked without a problem. I've even got a Fail-Safe Operator set up. We're still not getting it to work.
So it's got to be a problem in the Job Notification properties when we're setting the operator.
Any other thoughts?
Brandie
December 10, 2008 at 5:12 am
Jack,
Do you know what the ReplyTo problem was? Or at least a good search term for me to find the problem?
December 10, 2008 at 6:15 am
Brandie,
Here's a link to the Connect issue I created for it: https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=335613. It was fixed in a cumulative update which I list in my blog, http://wiseman-wiseguy.blogspot.com/2008/07/ghost-of-sql-server-2005-database-mail.html
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
December 12, 2008 at 7:16 pm
I couldn't believe it! I have had the same situation occur during the week for one of the SQL Servers. The notifications for jobs were not being received. The event log show "NOTE: Failed to notify via email."
As far as I can gather, a change had been made for some properties on the Alert System attributes for SQL Agent properties.
Anyhow, restarting the SQL Agent resolved the issue, as suggested in:
http://www.sqlservercentral.com/Forums/Topic263951-92-1.aspx#bm389494
------
Robert
December 13, 2008 at 7:30 am
Well, we'll see if the restart works. I won't know until Monday.
Truthfully, though, I doubt this will solve my problem. We've failed over our cluster a number times since this problem started (services stopping & restarting) due to OS patches & such. If it hasn't resolved by now, I doubt a manual restart will do it.
Still, I'm giving a shot. Just in case.
Thanks,
December 15, 2008 at 6:10 am
Nope. The SQL Agent Service restart didn't help me.
Darnit. This is annoying.
December 17, 2008 at 4:22 am
DOH!
I went back and checked our accounts after reading the Microsoft fix bulletin. Sure enough, different ReplyTo addresses than what's in the account name.
Fixed that and it still didn't work. Restarted SQL Server Agent and it started working. Now I have to bug the server people to install the hot fix.
Thanks, Guys. You really helped me out.
January 14, 2009 at 11:25 am
Brandie, how did you fix it?
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply