Hi Niklas,

I think you may have turned on Authentication setting in your receive port
as one of "Required (Drop Messages)" or "Required (Keep Messages)". The
'authentication' in the recieve port setting may not be something you
think. It's related to the party resolution which is for trading partner
management mainly. The standard party resolution component used in
XMLReceive pipeline only support SID or certificate for party resolution.
Since SQL Adapter doesn't provide sender's identity using SID or
certificate, the party resolution will always fail and the party resolution
component will cancel current transaction if your receive port require
authetication of sender's identity.

Can you try changing the Authentication setting in your receive port to
"Not Required"?

Thanks,
Sunghwa

--------------------
| From: "Niklas E" <raven_tln0sp4m@hotmail.com>
| Subject: New transaction cannot enlist in the specified transaction
coordinator / The party corresponding to the inbound message cannot be
identified
| Date: Sat, 23 Apr 2005 00:55:55 +0200
| Lines: 29
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
| X-RFC2646: Format=Flowed; Original
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
| Message-ID: <ucZxy54RFHA.3560@TK2MSFTNGP14.phx.gbl>
| Newsgroups: microsoft.public.biztalk.general
| NNTP-Posting-Host: capgeminitop.capgemini.se 193.234.247.50
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.biztalk.general:13239
| X-Tomcat-NG: microsoft.public.biztalk.general
|
| 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
|
|
|
|

[ Post a follow-up to this message ]