Resolving the issues you may face during BizTalk Runtime Configuration

BizTalk 2010 - Access permission issue for the machine.config file for .Net framework 4.0 

We get the following error message when you try to configure BizTalk runtime.
Error: "BizTalkMgmtDb" on server " SQLSERVERNAME ".
The type initializer for 'System.Data.SqlClient.SqlConnection' threw an exception.

Solution: When you take a process monitor trace at the time when this issue occurs, search for “Access Denied” in the result section for the below path of the machine.config file.  You can search for the System.UnauthorizedAccessException exception as well. Once you find these error, giving everyone access to C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\Machine.Config should resolve the issue.

BizTalk Runtime configuration failure when CheckNtGroupMembership API call fails

We get the following error messages when you try to configure BizTalk runtime.
Access denied. The client user must be a member of one of the following accounts to perform this function.

SSO Administrators: CSFB\bIBDnycPInvestrnBzSSORW
SSO Affiliate Administrators: CSFB\bIBDnycPInvestrnBzSSARW
Application Administrators: CSFB\cIBDnycPInvestrnBzADM
Application Users: CSFB\cIBDnycPInvestrnBzADM
Additional Data: CSFB\SysPInvestrnBzHstSvc {4C04AFDB-C314-43D0-A865-449EDF75606E} SOAP_TL_CS_AI_FAM_WorkflowInProcess

 Check group membership failed.
Group Name: CSFB\bIBDnycPInvestrnBzSSORW
Account Name: SysPInvestrnBzHstSvc
Additional Data: 644
Error Code: 0x80070005, Access is denied. 

Upon looking the config log file closely, you would find that CheckNtGroupMembership API call is failing for some reason. 

Work Around: Try to configure the runtime without creating host instance and create the host instance from BizTalk Admin Console manually.

MSDTC errors while configuring BizTalk Runtime 

We get the following MSDTC error while trying to configure BizTalk runtime           

Microsoft BizTalk Server Configuration Wizard

The Microsoft Distributed Transaction Coordinator (MSDTC) may not be configured correctly. Ensure that the MSDTC service is running and DTC network access is allowed on the BizTalk, SQL and SSO Master servers. For more information, see "MSDTC Configuration settings required for BizTalk Server" in the BizTalk Server Help.

Internal error: "New transaction cannot enlist in the specified transaction coordinator. 

Configuration Framework]Feature: [Group] Failed to configure with error message [Exception of type 'System.EnterpriseServices.TransactionProxyException' was thrown.]

Solution: For BizTalk to communicate properly with SQL via DTC, we need some MSDTC settings to be in place on both the servers. Please check out the below blog which talks about the settings which are required:

Runtime Configuration error when BizTalk Group is not configured properly
We get the following error message when BizTalk Group is not configured properly


Failed to setup database objects associated with BizTalk Host "BizTalkServerApplication" on MessageBox database server "RNOKENTUCKY\CIGINS2" / database name "BizTalkMsgBoxDb".
BizTalk Server cannot access SQL server.  This could be due to one of the following reasons:
1. Access permissions have been denied to the current user.  Either log on as a user that has been granted permissions to SQL and try again, or grant the current user permission to access SQL Server.
2. The SQL Server does not exist or an invalid database name has been specified.  Check the name entered for the SQL Server and database to make sure they are correct as provided during SQL Server installation.
3. The SQL Server exists, but is not currently running.  Use the Windows Service Control Manager or SQL Enterprise Manager to start SQL Server, and try again.
4. A SQL database file with the same name as the specified database already exists in the Microsoft SQL Server data folder.

Internal error from OLEDB provider: "Cannot open database "BizTalkMsgBoxDb" requested by the login. The login failed."

Solution:  This can happen if BizTalk Group was not configured properly and the BizTalkMsgBoxDb is missing in the SQL database. Re-Configure BizTalk group and then give it a try. It should work. 

Use of Local Group to configure multi server setup
You would also face problems with the configuration when you use local groups instead of domain groups to configure BizTalk on multi server setup.

Follow the below installation guide to get more information on the BizTalk server group setup

Note: Whenever you face an error while configuring BizTalk, after following the corrective steps close and reopen the configuration wizard to continue with configuration.

Hope this helps !!!


Written by
Yakshit Gohel

Reviewed by
Jainath V R

Microsoft India GTSC

Comments (0)

Skip to main content