Microsoft KB Archive/938483

= FIX: BizTalk Server 2006 suspends the orchestration and logs event 10033 in the Application log when BizTalk Server 2006 detects a schema version mismatch =

Article ID: 938483

Article Last Modified on 11/15/2007

-

APPLIES TO


 * Microsoft BizTalk Server 2006 Developer Edition
 * Microsoft BizTalk Server 2006 Enterprise Edition
 * Microsoft BizTalk Server 2006 Standard Edition

-





SYMPTOMS
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

Event ID 10033

Event Type Error

Description: Uncaught exception (see the 'inner exception' below) has suspended an instance of service 'Orchestrations.RetestOrchestration(ff7eb9a1-8269-98a7-9fbb-a534d9f7bbfd)'.

The service instance will remain suspended until administratively resumed or terminated.

If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.

InstanceId: 073b1a52-cb9a-48fe-a5b3-e65c6edec00a

Shape name: Cannot get friendly name

ShapeId: eb70ee3d-798f-4cd7-8f63-e412c9cc1761

Exception thrown from: segment 1, progress 66

Inner exception: Received unexpected message type 'Schemas.Response, Schemas, Version=2.0.0.0, Culture=neutral, PublicKeyToken=0388ea5fb11d1bc1' does not match expected type 'Schemas.Response, Schemas, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0388ea5fb11d1bc1'.

Exception type: UnexpectedMessageTypeException

Source: Microsoft.XLANGs.Engine

Target Site: Void _verifyPublisherSchema

Help Link:

The following is a stack trace that identifies the location where the exception occured

at Microsoft.XLANGs.Core.XMessage._verifyPublisherSchema

at Microsoft.XLANGs.Core.XMessage.FetchProperties

at Microsoft.XLANGs.Core.XMessage.GetContentProperty(Type propType)

at Microsoft.XLANGs.Core.XMessage.GetPropertyValue(Type propType)

at Microsoft.BizTalk.XLANGs.BTXEngine.BTXMessage.GetPropertyValue(Type propType)

at Microsoft.BizTalk.XLANGs.BTXEngine.BTXMessage.GetPropertyValueThrows(Type propType)

at Orchestrations.RetestOrchestration.segment1(StopConditions stopOn)

at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)

You expect one of the following to occur when BizTalk Server detects a schema version mismatch:
 * BizTalk Server logs the event every time. BizTalk Server suspends the orchestration every time.
 * BizTalk Server never throws an exception. BizTalk Server never suspends the orchestration.



Hotfix information
Note 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 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:

http://go.microsoft.com/?linkid=6294451

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:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
You must have Microsoft BizTalk Server 2006 installed to apply this hotfix.

Restart requirement
You do not have to restart BizTalk services 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.

BizTalk Server 2006, X64 version


MORE INFORMATION
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:       </assemblyBinding>  <AppDomains WeakXsdPartValidation =&quot;true&quot;/> </Configuration> <system.runtime.remoting> <channelSinkProviders> <serverProviders> <provider id=&quot;sspi&quot; type=&quot;Microsoft.BizTalk.XLANGs.BTXEngine.SecurityServerChannelSinkProvider,Microsoft.XLANGs.BizTalk.Engine&quot; securityPackage=&quot;negotiate&quot; authenticationLevel=&quot;packetPrivacy&quot; /> </serverProviders> </channelSinkProviders> <channel ref=&quot;tcp&quot; port=&quot;0&quot; name=&quot;&quot;> <serverProviders> <provider ref=&quot;sspi&quot; /> <formatter ref=&quot;binary&quot; typeFilterLevel=&quot;Full&quot;/> </serverProviders> </system.runtime.remoting>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

Keywords: kbexpertiseinter kbhotfixserver kbqfe KB938483

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.