This cumulative update for Microsoft BizTalk Server 2009 contains hotfixes for the BizTalk Server 2009 issues that were resolved after the release of BizTalk Server 2009．
We recommend that you test hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new update release contains all the hotfixes and all the security updates that were included in the previous BizTalk Server 2009 update release. We recommend that you consider applying the most recent update release that contains this hotfix.
Important notes about the cumulative update package
One cumulative hotfix package includes all the component packages. However, the cumulative update package updates only those features that are installed on the system.
Important To check whether a newer Service pack or Cumulative Update is available for BizTalk Server, click the following article number to view the article in the Microsoft Knowledge Base:
Cumulative update (CU) is a rollup update that contains all previous hotfixes to date for BizTalk Server
2009, all hotfixes from the BizTalk Server 2006 and 2006 R2 releases, and some additional new features and improvements. Some key fixes, features and improvements in this service pack are as follows:
Better reliability, performance, and scale for the following key features
HIPAA
Improved performance when opening and validating BizTalk maps in Visual Studio
Improved performance for ordered delivery orchestrations
BizTalk Server Log Shipping
BizTalk tracking
Improved support
EDI batching orchestration
HIPAA document processing
Compressed AS2 message processing
MIME or S/MIME document processing
New features
HIPAA 5010 Errata Schemas included
UI updates localized in all locales for design changes that are included in this update
Ability for BizTalk Adapter for TIBCO EMS to support ordered message delivery and SSL connections
Ability for BizTalk Adapter for TIBCO EMS to delete messages from the JMS queue with the DeleteAfterPoll registry value
Note For more information about HIPAA 5010, visit the following Microsoft Development Network (MSDN) website:
Fixed an issue in which you experience poor performance when you open a map if the schemas are from a separate project
Fixed an issue in which messages are received out of order in certain scenarios
The BizTalk Server team is testing this update model as a pilot program for BizTalk Server 2009. The future use of this update model will be based on the feedback we receive from the community.
For more information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates
BizTalk Server 2009 hotfixes that are included in Cumulative Update 2 for BizTalk Server 2009
Microsoft Knowledge Base articles that discuss these hotfixes are released as they become available. For more information about BizTalk Server bugs, click the following article numbers to view the articles in the Microsoft Knowledge Base:
Microsoft BizTalk Adapters for Enterprise Applications
FIX: Error message when you use BizTalk Adapter for PeopleSoft Enterprise to send a component interface to a PeopleSoft system: "A cross object system conversion error occurred"
658152
Not applicable
A new registry value called DeleteAfterPoll is available. The DeleteAfterPoll registry value specifies whether the messages are deleted from the JMS queue after they are successfully received by BizTalk Adapter for TIBCO EMS.
After you apply this cumulative update package on a computer that is running BizTalk Adapter for TIBCO EMS, the DeleteAfterPoll registry value is created automatically under the following registry subkey if it’s not present and set to False by default:
FIX: A hotfix is available that enables BizTalk Adapter for TIBCO EMS to support ordered message delivery and SSL connections in BizTalk Server 2006 R2 SP1 and BizTalk Server 2009
FIX: The BizTalk Server FTP adapter does not send messages and event errors occur when the FTP send port uses "QUIT" as the AfterPut command in BizTalk Server 2006 R2 or in BizTalk Server 2009
MIME or S/MIME messages that are signed or encrypted are not parsed correctly when you use the MIME/SMIME Decoder in BizTalk Server 2006 R2 or in BizTalk Server 2009
FIX: "There are multiple root elements" error when you try to export the bindings of the receive location in BizTalk Server 2009 Administration Console
FIX: The IIS worker process crashes, and MDNs are not sent to the sending party when you use the AS2EdiReceive pipeline in BizTalk Server 2006 R2 or in BizTalk Server 2009
FIX: An HIPAA 837 document is suspended unexpectedly in BizTalk Server 2006 R2 or in BizTalk Server 2009 if the "REF*G1" data element and the "REF*9F" data element are not adjacent
FIX: A valid EDIFACT message that contains a "+" character in the data element is suspended when you use the EDI receive pipeline in BizTalk Server 2006 R2 or in BizTalk Server 2009
FIX: Error message when you validate a BizTalk map in BizTalk Server 2006 R2 or in BizTalk Server 2009 if the map and its schemas are in a separate project
FIX: It takes a long time to open a BizTalk map in Microsoft Visual Studio if the schemas of the map are referenced from another BizTalk project in BizTalk Server 2006 R2 or in BizTalk Server 2009
FIX: The "BTSTask AddResource" command and the "BTSTask ListApp" command return inconsistent LUID formats in BizTalk Server 2006 R2 or in BizTalk Server 2009
FIX: A custom application stops responding when it uses the Submit adapter to submit more than 100 messages on a server that is running BizTalk Server 2006 R2 or BizTalk Server 2009
FIX: "Invalid 'id' attribute value: Duplicate ID attribute" error message when you use the XMLReceive pipeline or the XMLTransmit pipeline to receive or to send messages in BizTalk Server 2006 R2 or in BizTalk Server 2009
FIX: Messages are received out of order in ordered delivery orchestration during dehydration or rehydration in BizTalk Server 2006 R2 or in BizTalk Server 2009
FIX: SQL scheme is not updated if you rename a BizTalk Server group before you install a hotfix that updates SQL schema of BizTalk Server 2009 databases
How to obtain Cumulative Update 2 for BizTalk Server 2009
A supported cumulative update package is now available from Microsoft. However, the cumulative update package is intended to correct only the problems that are described in this article. Apply the cumulative update package only to systems that are experiencing these specific problems. This cumulative update package may receive additional testing. Therefore, if you are not severely affected by any of these problems, we recommend that you wait for the next BizTalk Server 2009 service pack. The next service pack will contain the hotfixes that are in this cumulative update package.
If the cumulative update 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 cumulative update package.
Note If additional issues occur or if any troubleshooting is required, you may 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 cumulative update package. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Website:
Note The "Hotfix Download Available" form displays the languages for which the cumulative update is available. If you do not see a certain language, no cumulative update package is available for that language.
Known issue
After you install BizTalk Server 2009 CU2, you may encounter the following known issue:
You create a BizTalk Server 2009 project in Visual Studio.
You create a receive pipeline. Then, you add the XML Disassembler pipeline component to the disassembler stage of the receive pipeline.
You select the XML Disassembler component, and then you try to configure the document schema by clicking the ellipsis next to the Document Schemas property.
In this scenario, you receive the following error message:
Invalid 'id' attribute value: Duplicate ID attribute.
To work around this issue, you can use one of the following methods:
Avoid creating a pipeline using XML Disassembler when you validate a schema.
Use the default pipeline XMLReceive, and configure its properties in BizTalk Server Administration Console following these steps: Click the ellipsis next to XMLReceive, Set property ValidateDocument to True, Set property DocumentSpecNames as Schema Name, Full Assembly Name.
Cumulative update package information
Prerequisites
To apply this update, you must have Microsoft BizTalk Server 2009 installed.
Additionally, the following feature has some corresponding hotfixes in this update. To apply the corresponding hotfixes, the component must be installed.
Microsoft BizTalk Adapters for Enterprise Applications (also known as BizTalk LOB Adapters)
If a Readme.txt file is included in this update, see the Readme.txt file for more information about how to install this update.
Note The hotfixes for Microsoft BizTalk Adapters for Enterprise Applications are included in a separate package whose name is “BizTalk LOB Adapters.”
Restart requirement
You may have to restart the computer after you apply this cumulative update.
File information
The English version of this cumulative update package 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.
For all supported x86-based versions of BizTalk Server 2009
Back to the top
