This article has been archived. It is offered "as is" and will no longer be updated.
You configure the following scenario in Microsoft BizTalk Server 2004:
You configure a two-way HTTP receive location.
You specify an outbound map in your BizTalk configuration.
You add a scope in your orchestration for the send shape, and you add an exception handler for a SOAP exception.
In this scenario, if you experience an error in your outbound map, an Error event is logged in the application log. This Error event indicates that the document has been suspended as you expect. However, your trading partner may still resend the original document.
This problem occurs because the exception handler for the SOAP exception is not triggered in the orchestration. Therefore, the orchestration continues as if no error occurred. When this problem occurs, Health and Activity Tracking (HAT) displays this document as having a status of "Delivered Not Consumed" instead of displaying the document as having a status of "Suspended." Because your trading partner does not receive a response document, your trading partner may resend the original document. Resending the original document causes duplicate documents to be generated.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft BizTalk Server 2004 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Because of file dependencies, you must be running BizTalk Server 2004 Service Pack 1 (SP1) to install this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
888751 How to obtain the latest BizTalk Server 2004 service pack
You must restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------------- 18-Mar-2005 01:44 3.0.6114.0 1,041,408 Btsmsgcore.dll 18-Mar-2005 02:11 3.0.6114.0 49,152 Microsoft.biztalk.messaging.dll
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates