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.
- Create the DatabaseMail.exe.config and drop it next to the DatabaseMail.exe under the Binn folder. You can use notepad.exe or any other editor to edit it. Just make sure you save it by using UTF-8 encoding (in notepad.exe, select Save As... and in the Encoding combo box, select UTF-8):
<?xml version="1.0" encoding="utf-8" ?>
- Run a repair setup action of SQL Server 2016 SP1.
- Manually install .Net Framework 3.5 on the machine.
Article ID: 3186435 - Last Review: 6 Apr 2017 - Revision: 13