BizTalk Server Setup - msdtc problem with win xp sp2, sql adapter and different sql server then local

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server Setup > November 2004 > msdtc problem with win xp sp2, sql adapter and different sql server then local





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 msdtc problem with win xp sp2, sql adapter and different sql server then local
John Smith

2004-11-15, 5:49 pm

Hello,

I have following configuration:

- win xp professional sp2
- sql server 2000 sp3a
- biztalk 2004 developer edition
- windows firewall disabled

ms dtc security settings are already set as follows:
- enabled Network DTC Access
- Allow remote clients checked
- Allow Inbound / Outbound checked
- No authentication required

After applying win xp sp2, I modified rpc settings according to
article 841893.
Biztalk server is now working ok, but there is a problem with msdtc
and sql adapter which access to sql server other then local machine.
Every message sent to different sql server results with following
message in event viewer:

The adapter "SQL" raised an error message. Details "New transaction
cannot enlist in the specified transaction coordinator.

The same orchestrations are working ok when executed from win xp sp1
machine.

msdtc trace is reporting following errors:

"transaction got begun, description : '<NULL>'"
"failed to propogate transaction to child node 'SQLServerName' because
the connection with the remote transaction manager went down"

Adding generated items using Sql adapter fails with message:
Failed to execute SQL statement. The transaction has already been
implicitly or explicitly committed or aborted.

This is probably msdtc security problem. Any advice would be
appreciated.

Thanks.
Balaji Thiagarajan

2004-11-15, 5:49 pm

This may be due to windows firewall blocked your MSDTC. You can fix it by
allowing MSDTC in your firewall settings. see this blog post for a quick fix
http://dotnetjunkies.com/WebLog/jly...8/23/23022.aspx

--
Balaji Thiagarajan
MCP (BizTalk)
http://biztalkbits.blogspot.com



"John Smith" <ng950@yahoo.com> wrote in message
news:de84550e.0411151458.4bcf3bed@posting.google.com...
> Hello,
>
> I have following configuration:
>
> - win xp professional sp2
> - sql server 2000 sp3a
> - biztalk 2004 developer edition
> - windows firewall disabled
>
> ms dtc security settings are already set as follows:
> - enabled Network DTC Access
> - Allow remote clients checked
> - Allow Inbound / Outbound checked
> - No authentication required
>
> After applying win xp sp2, I modified rpc settings according to
> article 841893.
> Biztalk server is now working ok, but there is a problem with msdtc
> and sql adapter which access to sql server other then local machine.
> Every message sent to different sql server results with following
> message in event viewer:
>
> The adapter "SQL" raised an error message. Details "New transaction
> cannot enlist in the specified transaction coordinator.
>
> The same orchestrations are working ok when executed from win xp sp1
> machine.
>
> msdtc trace is reporting following errors:
>
> "transaction got begun, description : '<NULL>'"
> "failed to propogate transaction to child node 'SQLServerName' because
> the connection with the remote transaction manager went down"
>
> Adding generated items using Sql adapter fails with message:
> Failed to execute SQL statement. The transaction has already been
> implicitly or explicitly committed or aborted.
>
> This is probably msdtc security problem. Any advice would be
> appreciated.
>
> Thanks.



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com