FIX: BAM email alerts do not work correctly for BAM Alert service accounts in BizTalk Server 2013 R2

Consider the following scenario:

• You use Microsoft BizTalk Server 2013 R2.
• You configure the Business Activity Monitoring (BAM) Alert service to run under an account that is not the SQL Server sysadmin role.
• You configure a BAM email alert, and you configure the alert so that it can be triggered by the condition set.

In this scenario, the email alert is not sent when the email alert is triggered. Additionally, the BAM Alert messages are moved from the [bam_Metadata_Distribution] table to the [bam_Metadata_Distribution_FailedItems] table in the Alerts database.

Note If you have BAM Alerts configured, you have to manually add the BAM Alerts Service account to the DatabaseMailUserRole role.