Consider the following scenario:
- You create and deploy a Business Activity Monitoring
(BAM) activity.
- You enable the Enable routing for failed
messages option for the corresponding send port of the deployed
activity.
- You receive a message that is generated by the activity in
Microsoft BizTalk Server 2006.
- BizTalk Server 2006 processes the message. However, the send port
fails in delivering the output message.
In this scenario, the transaction for BAM is not rolled back as
expected. After
the output message is sent out, the BAM data contains two entries for the transaction instead of one entry.
Notes- One of the two entries is in the table bam_ActivityName_Active of BAMPrimaryImport database. The other entry is in the bam_ActivityName_Completed table of the BAMPrimaryImport database.
- This problem does not occur if you clear the Enable
routing for failed messages option for the send port.
This problem occurs because of an error in the BizTalk
message engine.
Hotfix information
A
supported hotfix is available from Microsoft. However, this hotfix is intended
to correct only the problemP1 that P2 described in this article. Apply this
hotfix only to systems that are experiencing the problemP1 described in this
article. 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 requirement
You do not have to restart the computer after you apply this
hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
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.
x86-based version for Microsoft BizTalk Server 2006
Collapse this tableExpand this table
| File name | File version | File
size | Date | Time | Platform |
|---|
| Btshttpreceive.dll | 3.5.1711.0 | 183,824 | 19-Sep-2007 | 20:06 | x86 |
| Btsmessageagent.dll | 3.5.1711.0 | 694,288 | 19-Sep-2007 | 20:06 | x86 |
| Btsmsg.dll | 3.5.1711.0 | 195,072 | 19-Sep-2007 | 20:06 | x86 |
| Btsmsgcore.dll | 3.5.1711.0 | 1,225,224 | 19-Sep-2007 | 20:06 | x86 |
| Microsoft.biztalk.adapter.runtime.dll | 3.5.1711.0 | 83,000 | 19-Sep-2007 | 20:06 | x86 |
| Microsoft.biztalk.epmtransform.dll | 3.5.1711.0 | 19,504 | 19-Sep-2007 | 20:06 | x86 |
| Microsoft.biztalk.globalpropertyschemas.dll | 3.5.1711.0 | 848,960 | 19-Sep-2007 | 20:06 | x86 |
| Microsoft.biztalk.interop.agent.dll | 3.5.1711.0 | 58,416 | 19-Sep-2007 | 20:06 | x86 |
| Microsoft.biztalk.streaming.dll | 3.5.1711.0 | 54,312 | 19-Sep-2007 | 20:06 | x86 |
| Microsoft.xlangs.basetypes.dll | 3.5.1711.0 | 103,464 | 19-Sep-2007 | 20:06 | x86 |
| Microsoft.xlangs.biztalk.crossprocess.dll | 3.5.1711.0 | 87,104 | 19-Sep-2007 | 20:06 | x86 |
| Microsoft.xlangs.biztalk.engine.dll | 3.5.1711.0 | 238,640 | 19-Sep-2007 | 20:06 | x86 |
| Microsoft.xlangs.biztalk.process.dll | 3.5.1711.0 | 66,608 | 19-Sep-2007 | 20:06 | x86 |
| Microsoft.xlangs.bpel.bpelom.dll | 3.5.1711.0 | 123,944 | 19-Sep-2007 | 20:06 | x86 |
| Microsoft.xlangs.bpel.bpeltranslator.dll | 3.5.1711.0 | 488,504 | 19-Sep-2007 | 20:06 | x86 |
| Microsoft.xlangs.engine.dll | 3.5.1711.0 | 259,104 | 19-Sep-2007 | 20:06 | x86 |
| Microsoft.xlangs.runtimetypes.dll | 3.5.1711.0 | 119,856 | 19-Sep-2007 | 20:06 | x86 |
| Xlangscompiler.dll | 3.5.1711.0 | 1,137,680 | 19-Sep-2007 | 20:06 | x86 |
x64-based version for Microsoft BizTalk Server 2006
Collapse this tableExpand this table
| File name | File version | File
size | Date | Time | Platform |
|---|
| Btshttpreceive.dll | 3.5.1711.0 | 289,296 | 19-Sep-2007 | 20:08 | x64 |
| Btsmessageagent.dll | 3.5.1711.0 | 1,337,872 | 19-Sep-2007 | 20:08 | x64 |
| Btsmsg.dll | 3.5.1711.0 | 195,072 | 19-Sep-2007 | 20:08 | x86 |
| Btsmsgcore.dll | 3.5.1711.0 | 1,959,944 | 19-Sep-2007 | 20:08 | x64 |
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.
For more information about how to enable routing for failed
messages, visit the following Microsoft Developer Network (MSDN) Web site:
For more information about BAM, visit the following Microsoft Web
site:
For more information about failed message routing, visit the
following Microsoft Developer Network (MSDN) Web site: