Reputation: 4477
After configuring database mail on one server and sending a test email, I am finding nothing in the queue or the log. The mail id, however, keeps incrementing with each retry. I have checked the following:
EXEC msdb.dbo.sysmail_help_status_sp;
reports STARTED
SELECT sent_account_id, sent_date FROM msdb.dbo.sysmail_sentitems;
SELECT * FROM msdb.dbo.sysmail_event_log;
SELECT is_broker_enabled FROM sys.databases WHERE name = 'msdb';
I have configured this successfully on 4 other instances, it's just one that is giving me grief. Any other pointers would be appreciated.
Upvotes: 4
Views: 6233
Reputation: 4477
Looks like this issue is with a bug in the version of sql that I am running on this instance as explained here: https://support.microsoft.com/en-us/help/3186435/fix-sql-server-2016-database-mail-does-not-work-on-a-computer-that-doe
Installing CU2 will fix it:
Note This issue also affects instances that are running SQL Server 2016 SP1 CU1. This issue occurs because of a bug in SQL Server 2016 SP1 CU1 setup. The setup for SQL Server 2016 SP1 CU1 deletes the config file DatabaseMail.exe.config without replacing it with a new one. This causes the Database Mail to break in the absence of .Net framework 3.5 SP1. The fix in SQL Server 2016 SP1 CU2 is meant to address this issue and prevent the DatabaseMail.exe.config file from getting deleted from the machine after installing a CU. So if you install SQL Server 2016 SP1 + CU2, the Database Mail will not be impacted by the setup. However, if the Database Mail is broken by the installation of SQL Server 2016 SP1 CU1, you can use any one of the workarounds mentioned below.
Upvotes: 1