- This topic has 6 replies, 1 voice, and was last updated 8 years, 4 months ago by
.
-
Posts
-
-
I am having a slight problem with BTS2006.
I have a simple orchestration with a receive port whic is using XMLReceive pipeline.It simply gets XML file (Encoding UTF16) also tried with ANSI, UTF-8 etc.
and tries to forward it to send location. Previously all were ok even with SQL connectors, transformations etc. and all worked file, then something happened and now no message readings are succesful.All messages goes suspended (resumeable).
[b:ea3080dc23]Error is :
Reason : None of the components at Disassemble stage can recognize the data [/b:ea3080dc23]I have tried to make custom pieline also but error is the same. Also other buitIn adapters are tried.
All help would be appreciated.
-
Hello and thanks for a rapid reply.
File is valid XML file. I have tried to save it in notepad as ANSI, utf-8 and unicode which should be utf-16
As following xml header states <?xml version=\”1.0\” encoding=\”ISO-8859-1\”?> i have tried to change that also to utf16 and removed it totally etc.
error is as follows :
There was a failure executing the receive pipeline: \”Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35\” Source: \”XML disassembler\” Receive Port: \”Unload_1.0.0.0_Unload_Orchestration_Rcv_Unload_20cabe7d1842c63a\” URI: \”C:\\Receive\\UNLOAD.xml\” Reason: None of the components at Disassemble stage can recognize the data.when going to message and body message is there as it is supposed to be
<?xml version=\”1.0\” encoding=\”ISO-8859-1\”?>
<messages batch=\”3\”>
SOME XML HERE… Well formed anyway
</body>
</message>
</messages>-
Hello. Problem is now [b:106ced1d5c]solved[/b:106ced1d5c].
Actually problen was in files that bts was reading. There were no namespace definitions in files and therefore it could not be routed into proper disassembler. Problem was solved by adding namespace definition to receiving XML file. This problem occured when having more than 1 receive ports in 1 solution.
Does anyone have idea how to define correct schema by filename?
/RM
[quote:106ced1d5c=\”RM \”]I am having a slight problem with BTS2006.
I have a simple orchestration with a receive port whic is using XMLReceive pipeline.It simply gets XML file (Encoding UTF16) also tried with ANSI, UTF-8 etc.
and tries to forward it to send location. Previously all were ok even with SQL connectors, transformations etc. and all worked file, then something happened and now no message readings are succesful.All messages goes suspended (resumeable).
[b:106ced1d5c]Error is :
Reason : None of the components at Disassemble stage can recognize the data [/b:106ced1d5c]I have tried to make custom pieline also but error is the same. Also other buitIn adapters are tried.
All help would be appreciated.[/quote:106ced1d5c]
-
Hi.
Yes , if file name is unique for a certain filetype can I then define which schema should be used for file even if namespaces in xml files are missing.
\\RM
[quote:dc7dbe7952=\”greg.forsythe\”]I am not sure I understand your question:
Does anyone have idea how to define correct schema by filename?
Are you referring to how Biztalk matches an incoming message to its schema?[/quote:dc7dbe7952]
-
I have tried a number of scenarios to duplicate this error.
If you submit a text document to the XmlReceive pipeline
If you submit a UTF-16 doument without the Byte Order MarkHave you looked at the suspended message.
In Group Hub – query for suspended message
Select the service instance -> right click -> Show Messages
Select the message -> Message Details
Select BodyDo you get this error:
[quote:d62e1b8c5f]The textual representation of the data may not be accurate in this view. Use the binary tab to view the raw data. [/quote:d62e1b8c5f]Select the Binary tab and ensure the BOM, character encoding and Xml encoding definition are all in sync.
-
I am not sure I understand your question:
Does anyone have idea how to define correct schema by filename?
Are you referring to how Biztalk matches an incoming message to its schema?
-
You cannot rely on the file name to assign a schema.
Only two of the numerous adapters have a file name (FILE & FTP). All the others have no file name and numerous other protocol or application mechanisms for identifying a message.The internals of Biztalk need to be adapter agnostic, hence the use of the root node and targetnamespace to identify a message type.
You can handle documents without a target namespace, but you can only have one document with the same root node without a namespace.
i.e.
type1 = <invoice> OK
type2 = <invoice xmlns=\”namespace1\”> OK
type3 = <invoice xmlns=\”namespace2\”> OK
type4 = <invoice> this will clash with type 1This limitation is not by assembly but by Biztalk Server Group.
To delare a schema without a namespace
Open the schema
Select <Schema>
In properties window find the Target Namespace property and delete.
-
-
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.