BizTalk Server General - New transaction cannot enlist in the specified transaction coordinator / The party cor

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server General > April 2005 > New transaction cannot enlist in the specified transaction coordinator / The party cor





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 coordinator / The party cor
Niklas E

2005-04-22, 5:58 pm

Lately we have gotten errors in the event log in one of our SQL adapter
receive location.

Anyone who has been experiencing this? Anyone has a clue what to do?

I have tried with the DTCTester and DTCPing tools which works fine and I
have tried to add "TurnOffRpcSecurity=1" in the registry. I have also tried
to update to Windows 2003 SP1 and BizTalk 2004 SP1 without any success.
After BizTalk 2004 SP1 it got even worse first, but then I found out that
BizTalk 2004 SP1 overwrites the .config file, where we use custom
AppSettings. Not so nice. So when re-adding my custom AppSettings I am
back in the same error situation.

---------
BizTalk Server 2004 [SERVERNAME]
Microsoft.BizTalk.DefaultPipelines.XMLReceive
Microsoft.BizTalk.Pipeline.Components SQL://[SQLSERVERNAME]/MDB/ There was
an authentication failure. "The party corresponding to the inbound message
cannot be identified".

BizTalk Server 2004 [SERVERNAME] SQL New transaction cannot enlist in the
specified transaction coordinator.
---------

Best regards
Niklas



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com