Microsoft KB Archive/914591

= Event ID: 5724 or Event ID: 5719 occurs when you use the Base EDI Adapter in BizTalk Server 2004 =

Article ID: 914591

Article Last Modified on 3/7/2006

-

APPLIES TO


 * Microsoft BizTalk Server 2004 Standard Edition
 * Microsoft BizTalk Server 2004 Developer Edition
 * Microsoft BizTalk Server 2004 Enterprise Edition
 * Microsoft BizTalk Server 2004 Partner Edition

-





SYMPTOMS
When you use the Microsoft BizTalk Server 2004 Base EDI Adapter in Microsoft BizTalk Server 2004, you may receive an error message that is similar to one of the following error messages:

Error message 1

Event Type: Error

Event Source: BizTalk Server 2004

Event Category: BizTalk Server 2004

Event ID: 5724

Description:

The Messaging Engine is dropping the message due to authentication failure. The message came from Receive Location URL &quot;EDI://1234567:ZZ:1234567&quot;.

Error message 2

Event Type: Error

Event Source: BizTalk Server 2004

Event Category: BizTalk Server 2004

Event ID: 5719

Description:

There was a failure executing the receive pipeline: &quot;Microsoft.BizTalk.DefaultPipelines.XMLReceive&quot; Source: &quot;Microsoft.BizTalk.Pipeline.Components&quot; Receive Location: &quot;EDI://1234567:ZZ:1234567&quot; Reason: There was an authentication failure. &quot;The party corresponding to the inbound message cannot be identified&quot;.

This issue occurs when you use party resolution together with an EDI receive location.



CAUSE
This issue occurs because the BizTalk Server 2004 Base EDI Adapter does not support party resolution.



RESOLUTION
To determine the inbound party of an EDI receive location in BizTalk Server 2004, create a custom application that uses the InboundTransportLocation context property to verify the URI value. Then, you can use the ExplorerOM object model to enumerate through the parties to find the party that has an EDI qualifier value that is the same value as the InboundTransportLocation property value. This custom application can be called within a BizTalk Server pipeline component or an orchestration.



STATUS
This behavior is by design.



Steps to reproduce the behavior

 * 1) Create an EDI receive location that uses the default XMLReceive pipeline. The default XMLReceive pipeline contains a party resolution component.
 * 2) Set the Authentication property for the receive port to Required.
 * 3) Drop an EDI file in the receive location.

Keywords: kbtshoot kbprb kbbtsadapters KB914591

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.