Article ID: 890241
Article Last Modified on 11/15/2007
APPLIES TO
- 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
SYMPTOMS
When you undeploy an older version of an assembly in Microsoft BizTalk Server 2004, a newer version of the assembly may unexpectedly stop working.
CAUSE
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.
RESOLUTION
Hotfix information
A supported hotfix is now 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 service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
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.
Prerequisites
You must have Microsoft BizTalk Server 2004 Service Pack 1 (SP1) installed to apply this hotfix.
Restart requirement
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
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.
| File name | File size | Date | Time |
|---|---|---|---|
| Bts_deployment_logic.sql | 94,764 | 02-Feb-2005 | 22:19 |
| Bts_deployment_schema.sql | 33,126 | 09-Feb-2005 | 20:06 |
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
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
Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver kbbts kbbiztalk2004-2006swept KB890241
