Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Event ID: 5724 or Event ID: 5719 occurs when you use the Base EDI Adapter in BizTalk Server 2004

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

View products that this article applies to.

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 "EDI://1234567:ZZ:1234567".
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: "Microsoft.BizTalk.DefaultPipelines.XMLReceive" Source: "Microsoft.BizTalk.Pipeline.Components" Receive Location: "EDI://1234567:ZZ:1234567" Reason: There was an authentication failure. "The party corresponding to the inbound message cannot be identified".
This issue occurs when you use party resolution together with an EDI receive location.

↑ Back to the top

Cause

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

↑ Back to the top

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.

↑ Back to the top

Status

This behavior is by design.

↑ Back to the top

More information

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.

↑ Back to the top

Keywords: KB914591, kbbtsadapters, kbprb, kbtshoot

↑ Back to the top

Article Info
Article ID : 914591
Revision : 1
Created on : 3/7/2006
Published on : 3/7/2006
Exists online : False
Views : 324