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.
The problem occurs because the BAM Alert service account is not added to the DatabaseMailUserRole role when you configure the BAM Alert service in BizTalk Server 2013 R2.
Cumulative update information
BizTalk Server 2013 R2
This problem was first fixed in the following cumulative update for BizTalk Server 2013 R2:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the service packs and cumulative update list for BizTalk Server, see KB 2555976: Service pack and cumulative update list for BizTalk Server.
For more information about BizTalk Server hotfixes, see KB 2003907: Information about BizTalk hotfixes and cumulative update support.