Article ID: 944233 - Last Review: October 8, 2011 - Revision: 3.0 FIX: A message is processed even if the delivery notification acknowledgement fails to route in Microsoft BizTalk Server 2006
On This PageSYMPTOMSIn 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. RESOLUTIONHotfix informationA 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: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
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.PrerequisitesYou must have BizTalk Server 2006 installed to apply this hotfix.Restart informationYou do not have to restart the computer after you apply this hotfix.Registry informationYou do not have to change the registry.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThis 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 versionCollapse this table
BizTalk Server 2006, X64 versionCollapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. 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
(http://support.microsoft.com/kb/824684/LN/
)
Description of the standard terminology that is used to describe Microsoft software updates | Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
