Re: BizTalk 2004 MSDTC

On my Windows XP, dev machine, I set

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\TurnOffRpcSecurity = 1

and it still errors out when updating a remote SQL Server database running
on Windows 2000.

I'm still at a loss as to how to fix this.

"Tomas Restrepo (MVP)" <tomasr@xxxxxxxx> wrote in message
news:eqCrc6aDGHA.2040@xxxxxxxxxxxxxxxxxxxxxxx
> Nick,
>
>>I have a multicomputer configuration:
>> 1. BizTalk 2004 Server installed on a Windows 2003 Server
>> 2. BizTalk 2004 Server, Visual Studio.Net, and local SQL Server DB
>> installed on Windows XP
>> 3. SQL Server installed on a Windows 2000 Server
>>
>> On the #2 system, in Visual Studio.Net, I have two databases showing in
>> the BizTalk Explorer. The problem I am having is that with MSDTC
>> configured to "Use Local Coordinator", I can't manage the #3 system
>> database and with MSDTC configured to use the #3 system as the Remote
>> Host, I can't manage the local #2 database.
>>
>> I haven't found a way to manage both databases without switching the
>> MSDTC settings.
>
> You should be able to get this to work by enabling network DTC support in
> your WIndows 2003 and Windows XP machines, as well as removing
> authentication support in the DTC (the security mechanisms introduced in
> the DTC in XP SP1/2 and Windows 2003 + SP1 cause problems when connecting
> to a Win2000 machine).
>
> You can do this from the COmponent Services MMC console, by right clicking
> on the Computer node and selecting properties, then going to the MSDTC tab
> and pushing the Security Button.
>
> Here's an article that talks a little bit more about it and provides some
> pointers to try:
> http://support.microsoft.com/Default.aspx?scid=kb;en-us;839187&spid=1444&sid=21
>
>
> --
> Tomas Restrepo
> tomasr@xxxxxxxx
> http://www.winterdom.com/
>


.

Loading