There is some confusion exists between Cumulative Update and BizTalk Version.
Recently, when we have installed cumulative update 6 (CU) in our client’s BizTalk Server 2010 environment. Our client was in an assumption that this new CU would update the version details of the BizTalk server. And as part of their post installation procedure, they were looking for the BizTalk version update in Windows registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk
Server\3.0) and also in BizTalkDbVersion table in BizTalkMgmtDb database.
Many assumed that CU would update the BizTalk’s version after reading many blogs on this context.
|Product Name||Product Version Key|
|BizTalk Server 2004 SP1||3.0.6070.0|
|BizTalk Server 2004||3.0.4902.0|
|BizTalk Server 2004 SP2||3.0.7405.0|
|BizTalk Server 2006||3.5.1602.0|
|BizTalk Server 2006 R2||3.6.1404.0|
|BizTalk Server 2006 R2 SP1||3.6.1404.0|
|BizTalk Server 2009||3.9.469.0|
|BizTalk Server 2010 - Cumulative Update 1||3.9.522.2|
|BizTalk Server 2010 - Cumulative Update 2||3.9.530.2|
|BizTalk Server 2010 - Cumulative Update 3||3.9.542.2|
|BizTalk Server 2010 - Cumulative Update 4||3.9.545.2|
|BizTalk Server 2010 - Cumulative Update 5||3.9.556.2|
|BizTalk Server 2010 - Cumulative Update 6||3.9.575.2|
|BizTalk Server 2013 (RTM)||188.8.131.52|
|BizTalk Server 2013 - Cumulative Update1||3.10.301.2|
|BizTalk Server 2013 - Cumulative Update2||3.10.305.2|
But registry entry or SQL table only contains the product version not the Cumulative update version.
Also, some also assume that CU would update all the BizTalk specific assembly versions. But CU would only update engine specific assemblies (like Microsoft.XLANGs.BaseTypes, Microsoft.XLANGs.Engine will have updated version of the CU), not all assemblies’ (like Microsoft.XLANGs.RuntimeTypes, Microsoft.XLANGs.Pipeline etc) versions would have the latest version of CU.