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.

FIX: A message is processed even if the delivery notification acknowledgement fails to route in Microsoft BizTalk Server 2006


View products that this article applies to.

Symptoms

In Microsoft BizTalk Server 2006, you use the delivery notification feature in a BizTalk orchestration. A delivery notification acknowledgement would be sent to the orchestration instance after the message has been sent successfully by BizTalk Server 2006. However, in some cases, the orchestration instance stops unexpectedly before the acknowledgement is sent back. When this issue occurs, the message is sent successfully, but no errors are logged even if there is no subscriber for the delivery notification acknowledgement.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have BizTalk Server 2006 installed to apply this hotfix.

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

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 item in Control Panel.
BizTalk Server 2006, x86 version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Btshttpreceive.dll3.5.1736.0183,31209-Nov-200720:47x86
Btsmessageagent.dll3.5.1736.0693,26409-Nov-200720:47x86
Btsmsg.dll3.5.1736.0195,07209-Nov-200720:47x86
Btsmsgcore.dll3.5.1736.01,224,20009-Nov-200720:47x86
Microsoft.biztalk.adapter.runtime.dll3.5.1736.083,00009-Nov-200720:47x86
Microsoft.biztalk.epmtransform.dll3.5.1736.019,50409-Nov-200720:46x86
Microsoft.biztalk.globalpropertyschemas.dll3.5.1736.0848,96009-Nov-200720:47x86
Microsoft.biztalk.interop.agent.dll3.5.1736.058,41609-Nov-200720:46x86
Microsoft.biztalk.streaming.dll3.5.1736.054,31209-Nov-200720:46x86
Microsoft.xlangs.basetypes.dll3.5.1736.099,36809-Nov-200720:47x86
Microsoft.xlangs.biztalk.crossprocess.dll3.5.1736.087,10409-Nov-200720:47x86
Microsoft.xlangs.biztalk.engine.dll3.5.1736.0238,64009-Nov-200720:47x86
Microsoft.xlangs.biztalk.process.dll3.5.1736.066,60809-Nov-200720:47x86
Microsoft.xlangs.bpel.bpelom.dll3.5.1736.0123,94409-Nov-200720:47x86
Microsoft.xlangs.bpel.bpeltranslator.dll3.5.1736.0488,50409-Nov-200720:47x86
Microsoft.xlangs.engine.dll3.5.1736.0255,00809-Nov-200720:47x86
Microsoft.xlangs.runtimetypes.dll3.5.1736.0119,85609-Nov-200720:47x86
Xlangscompiler.dll3.5.1736.01,137,68009-Nov-200720:47x86
BizTalk Server 2006, X64 version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Btshttpreceive.dll3.5.1736.0288,78409-Nov-200720:51x64
Btsmessageagent.dll3.5.1736.01,336,84809-Nov-200720:51x64
Btsmsg.dll3.5.1736.0195,07209-Nov-200720:51x86
Btsmsgcore.dll3.5.1736.01,961,99209-Nov-200720:51x64
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

After you apply this hotfix, a routing failure report message will be generated if there is no subscriber for the delivery notification acknowledgement. Additionally, the send adapter will roll back the sent message, and the message will be suspended in the message box. For more information about software update terminology, 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

↑ Back to the top


Keywords: kbautohotfix, kbbtsmessaging, kbtshoot, kbexpertiseadvanced, kbfix, kbbug, kbqfe, kbHotfixServer, kbbiztalk2006presp1fix, KB944233

↑ Back to the top

Article Info
Article ID : 944233
Revision : 3
Created on : 10/8/2011
Published on : 10/8/2011
Exists online : False
Views : 433