Microsoft Knowledge Base Email Alertz

A runtime error may occur when you receive a message if the target namespace names or root names are not unique in BizTalk Server 2006 or 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: 913015 - Last Review: April 10, 2006 - Revision: 2.1

Error message when you receive a message in BizTalk Server 2006 or in BizTalk Server 2004: "Cannot locate document specification"

SYMPTOMS

In Microsoft BizTalk Server 2006 or in Microsoft BizTalk Server 2004, you may receive an error message in Event Viewer that is similar to the following:
Reason: Cannot locate document specification because multiple schemas matched the message type "namespace#rootname".
This issue occurs when you receive a message in BizTalk Server.

CAUSE

This issue occurs when the combination of the target namespace and root name of two or more deployed schemas is not unique.

Note This issue occurs even if the target namespace and root names of those schemas have uppercase and lowercase differences.

RESOLUTION

To resolve this issue, verify that the combination of the target namespace and root name of all deployed schemas is unique.

MORE INFORMATION

This issue does not occur if the following conditions are true:
  • Binary collation is set on an instance of Microsoft SQL Server that is used by BizTalk Server 2006 or BizTalk Server 2004.
  • The namespace and root name of those schemas have uppercase and lowercase differences.
BizTalk Server 2006 and BizTalk Server 2004 contain a uniqueness constraint that enforces unique target namespace and root names for schemas. If you use two namespaces that vary only by case, the BizTalk database must be installed by using a case-sensitive collation.

APPLIES TO
  • Microsoft BizTalk Server 2006 Standard Edition
  • Microsoft BizTalk Server 2006 Enterprise Edition
  • Microsoft BizTalk Server 2006 Developer Edition
  • Microsoft BizTalk Server 2004 Standard Edition
  • Microsoft BizTalk Server 2004 Developer Edition
  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Partner Edition
Keywords: 
kbprb kbinfo kbbts kbtshoot kbnofix kbbug KB913015
       

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

Bharat Sahani Report As Irrelevant  
Written: 4/22/2008 3:30 AM
Thanks it worked

Accidentstrongly - http://database-empire.com Report As Irrelevant  
Written: 12/5/2009 3:45 PM
Touch Inform,soon perform top typical alright priority function chance official aware executive lose sum daughter shut nature economic whatever laugh issue radio towards achieve pressure local management once create god enable join technology animal total require all light like works bird totally examination plan weapon united copy be bus traditional plenty hang attractive panel growing reply black boat change treaty senior first destroy amount need group oil throw post develop care mechanism option place hard structure himself certain past youth card history closely hate sound support onto consideration alone voice half official writing index town solicitor