BizTalk 2013 - BAMAlerts service crash

Question

Hi,
I am deploying BizTalk into a new clean Production environment. My topology is the following:
- 2 SQL Server machines (clustered)
- 2 BizTalk application servers (with BTS runtime)
- 1 BAM server
I have everything deployed and working well except for the BAMAlerts service crashing a minute after it starts on the BAM server.
The software installed on the BAM server is:
Windows 2008 R2 x64
SQL Server 2012 SP1 x64 with the  following features:
Reporting Services (Native)
SQL Server Data Tools
Client Tools Connectivity
Integration Services
Management Tools – Basic
Management Tools – Complete
SQL Server 2012 SP1 Cumulative Update 9
BizTalk Server 2013 x64 with the following features:
Portal Components
Business Activity Monitoring
Administrative Tools and Monitoring
Additional Software
Enterprise Single Sign-On Administration Module
Enterprise Single Sign-On Master Secret Server
BAM Alert Provider for SQL Notification Services
BAM Client
BAM-Eventing
Office Excel 2013 (x86)
Once the BizTalk binaries are installed I installed Windows Update suggested patches including  the update for BizTalk Server 2013 (KB2830546).
I then went on and configured the relevant features. Configuration worked well but the BAMAlerts service crashes 1 minute after starting with the following error:
Microsoft.BizTalk.Bam.Management.BamManagerException: Encountered error while executing command on SQL Server "". ---> System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection
to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I verified the following:
A database mail profile was created on the SQL Server instance and it works (I can use it to send emails)
Using the BAMAlerts service account I am able to connect to the SQL Server instance using Named Pipes or TCP/IP, call BizTalkMgmtDb.dbo.adm_Group_GetBAMServerAndDBName or query tables
I installed SQL Server 2005 Notification Services x64 in order to see if it helps but no success.
I installed BizTalk 2013 Cumulative Update 2 but it did no help either.
The worse part is that I hit the same issue when setting up our UAT environment, tried a number of things and ended up with a setup that works but I am not able to reproduce that success in Prod...
Following is the full error message:
Microsoft.BizTalk.Bam.Management.BamManagerException: Encountered error while executing command on SQL Server "". ---> System.Data.SqlClient.SqlException:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.BizTalk.Bam.Management.SqlHelper.ExecuteQuery(String cmdText, CommandType cmdType, Transaction transaction)
--- End of inner exception stack trace ---
at Microsoft.BizTalk.Bam.Management.SqlHelper.ExecuteQuery(String cmdText, CommandType cmdType, Transaction transaction)
at Microsoft.BizTalk.Bam.AlertHost.AlertHost.Run()
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
Thanks
Emmanuel

Answer 1

Known issue, you need BizTalk Server 2013 CU1:
http://support.microsoft.com/kb/2838133/en-us
(See hotfix 2832137)
Morten la Cour