BizTalk Server 2013 R2 BHM toolBizTalk 2013 R2 ships with a new tool called as “BizTalk Health Monitor”. BHM is freely available for all BizTalk 2013 R2 users. More about BHM tool at BizTalkHealthMonitor
When you configure BizTalk Server 2006, BizTalk Server 2006 R2, BizTalk Server 2009, or BizTalk Server 2010, the group configuration fails and you receive the following error message:
Exception of type 'System.EnterpriseServices.TransactionProxyException' was thrown.
The installation log entry is as below:
[INFO] WMI Error occurred during database creation; attempt to rollback and delete the partially created database'croehric911\BizTalkDTADb' [INFO] WMI Calling CDataSource.Open() against SQLServerInstance\master [INFO] WMI CDataSource.Open() returned [WARN] AdminLib GetBTSMessage: hrErr=80070002; Msg=The system cannot find the file specified.; [WARN] AdminLib GetBTSMessage: hrErr=c0c02560; Msg=Failed to read "KeepDbDebugKey" from the registry.The system cannot find the file specified.; [INFO] WMI Error occurred during database creation; attempt to rollback and delete the partially created database' SQLServerInstance \BizTalkMgmtDb' [INFO] WMI Calling CDataSource.Open() against SQLServerInstance \master [INFO] WMI CDataSource.Open() returned [WARN] WMI Rollback failed. Could not delete database. [ERR] WMI Failed in pAdmInst->Create() in CWMIInstProv::PutInstance(). HR=c0c025b3 [ERR] WMI WMI error description is generated: Exception of type 'System.EnterpriseServices.TransactionProxyException' was thrown. [INFO] WMI CWMIInstProv::PutInstance() finished. HR=c0c025b3
There are a couple of ways to tackle this issue. We need to check the steps one by one.
To do this in Windows Server 2003, follow these steps:
To do this in Windows Vista, in Windows Server 2008, in Windows 7, and in Windows Server 2008 R2, follow these steps:
2. After you configure the properties page, the properties page settings resemble the settings in the following image.
3. Save the configurations, and then wait for the MSDTC service to restart.
CID for MSDTC
Check whether the CID for MSDTC is identical on the machines involved. CID for MSDTC can be the same when the servers are cloned.You need to uninstall and reinstall MSDTC in this case.
You can find the details on reinstalling MSDTC at http://blogs.msdn.com/b/distributedservices/archive/2009/04/01/instructions-to-reinstall-the-microsoft-distributed-transaction-coordinator-msdtc-service.aspx .
If possible, stop the firewall on the servers involved and try to configure BizTalk server. If this succeeds you can be sure that the issue was with the port blocking by the firewall. You can open the required ports in the firewall to solve this issue.You can find the required ports for BizTalk server at http://msdn.microsoft.com/en-us/library/aa577684(v=bts.20).aspx .
If the above steps don’t help in fixing the issue, you might need to troubleshoot the MSDTC as mentioned at http://msdn.microsoft.com/en-us/library/aa561924.aspx .
Hope this saves your time.
Written byJainath V R
Reviewed byChirag Pavecha
Microsoft India GTSC