- This topic has 2 replies, 1 voice, and was last updated 9 years, 5 months ago by
.
-
Posts
-
-
Your message is not saying that Biztalk didn’t recognize the schema, only that there are now subscribers.
All incoming messages must have a subscriber or else they are considered a useless message.
So either there should be a send port that typically has a filter that relates to either the receive port, receive location, or message type. Or there should be orchestrations that are bound to the receive location (or use direct binding and have filters in the orchestration that tie them to message).
Neal Walters
http://Biztalk-Training.com -
What pipeline are you using.
The Passthru pipeline has no components and does not attempt to identify the message.
The XMLReceive pipeline contains the XmlDisassembler which will attempt to match the incoming Xml data with a deployed schema. It uses the root node and target namespace as the message type and this should match a schema. If the schema is not found the pipeline will stop and generate an error.
If you are using flat files you need to create your own pipeline containing the Flat File Disassembler and specifying the schema that you wish to use to parse the incoming data.-
I deployed a Biztalk Server 2004 Application.When I tested it , an error occured in the pipe of the receive location.
Tracing in the HAT , I found the error information was \”Cannot find a corresponding subscription\” , and the inbound message type is \”Unparsed Interchange\”.
So since the schema was successfully deployed in the messagebox , why the Biztalk Server could not identify the message?
How to solve the problem?
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.