Microsoft has officially released Cumulative Update Package 4 (CU4) for BizTalk Server 2009. As with all cumulative updates, this is a “rollup” package, meaning it contains all previous fixes from CU1, CU2, and CU3, plus new hotfixes.
If you are running a production environment on BizTalk 2009, applying this update is critical for long-term stability and security.
📝 One-Minute Brief
Microsoft has released Cumulative Update Package 4 (CU4) for BizTalk Server 2009. This rollup contains all hotfixes released since the initial launch, including critical fixes for the FTP adapter, WCF adapters, and EDI/AS2 runtime. It is a highly recommended update for maintaining environment stability and performance.
The cumulative update package for Microsoft BizTalk Server 2009 contains hotfixes for issues that were fixed after the release of BizTalk Server 2009.
Microsoft recommends that you test the 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. Also, is recommended that you consider applying for the most recent update release.
To know more about this CU and all Hotfixes that are included, check Microsoft Help and Support.
Prerequisites
To apply this update, you must have BizTalk Server 2009 installed.
Hotfixes that are included in this cumulative update package
- BizTalk Server EDI support: FIX: A TA1 interchange acknowledgment is not returned when you use a two-way receive port to receive EDI interchanges in BizTalk Server
- BizTalk Server Design Tools: FIX: Visual Studio crashes when you build a project in BizTalk Server 2009 if message types are classes from a referenced .NET project
- Microsoft BizTalk Server Adapters: FIX: “Error encountered while querying virtual server state for URL” error when you configure WSS adapter in BizTalk Server 2009
Restart requirement
You may have to restart the computer after you apply this cumulative update.
Known issue
After you apply this cumulative update, the settings for the DTA Purge and Archive Job roll back to default. This may cause a backlog in the BizTalk Tracking (BizTalkDTADb) database. It is recommended to reconfigure the job. For more information, visit the following Microsoft website: How to Configure the DTA Purge and Archive Job
You can download it from here: http://support.microsoft.com/kb/2604321
