Cumulative update package 1 for BizTalk Server 2009

Applies to: BizTalk Server 2009 BranchBizTalk Server 2009 DeveloperBizTalk Server 2009 Enterprise


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:
2555976 Service Pack and Cumulative Update list for BizTalk Server

More Information

Cumulative update (CU) is a rollup update that contains all previous hotfixes to date for BizTalk Server 2009.

The BizTalk Server team is using this model as a pilot and also for this specific version. The plan to apply this model is based on the feedback we received 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 1 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:

VSTS bug numberKB article numberDescription
5624092462241 FIX: Error message when you use a WSS adapter send port that enables ordered delivery option to resume failed messages in BizTalk Server 2009: 'Root element is missing'
5780422450458 FIX: Meaningless characters in a name of a hotfix for BizTalk Server 2009 when you use System Center Configuration Manager 2007 to check the hardware inventory
5100542435900 FIX: "Invalid Date" EDI interchange error occurs in BizTalk Server 2009 if a data element contains a leap date value
5657322431074 FIX: The WCF-Custom adapter does not close the connection to a WCF-based service in BizTalk Server 2009 if a WCF-based typed fault occurs
5460742406405 "<MapName.btm>: Exception Caught" error message when you try to use Visual Studio Team System 2010 TFS to build and deploy a BizTalk 2009 project that contains a map that references a schema in another project
5352572389193 FIX: Word 2007 or Word 2010 stops responding when you try to open or save a file on a computer that has BizTalk Assembly Viewer registered
5415832387313 FIX: Poor performance occurs when you use WCF-based BizTalk Adapter for Oracle Database on a dynamic port that is used by BizTalk Server 2009
5076692327918 FIX: BAM activity data is not written when you run a BizTalk application that uses a WCF-WSHttp send port in BizTalk Server 2009
5243932284013 The BizTalk WCF Service Consuming Wizard incorrectly converts a dash in the WCF Service name to an underscore in BizTalk Server 2009
5076652263355 FIX: The BizTalkDTADb database becomes very large after a BizTalk orchestration runs for a while in BizTalk Server 2009 if an exception is caught
4731402125511 FIX: A file receive location that points to a remote UNC path is disabled unexpectedly when you use BizTalk Server 2009 in Windows Vista or in Windows Server 2008
465552/5234202029078 BizTalk Server sends back an incorrect EDIFACT CONTRL acknowledgement to a trading partner
4657692028814 FIX: A BizTalk Server Group Hub page takes a long time to refresh after one node goes offline in a BizTalk 2009 and BizTalk Server 2006 R2 host clustering environment
465773981960 FIX: Changes that are made to adapter handlers are not displayed unless you restart BizTalk Server 2009 Administration Console
465760981428 FIX: You receive System.OutOfMemory exceptions or Visual Studio 2008 stops responding when you use BizTalk Server 2009 maps
465728981422 FIX: Incoming messages are not received correctly when you use the WCF-WSHttp adapter in BizTalk Server 2009
465758981327 FIX: Resource artifacts may take very long time to load in BizTalk Server 2009 Administration Console
465696980950 FIX: "xlang/s engine event log entry: Exceptions.Types.InterceptorException" error message when you run a BizTalk orchestration after you upgrade BizTalk Server 2006 R2 to BizTalk Server 2009
465735980560 FIX: "Communication with all MessageBoxes has now been re-established" entries are logged unexpectedly in the BizTalk Server 2009 Application log
465664979478 FIX: Document properties are missing when you use the WSS adapter to copy documents from one document library to another document library in BizTalk Server 2009
465751979438 FIX: You cannot deploy a BizTalk Server application in Visual Studio when the Restart Host Instances property is set to True
465643979264 FIX: A BizTalk Server 2009 receive location that uses the WCF-BasicHttp transport type does not work if the endpoint address contains an embedded space
465669979221 FIX: An EDI batching orchestration takes longer than expected to process EDI messages on a computer that is running BizTalk Server 2009
465655979153 FIX: BizTalk Server 2009 Orchestration Designer incorrectly indicates that there is an error in a BizTalk Server 2009 project
465695978796 FIX: An orphaned BizTalk DTA service instance is created unexpectedly after a BizTalk orchestration handles an exception
465524977976 FIX: Importing an .msi file or starting a BizTalk application takes a very long time or fails in BizTalk Server
465602977428 FIX: You experience various problems when you develop a BizTalk project that references another BizTalk project in Visual Studio on a computer that is running BizTalk Server 2009
465802977292 FIX: Some schemas are lost when you add a schema-based WCF Service to a BizTalk project as a service reference
465604977141 FIX: "Tracked message with id: should not exist in multiple locations" error message when you try to view message details for a tracked message event in BizTalk Server 2009
465619976927 FIX: SQL connections to BizTalk databases are not cleaned up or reused when you use the BiztalkOperations class in BizTalk Server 2006 R2 or in BizTalk Server 2009
465620976891 FIX: A file is not removed from an FTP location when you use BizTalk Server 2006 R2 or BizTalk Server 2009
465590976612 FIX: Error Message when the DTA Purge and Archive SQL Server Agent job runs on BizTalk Server: "Invalid object name 'EdiMessageContent'. [SQLSTATE 42S02] (Error 208). The step failed."
465583976554 FIX: Error message when you receive an EDI message in BizTalk Server 2009: "Duplicate Control Number"
465576976172 An error occurs when you check message flow on a completed orchestration if a BizTalk Server 2009 tracking database is hosted on a named instance of SQL Server
465574976074 FIX: Special characters are not written into the output document after they are processed by a send pipeline that uses the Flat File Assembler in BizTalk Server 2009
465617975826 FIX: Error message when you use the POP3 adapter in BizTalk Server 2006 R2 or BizTalk Server 2009: "The POP3 adapter received a response line from a server that contains more than 512 characters"
465631/519699975118 FIX: BizTalk host instances may crash with a System.OutOfMemoryException exception message in BizTalk Server
465518975020 A hotfix is available that lets you promote the GE01 segment as an EDI context property in BizTalk Server 2009
465614973901 FIX: Error message when you receive an 837 document in BizTalk Server 2006 R2 or BizTalk Server 2009: "Missing or invalid or duplicate Transaction set identifier"
465613973770 FIX: BizTalk Server 2006 or BizTalk Server 2006 R2 or BizTalk Server 2009 experiences low performance when you execute an SQL query that refers to the "ActivityID" field in the bam_ActivityName_CompletedRelationships table
465616973430 FIX: You receive a NullReferenceException exception when you use the Call Orchestration shape in BizTalk Server 2006 R2 or BizTalk Server 2009
465495973415 A hotfix is available that enables support for HIPAA 5010 standards in BizTalk Server 2009
465465973387 FIX: Error message when you receive EDI interchanges by using the EDI receive pipeline in BizTalk Server 2009: "Fatal error encountered in EDI Disassembler, error information is GetTempFileName Failed"
465476972752 FIX: You receive a load assembly error message when you publish a BizTalk orchestration as a Web service or as a WCF service in BizTalk Server 2009
552102972478 FIX: The SE Segment delimiter/terminator is missing intermittently in outgoing 997 functional acknowledgements when you send and receive EDI messages in BizTalk Server 2006 R2 or in BizTalk Server 2009
465697972196 FIX: A BizTalk host instance stops and an Event ID 5410 is logged in the Application log in BizTalk Server 2006 or in BizTalk Server 2009
540358970856 FIX: Messaging properties are not tracked for some messages in an interchange in BizTalk Server 2006 R2 or in BizTalk Server 2009
465812969558 FIX: Error message when you try to deploy BAM update when partitioning is enabled for an existing activity: "All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target lists"
465757969217 FIX: Event ID 14014 is logged in the BizTalk Server Application log and BAM Alerts are not sent as expected
465686967945 FIX: The generated XML files are much larger than expected when you try to split an EDI document that contains multiple sub-documents by using a "multiple" type schema in BizTalk Server 2006 R2 or in BizTalk Server 2009
465419967036 FIX: Binding configurations for some binding types are not saved in the WCF-Custom adapter or in the WCF-CustomIsolated adapter in BizTalk Server Administration Console
465606961724 FIX: The BizTalk 2006 or BizTalk Server 2009 FTP adapter does not retrieve a file from an FTP server when you issue the RETR command
465512957514 FIX: You may receive an error message when you try to configure the Windows SharePoint Services adapter for Office SharePoint Server 2007 in a BizTalk Server environment
465543927052 FIX: Error message when you try to enlist two orchestrations at the same time in BizTalk Server: "Value does not fall within the expected range"
658681978404 FIX: Messages are not delivered to the destination after you change the host for a send handler in BizTalk Server

How to obtain Cumulative Update 1 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.

Cumulative update package information


To apply this update, you must have Microsoft BizTalk Server 2009 installed.

Additionally, the following features have some corresponding hotfixes in this update. To apply the corresponding hotfixes, the feature must be installed.
  • Microsoft BizTalk Adapters for Enterprise Applications (also known as BizTalk LOB Adapters)
  • Microsoft BizTalk Accelerator 2009 for HL7
  • Microsoft BizTalk 2009 Accelerator for SWIFT
If a Readme.txt file is included in this update, see the Readme.txt file for more information about how to install this update.

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
File nameFile versionFile sizeDateTimePlatform
Admin_server_logic.sqlNot applicable72,83229-Nov-201014:17Not applicable
Biztalkcommon.targetsNot applicable10,68129-Nov-201014:17Not applicable
Biztalkmsgboxdbsps.sqlNot applicable57,21129-Nov-201014:17Not applicable
Bts_tracking_logic.sqlNot applicable322,09629-Nov-201014:17Not applicable
Btsedimessagecontenttables.sqlNot applicable2,07029-Nov-201014:17Not applicable
Msgbox_application_logic.sqlNot applicable529,85029-Nov-201014:17Not applicable
Msgboxlogic.sqlNot applicable570,59629-Nov-201014:17Not applicable
Biztalkmsgboxdbsps.sqlNot Applicable57,21116-Nov-201022:08Not Applicable
Microsoftedixsdtemplateskb973415.exeNot Applicable1,785,55708-Jul-200915:17x86
For all supported x64-based versions of BizTalk Server 2009
File nameFile versionFile sizeDateTimePlatform
Admin_server_logic.sqlNot applicable72,83229-Nov-201017:37Not applicable
Biztalkcommon.targetsNot applicable10,68129-Nov-201017:37Not applicable
Biztalkmsgboxdbsps.sqlNot applicable57,21129-Nov-201017:37Not applicable
Bts_tracking_logic.sqlNot applicable322,09629-Nov-201017:37Not applicable
Btsedimessagecontenttables.sqlNot applicable2,07029-Nov-201017:37Not applicable
Msgbox_application_logic.sqlNot applicable529,85029-Nov-201017:37Not applicable
Msgboxlogic.sqlNot applicable570,59629-Nov-201017:37Not applicable
Biztalkmsgboxdbsps.sqlNot Applicable57,21116-Nov-201022:08Not Applicable
Microsoftedixsdtemplateskb973415.exeNot Applicable1,785,55708-Jul-200915:17x86

Installation Instructions

Before you install the hotfix, back up the following files:
  • Microsoft.BizTalk.Edi.BaseArtifacts.dll
  • Microsoft.BizTalk.MessageCore.dll
  • Microsoft.BizTalk.Edi.Shared.dll
  • Microsoft.BizTalk.Edi.PipelineComponents.dll
  • Microsoft.BizTalk.Edi.BaseArtifacts.dll, Microsoft.BizTalk.MessageCore.dll and Microsoft.BizTalk.Edi.Shared.dll are located at <Drive:>\Program Files\Microsoft BizTalk Server 2009.
  • Microsoft.BizTalk.Edi.PipelineComponents.dll is located at <Drive:>\Program Files\Microsoft BizTalk Server 2009\Pipeline Components.
To install this hotfix, follow these steps:
  1. Extract the hotfix package, and run the Setup.exe file.
  2. In the BizTalk Server Administration Console, expand
    BizTalk Server 2009 Administration, expand BizTalk Group, expand Applications, expandBizTalk EDI Application, expandResources, and then remove the Microsoft.BizTalk.Edi.BaseArtifacts assembly from this directory.
  3. Restart the BizTalk host instance.
  4. In the same Resources directory that was mentioned in step 2, right-click
    Resources, click Add, and then click
    BizTalk Assemblies.
  5. In the Add Resources dialog box, click
    Add, and then browse to the following directory:
    <Drive:>\Program Files\Microsoft BizTalk Server 2009
  6. In this directory, double-click the Microsoft.BizTalk.Edi.BaseArtifacts.dll file.
  7. Restart the BizTalk host instance.
  8. Run the MicrosoftEdiXSDTemplatesKb973415.exe file that is in this hotfix package to self-extract the latest set of HIPAA5010-compliant schemas. Save them to the following suggested directory:
    <Drive:>\Program Files\Microsoft BizTalk Server 2009\XSD_Schema\EDI
  9. You can then follow the standard procedure for building and deploying schemas.
For more information, refer to the Readme.txt file that is contained in this hotfix package.

Important notes

  • In HIPAA 4010 schemas, elements of the X12_R type are not checked for minimum and maximum lengths. However, HIPAA 5010 guarantees that minimum and maximum lengths are checked.
  • The ST03 elements in the following schemas are not supposed to be changed because their values are used to identify the correct variant schemas:
    • 837 variants (I, P, D)
    • 277
    This is a HIPAA 5010 standard.

Known issues

  1. The design time tools have an issue when it validates batched EDI interchange for 837 message variants (I, P, D) that are included HIPAA 5010 schemas. This issue does not occur when the tools validate a non-batched EDI interchange.
  2. BizTalk tracking may stop working because the required permissions are removed in certain DTA database tables after this cumulative update package is applied. To resolve this issue, follow these steps:
    • Open BizTalk Administration Console, click to select the Allow Host Tracking option in another BizTalk Server host, and then click to clear the option in the current tracking host.
    • Restart BizTalk Server host instances.
    • Click to select the Allow Host Tracking option in another BizTalk Server host, and then click to clear the option in the current tracking host.
    • Restart the host instances to correctly apply the permissions.
  3. Some BizTalk databases may not be updated if you change the BizTalk Server group name before you apply this cumulative update package. To avoid this issue, rename the BizTalk Server group back to the following default name before you apply the update:
    BizTalk Group


For more information about BizTalk Serverhotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
2003907 Information on BizTalk Server hotfixes