Post reply

Failed to notify ''operator name'' via email?

  • December 11, 2012 at 9:46 am

    #1567517

    Got the same problem over here, google it, found this thread and... it resolved my problem !!

    Thank you 😀

  • December 12, 2012 at 2:49 pm

    #1568076

    I recently encountered a situation on a new server (SS2012) where I wanted an email notification if any SQL Agent job failed to execute to successful completion but could not get it to work. I never had the problem before. ????

    To test it, I created a SQL Agent job with a T-SQL script that was bound to fail, executed it, and no email message was received.

    To make a long research story short, placing this short T-SQL script at the beginning of all SQL Agent jobs' T-SQL scripts solves the problem:

    "SET XACT_ABORT ON"

  • January 8, 2013 at 5:53 am

    #1574775

    It works 4 m... Thanks 😀

  • October 15, 2013 at 11:54 am

    #1658636

    This was the answer I needed. Thanks.

    🙂

  • October 23, 2013 at 10:49 am

    #1661036

    hey, very helpful information!:-)

  • January 6, 2014 at 4:41 am

    #1677699

    TNX!! helped me a lot!

  • April 11, 2014 at 6:41 pm

    #1705493

    Excellent Post, Thanks as well!!!

  • April 23, 2014 at 10:16 pm

    #1708296

    Gerd Hoefler (4/21/2006)

    Hi all,

    some time ago i had the same problem.

    I fixed this and make a docu to solve this.

    But i have no idea how i can post this document here.

    If everyone would have this, send me a mail: <A href="mailto:gerd.hoefler@gmx.at">gerd.hoefler@gmx.at</A>

    Gerd

    8 years and 2 days, several versions of SQL and this post still helps...:w00t:

  • April 24, 2014 at 7:33 am

    #1708406

    I sometimes see criticism of posting on old threads. I think the criticism is misplaced.

    Good information is never antiquated.

  • May 6, 2014 at 3:06 pm

    #1711283

    henrik staun poulsen (2/17/2006)

    I just had the same problem.

    Ihad to enable DatabaseMail on the SQL Server Agent -> properties -> Alert System (check the checkbox), and then restart SQL Server Agent.

    It works now, thanks to a posting by "Johnny" in microsoft.public.sqlserver.serverwith the topic "How to setup Operator for sending alerts?"

    HIH

    Henrik Staun Poulsen

    8 years later, this is still relevant.... thanks, that was causing my problem today 🙂 Two servers, one with this set right and one it got missed on and we couldn't figure out why some jobs notified upon failure and others didn't.

  • November 21, 2014 at 10:22 am

    #1760226

    Perfect! That's just the info I needed.

  • June 22, 2015 at 12:04 pm

    #1807139

    Hi Gerd

    I have sent an email to you asking yu to send me the document but got a bounced back email.

    Can you please tell me your present email id?

    Thanks.

  • January 22, 2016 at 11:10 am

    #1853880

    Just wanted to keep the "Thank You" chain going into year 2016!

    I was having this exact same problem in SQL Server 2008 and enabling Alerts for SQL Server Agent and restarting the service worked for me.

    Thanks a million!

  • April 2, 2017 at 7:51 pm

    #1936198

    The answer is still going strong - than you.
    enable DatabaseMail on the SQL Server Agent -> properties -> Alert System (check the checkbox), 
    2016 - nice if the error message could have given more clues.
    Anyway - thank you

  • July 30, 2018 at 2:47 am

    #1999420

    henrik staun poulsen - Friday, February 17, 2006 3:47 AM

    I just had the same problem.I had to enable DatabaseMail on the SQL Server Agent -> properties -> Alert System  (check the checkbox), and then restart SQL Server Agent.It works now, thanks to a posting by "Johnny" in microsoft.public.sqlserver.server with the topic "How to setup Operator for sending alerts?"HIHHenrik Staun Poulsen

    Thank you henrik !! It worked for me as well !!

Viewing 15 posts - 61 through 75 (of 75 total)

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