Article ID: 839187 - Last Review: August 9, 2007 - Revision: 2.3 You receive an "A Microsoft Distributed Transaction Coordinator problem prevented connection to the Configuration database" error message when you publish assemblies from BizTalk Server 2004Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986
(http://support.microsoft.com/kb/256986/
)
Description of the Microsoft Windows registry On This PageSYMPTOMSWhen you work with a Microsoft BizTalk Server 2004 project on a Microsoft Windows Server 2003-based
computer, and you deploy the
assemblies to BizTalk Server 2004, you may receive the following error message
from Microsoft Visual Studio .NET: [Microsoft.BizTalk.Deployment.DeploymentException] Cannot open
database BizTalkMgmtDb on server [server].
[Microsoft.BizTalk.Deployment.DeploymentException] Cannot open database
BizTalkMgmtDb on server [server]. A Microsoft Distributed Transaction
Coordinator problem prevented connection to the Configuration database. The
transaction has already been implicitly or explicitly committed or aborted
The deployment wizard log file may contain the following log entries: A Microsoft
Distributed Transaction Coordinator problem prevented connection to the
Configuration database. The transaction has already been implicitly or
explicitly committed or
aborted [Microsoft.BizTalk.Deployment.DeploymentException] Cannot open database BizTalkMgmtDb on server [server]. [Microsoft.BizTalk.Deployment.DeploymentException] Cannot open database BizTalkMgmtDb on server[server]. Command failed with 3 errors and 0 warnings. All actions have been undone and no changes have been made. CAUSEThis behavior occurs because Remote Procedure Call (RPC) security requires that the computer that is running SQL Server 2000 and the BizTalk Server 2004 computer exist in the same Active Directory domain. RPC security is used for Data Transaction Coordinator (DTC) authentication between BizTalk 2004 computers. WORKAROUNDWarning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. You may also experience this problem after you install Microsoft Windows Server 2003 Service Pack 2 (SP2) or Windows Server 2003 Service Pack 1 (SP1). To work around this problem, turn off RPC security on the computers that are running Windows Server 2003. Windows Server 2003To turn off RPC security on a computer that is running Windows Server 2003 without any service packs installed, set the DWORD value of the TurnOffRpcSecurity registry value to 1. To do this, follow these steps:
Windows Server 2003 SP1 and later service packsTo turn off RPC security on a computer that is running Windows Server 2003 SP1 or a later service pack, follow these steps:
MORE INFORMATIONRPC security is a new MS DTC feature in Windows Server
2003. When you disable RPC security, the MS DTC authentication security level for
RPC calls goes back to a security level that is available in Microsoft Windows 2000
Server.
For more information about the new MS DTC functionality in Windows 2003 Service Pack 1 and in later service packs, click the following article number to view the article in the Microsoft Knowledge Base:
899191
(http://support.microsoft.com/kb/899191/
)
New functionality in the Distributed Transaction Coordinator service in Windows Server 2003 Service Pack 1 and in Windows XP Service Pack 2
For more information about BizTalk Server 2004 and SQL Server 2000 in separate domains, click the following article number to view the article in the Microsoft Knowledge Base:
827805
(http://support.microsoft.com/kb/827805/
)
BUG: MSDTC fails to mutually
authenticate when computers do not run in the same domain
| Article Translations
|
Back to the top
