Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 884624 - Last Review: November 16, 2007 - Revision: 1.4
BUG: You receive a "Cannot Resolve Schema Location Attribute" error message when you Import or Include schemas across different projects in BizTalk Server 2004
In Microsoft BizTalk Server 2004, when you
Import or
Include schemas from different projects, you receive an error message that is similar to the following:
Cannot Resolve Schema Location Attribute. An error occurred at (3,4)
This behavior may occur if the
Imports or the
Includes of the schema are across different assemblies and there are redundant
Imports or
Includes in the relationship. For example, with schemas A.xsd, B.xsd, and C.xsd, the following conditions are true:
- Schema B.xsd imports A.xsd.
- Schema C.xsd imports both A.xsd and B.xsd.
If these conditions are true, A.xsd is reachable through two paths. One path is through direct import of A.xsd. The other path is through the direct import of B.xsd.
Whenever this redundancy occurs and these schemas are spread over different assemblies, you receive the error message.
To work around this behavior, either break the cycle or redundancy in the schema relationships, or make sure that all the schemas are in the same project. This will cause all the schema locations to be referenced by file paths instead of assembly locations.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
For more information, visit the following Microsoft Developer Network MSDN) Web site:
APPLIES TO
- Microsoft BizTalk Server 2004 Enterprise Edition
- Microsoft BizTalk Server 2004 Developer Edition
- Microsoft BizTalk Server 2004 Partner Edition
- Microsoft BizTalk Server 2004 Standard Edition
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