Microsoft Knowledge Base Email Alertz

Event ID 10034 when an orchestration terminates unexpectedly in BizTalk Server 2004

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 928759 - Last Review: December 11, 2006 - Revision: 1.2

Event ID 10034 when an orchestration terminates unexpectedly in BizTalk Server 2004

SYMPTOMS

In Microsoft BizTalk Server 2004, an orchestration may terminate unexpectedly. When this issue occurs, an error message that resembles the following may be logged in the Application event log:
Event Type: Error
Event Source: XLANG/s
Event Category: None
Event ID: 10034
Description:
Uncaught exception terminated service DirectBindingTrackingIssue.BizTalk_Orchestration1
(5d96da1f-e6b1-3aba-7c56-aeb4b73beb5a), 
instance d331d248-0519-45ce-84b1-62d0c81857df

Received unexpected message type 'Microsoft.Solutions.BTARN.GlobalSchemas.LOBMessage.
Microsoft.Solutions.BTARN.GlobalSchemas, Version=3.0.0.0, Culture=neutral, 
PublicKeyToken=31bf3856ad364e35' does not match expected type 
'DirectBindingTrackingIssue.LOBMessage, DirectBindingTrackingIssue, 
Version=1.0.0.0, Culture=neutral, PublicKeyToken=c08b577ed7e23f79'.

Exception type: UnexpectedMessageTypeException
Source: Microsoft.XLANGs.Engine
Target Site: Void _verifyPublisherSchema()

CAUSE

This issue occurs if multiple assemblies contain the same schema.

WORKAROUND

To work around this issue, create the schema in one assembly. Then, reference that schema in the other projects.

STATUS

This behavior is by design.

MORE INFORMATION

When a process submits a message to the MessageBoxDb database, the message is typed with the assembly information for the assembly that contains the schema. When a different orchestration collects the message, the orchestration verifies that the type of document that it receives matches the type of document that is expected.

Therefore, you experience this issue if the following conditions are true:
  • The process that submits the message to the MessageBoxDb database uses the schema from one assembly.
  • The process that collects the message uses another assembly.

APPLIES TO
  • Microsoft BizTalk Server 2004 Standard Edition
  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Developer Edition
  • Microsoft BizTalk Server 2004 Partner Edition
Keywords: 
kbbtsorchestration kbbts kbtshoot kbprb KB928759
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate