BizTalk Server - New transaction cannot enlist in the specified transaction coordin

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server > September 2004 > New transaction cannot enlist in the specified transaction coordin





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author New transaction cannot enlist in the specified transaction coordin
Talene

2004-08-27, 6:06 pm

I am getting this error when using Biztalk 2003 to push a file from my local
W2K3 server to a remote W2K SQL server. The local machine and the remote
machine are in two different domains. In addition, the remote machine is
within a cluster.

In chasing this issue I've come across several articles that point to DTC
and RPC issues.
http://support.microsoft.com/defaul...kb;en-us;306843
http://support.microsoft.com/default.aspx?kbid=817064
http://support.microsoft.com/defaul...kb;en-us;191168
http://support.microsoft.com/defaul...kb;en-us;827805

In following the guidelines of these articles I've done the following and
still have the same issue.
* DTC is running on both sides
* Opened TCP/IP port range 5000-5020
* Opened port 135 (EPMapper) on both ends
* Validated that ICMP is open in both directions
* Ran DTCPing and get RPC successful yet the following error appears:
Error(0x2AFC) at nameping.cpp @62
-->gethostbyaddr
-->183(Cannot create a file when that file already exists.)
* Added TurnOffRpcSecurity REG_DWORD 1 to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
DTC
Martijn Hoogendoorn

2004-08-27, 6:06 pm

On Thu, 26 Aug 2004 10:57:06 -0700, Talene wrote:

> I am getting this error when using Biztalk 2003 to push a file from my local
> W2K3 server to a remote W2K SQL server. The local machine and the remote
> machine are in two different domains. In addition, the remote machine is
> within a cluster.
>
> In chasing this issue I've come across several articles that point to DTC
> and RPC issues.
> http://support.microsoft.com/defaul...kb;en-us;306843
> http://support.microsoft.com/default.aspx?kbid=817064
> http://support.microsoft.com/defaul...kb;en-us;191168
> http://support.microsoft.com/defaul...kb;en-us;827805
>
> In following the guidelines of these articles I've done the following and
> still have the same issue.
> * DTC is running on both sides
> * Opened TCP/IP port range 5000-5020
> * Opened port 135 (EPMapper) on both ends
> * Validated that ICMP is open in both directions
> * Ran DTCPing and get RPC successful yet the following error appears:
> Error(0x2AFC) at nameping.cpp @62
> -->gethostbyaddr
> -->183(Cannot create a file when that file already exists.)
> * Added TurnOffRpcSecurity REG_DWORD 1 to
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
DTC


Hi Talene,

Do you use a linked server in any way? Looped-back linked servers do not
support DTC.

HTH,

Martijn Hoogendoorn
Bill Ticehurst [MSFT]

2004-09-02, 6:18 pm

Hi Talene,

If the remote SQL Server is a cluster on Windows 2000 you may also want to
check the KB article at
http://support.microsoft.com/defaul...KB;EN-US;290624 .

DTCPing can fail with the error you reported if the server name is greater
than 16 characters as it depends on NetBIOS name resolution. Name
resolution is probably the most common cause of these types of failures.
Is it possible to update the HOSTS / LMHOSTS files are per some of the KBs
you reference to ensure this is occurring OK?

If the above all still fails I'd recommend grabbing a network trace with
Network monitor (preferably at both ends) to see if the traffic is as
expected and if any required ports are still being blocked somewhere.

Post back with the results of any changes/tests.

Regards,

- Bill Ticehurst [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights

--------------------
| From: Martijn Hoogendoorn <martijn.hoogendoorn@macaw.nl>
| Subject: Re: New transaction cannot enlist in the specified transaction
coordin
|
| On Thu, 26 Aug 2004 10:57:06 -0700, Talene wrote:
|
| > I am getting this error when using Biztalk 2003 to push a file from my
local
| > W2K3 server to a remote W2K SQL server. The local machine and the
remote
| > machine are in two different domains. In addition, the remote machine
is
| > within a cluster.
| >
| > In chasing this issue I've come across several articles that point to
DTC
| > and RPC issues.
| > http://support.microsoft.com/defaul...kb;en-us;306843
| > http://support.microsoft.com/default.aspx?kbid=817064
| > http://support.microsoft.com/defaul...kb;en-us;191168
| > http://support.microsoft.com/defaul...kb;en-us;827805
| >
| > In following the guidelines of these articles I've done the following
and
| > still have the same issue.
| > * DTC is running on both sides
| > * Opened TCP/IP port range 5000-5020
| > * Opened port 135 (EPMapper) on both ends
| > * Validated that ICMP is open in both directions
| > * Ran DTCPing and get RPC successful yet the following error appears:
| > Error(0x2AFC) at nameping.cpp @62
| > -->gethostbyaddr
| > -->183(Cannot create a file when that file already exists.)
| > * Added TurnOffRpcSecurity REG_DWORD 1 to
| > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
DTC
|
| Hi Talene,
|
| Do you use a linked server in any way? Looped-back linked servers do not
| support DTC.
|
| HTH,
|
| Martijn Hoogendoorn
|

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com