This article has been archived. It is offered "as is" and will no longer be updated.
When you undeploy an older version of an assembly in Microsoft BizTalk Server 2004, a newer version of the assembly may unexpectedly stop working.
This problem occurs because the GUIDs for the property schema for the assembly are not updated when the newer version of the assembly is deployed. Therefore, a new property schema is not created for the newer version of the assembly. A single property schema exists for the newer version of the assembly and for the older version of the assembly. When you undeploy the older version of the assembly, the property schema is deleted. This causes the newer version of the assembly to unexpectedly stop working.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. 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.
You cannot roll back this hotfix from the BizTalk Server environment. Therefore, make sure that you fully test this hotfix in a test environment before you apply this hotfix to a production environment. Do not try to use Add or Remove Programs to remove this hotfix. This does not roll back the database changes and leaves the BizTalk Server environment in an inconsistent state.
You must have Microsoft BizTalk Server 2004 Service Pack 1 (SP1) installed to apply this hotfix.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
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.
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
When you run the SQL script that is included in this hotfix, the property GUID uniqueness requirement is removed from the BizTalkMgmtDb database. This change allows for property schema versioning and side-by-side deployment of assemblies.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Microsoft BizTalk Server 2004 Service Pack 1, Microsoft BizTalk Server 2004 Standard Edition, Microsoft BizTalk Server 2004 Partner Edition, Microsoft BizTalk Server 2004 Enterprise Edition, Microsoft BizTalk Server 2004 Developer Edition