Microsoft Knowledge Base Email Alertz

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

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 914591 - Last Review: March 7, 2006 - Revision: 1.1

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

On This Page

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.

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.

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.

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
Keywords: 
kbbtsadapters kbtshoot kbprb KB914591
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate