5

After applying SQL Server 2016 SP2 CU1 (SP2 was already applied) to SQL Server 2016 on several different Windows Server 2016 installations, we noticed that Database Mail stopped working. Mails were being queued but not sent and we could find no error messages on the servers, neither in the SQL Server logs nor in the Windows Server event logs.

After verifying that none of the settings for Database Mail had changed and that everything was as it should be with regards to mail relaying server and other external factors, we could see that an old problem seemed to have resurfaced:

The DatabaseMail.exe.config configuration file for DatabaseMail.exe, allowing it to work without having .NET Framework 3.5 installed, had been removed by the SQL Server 2016 SP2 CU1 update.

On all instances where the patch had been applied, the config file above was missing from the binaries directory for the SQL Server installation. It was present before the patch was applied.

Example configuration file path: C:\Program Files\Microsoft SQL Server\MSSQL13.instance_name\MSSQL\Binn\DatabaseMail.exe.config

Improve this question
3
  • 1
    Yes, other people have experienced this problem. Is that your question?
    – Aaron Bertrand
    Jun 19, 2018 at 14:13
  • Hi Aaron. Yes, that is my question as I have searched and not found any references to other people experiencing the same issue so far.
    – Jonas Olsson
    Jun 19, 2018 at 15:26
  • Well other people have experienced this problem (click on the link in my comment), but this type of question is not really a good fit for this site. We're here to solve issues, not compare scars. :-)
    – Aaron Bertrand
    Jun 19, 2018 at 15:42

1 Answer 1

Reset to default
3

The main point of the question was to check if other people had the same issue and to help spread the information on issues with the SQL Server 2016 SP2 CU1 patch. Since these objectives have been reached and there is a solution presented in the post, I will close this as answered.

The solution was as follows:

We recreated the file based on the following KB article: https://support.microsoft.com/en-us/help/3186435/fix-sql-server-2016-database-mail-does-not-work-on-a-computer-that-doe

After that we had to restart the Database Mail queues to start processing queued mails:

USE msdb;
EXEC sysmail_stop_sp;
EXEC sysmail_start_sp;

This cleared the issue and any queued messages were successfully sent.

Patch link: https://support.microsoft.com/en-us/help/4135048/cumulative-update-1-for-sql-server-2016-sp2

Improve this answer
1
  • I've just had the same problem reoccur with SQL 2016 SP2 CU2. Although it only seemed to affect my Win 2016 servers and not Win 2012.
    – Sir Swears-a-lot
    Oct 15, 2018 at 20:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.