Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Finding the doucment specification by message type failed
- This topic has 1 reply, 1 voice, and was last updated 9 years, 10 months ago by
community-content.
-
AuthorPosts
-
-
May 7, 2009 at 12:13 PM #22325
I’m receiving the above error, any help on this will be appreciated.
My source file (.xml file) contains the same tags as the .xsd file in my application.
Nar_BTS had suggested the following, can you please explain step by step as how to accomplish this?
1.verify your source file nameapce:http://RefillmentSchemas.Request same as sourse schema yet orch\\receive port. still problem not solved
2. create a xml disassembler and add xml disassembler yet receive location.
Thanks in advance
-
May 8, 2009 at 3:22 AM #22336
You are already using the XmlDisassembler – it is reporting the error.
When a document arrives at the XmlDisassembler it will try and find a matching schema. It does this by creating the message type from the file and looking in the BiztalkMgmtDb for a matching messagetype.
The message type is creted by concatentaing the root element namespace with the root node.
e.g.
<root>…</root> the message type is ‘root’
<ns0:root xmlns:ns0=”MyNamespace”>…</root> the message type is ‘MyNamespace#DXLawson_Journal_Entries’In your case it will check for a schema with a root node of DXLawson_Journal_Entries and no TargetNamespace.
Check you schema to see if it has a TargetNamespace if it does you can either modify you Xml message to match or delete the TargetNamespace from the schema.
One other catch, if you have two schemas deployed with the same combination of root node name and targetnamespace the Biztalk cannot decide which one to use and you will get the same error. In this case you can delete the duplicate schema assembly from Biztalk or specify the actual assembly name for the schema on the XmlDisassembler.
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.