Article ID: 938483 - View products that this article applies to.
In Microsoft BizTalk Server 2006, you use a correlated receive in a long-running orchestration. If you periodically change the schema definition, BizTalk Server detects a schema version mismatch. When BizTalk Server detects the schema version mismatch, BizTalk Server suspends the orchestration. Additionally, BizTalk Server occasionally logs the following event in the Application log:
Event Source XLANG/S
Hotfix informationNote You cannot roll back this hotfix from the BizTalk Server environment. Therefore, before you apply this hotfix to a production environment, make sure that you fully test this hotfix in a test environment. Do not use the Add or Remove Programs item in Control Panel to remove this hotfix. The Add or Remove Programs item does not roll back the database changes. Therefore, the BizTalk Server environment is left in an inconsistent state. For more information, see the Readme.txt file that is included in the hotfix package.
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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
PrerequisitesYou must have Microsoft BizTalk Server 2006 installed to apply this hotfix.
Restart requirementYou do not have to restart BizTalk services after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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.
BizTalk Server 2006, x86 version
Collapse this tableExpand this table
BizTalk Server 2006, X64 version
Collapse this tableExpand this table
After you install this hotfix, the event message occurs every time that a schema version mismatch is detected. In other words, this hotfix makes sure that the orchestration instance is suspended and an Error event is logged in the Application log every time that a schema version mismatch occurs, instead of being logged only occasionally. However, if you do not want to log the error message in BizTalk Server 2006, you can change the Btsntsvc.exe.config file to skip the unexpectedmessagetype exception.
In some long-running orchestrations that use a correlated receive mode, schema updates cannot be made. In this scenario, you can change the behavior so that orchestration instances are not always suspended when schema version mismatches are detected. We recommend that you complete all active instances or publish a new application. However, if this is not possible for an application that is already published, you can change the Btsntsvc.exe.config file so that it skips the unexpectedmessagetype exception. You must have the hotfix installed to support these configuration changes.
Note If you override the Btsntsvc.exe.config file on a BizTalk server, make sure that no schema changes are made to the published schema. If changes are made, unpredictable results can occur.
To change the Btsntsvc.exe.config file, add the following sections to the configuration element:
After you change the Btsntsvc.exe.config file, the Btsntsvc.exe.config file resembles the following section:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 938483 - Last Review: November 15, 2007 - Revision: 1.4
Contact us for more help