Maintenance Plans Notify Task Issue

Question

All,

We are using DB mail and are able to send mail.  In the maintenance plan if you add the Notify Task you get an error saying the database is not setup.  I have gone through all setup again - sent test mail and have mail working for other processes but still get the same error for the Notify Task.  I ran the sql code the Notify task uses and it works as well.  Is this bug?  We are running SQL 2016.

Thank you, 

Dan

Answer 1

I rarely use maint plans, but perhaps this task uses the Agen config for Database Mail? I.e., perhaps it fails if you didn't configure what main profile Agent should use (Agent, properties in the GUI).

---

Tibor Karaszi, SQL Server MVP (Web Blog)

Answer 2

Hi Dan Bigelow,

Could you please share the screenshot of the error message to us for analysis? I tested it on SQL Server 2016, but I did not see a similar problem. I think this is something wrong with configuration instead of a bug.

I suggest you reading this article: http://www.rad.pasfu.com/index.php?/archives/52-Notify-Operator-Task-SSIS.html to check if you have missed some steps or use some wrong configuration such as the Database Mail profile Security settings, is it public or private?

Best Regards,

Teige

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 3



Answer 4

The image is what I get when I try to add the task to a new plan.  I get the other image when I try and trouble shoot an existing plan.  

Answer 5

Answer 6

SQL Agent must be setup with Alert System -> Enable Mail Profile.

You also need to restart SQL Agent after making that change to take affect.

https://docs.microsoft.com/en-us/sql/relational-databases/database-mail/configure-sql-server-agent-mail-to-use-database-mail

Answer 7

I have done that

Answer 8

What version of SSMS are you running?   Try updating to the current version.

Answer 9

This is a known issue fixed in SP1 + CU2.

See:

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/5bc30c4e-a3f7-4358-a434-e6a7ced4da49/sql-2016-database-mail-breaks-after-sp1-cu1-without-net-35?forum=sqlnotificationservices#6c247059-342b-4196-9450-d5b947908d6b