|
Home > Archive > BizTalk Server General > April 2006 > Error reading XML file through XML Receive default pipeline
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Error reading XML file through XML Receive default pipeline
|
|
| Learner 2006-04-18, 12:46 am |
| Hello there,
While using the File transport and the default XML Receive pipeline, I get
an error saying "No Disassemble stage components can recognize the data.".
The data is correct because I used the Generate Instance feature to create
it. Detail error is at the end of this message.
Any directions on how to proceed? Thank you.
Detail error message:
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:
"MyFirstOrchestration_1.0.0.0_MyFirstOrchestration. EmployeeOrchestration_RecvEmpPort_47ccec
8122e76f71"
URI: " C:\tutorial\Lessons\MyFirstIntegration\R
eceive\*.xml" Reason: No
Disassemble stage components can recognize the data.
| |
| Eric Stott 2006-04-18, 12:46 am |
| Make sure that you have deployed the schema that you used to generate the
file, and that the namespace in the xml document matches the namespace in
the schema.
Eric
http://stottcreations.com/blog
"Learner" <learner@msn.com> wrote in message
news:OfF3BeYXGHA.3444@TK2MSFTNGP05.phx.gbl...
> Hello there,
>
> While using the File transport and the default XML Receive pipeline, I get
> an error saying "No Disassemble stage components can recognize the data.".
> The data is correct because I used the Generate Instance feature to create
> it. Detail error is at the end of this message.
>
> Any directions on how to proceed? Thank you.
>
>
> Detail error message:
> 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:
> "MyFirstOrchestration_1.0.0.0_MyFirstOrchestration. EmployeeOrchestration_RecvEmpPort_47ccec
8122e76f71"
> URI: " C:\tutorial\Lessons\MyFirstIntegration\R
eceive\*.xml" Reason: No
> Disassemble stage components can recognize the data.
>
| |
| Learner 2006-04-18, 12:46 am |
| Eric,
Thanks. Schema is deployed and the namespace does match. I think I am
missing some step.
Before doing this, I tried a tutorial that shipped with BTS 2006. In that
tutorial there were some steps in which one has to specify Schema Editor
Extension=Flat File Extension and set Structure to either Positional or
Delimited. I haven't done anything like that because my input file is a XML
file. Do I need to do that?
Thanks.
Rahul
"Eric Stott" <eric@stottcreations_nospam.com> wrote in message
news:eOLErlYXGHA.1084@TK2MSFTNGP04.phx.gbl...
> Make sure that you have deployed the schema that you used to generate the
> file, and that the namespace in the xml document matches the namespace in
> the schema.
> Eric
> http://stottcreations.com/blog
>
> "Learner" <learner@msn.com> wrote in message
> news:OfF3BeYXGHA.3444@TK2MSFTNGP05.phx.gbl...
>
>
| |
| Greg Forsythe 2006-04-18, 12:46 am |
| Could be an encoding problem.
Do you have a processing instruction preceding the Xml
e.g. <?xml version="1.0" encoding="UTF-16"?>
If not you need to use UTF-8 encoding.
You may also need BOM - Byte order mark characters at the beginning of the
file
Greg
"Learner" <learner@msn.com> wrote in message
news:O7BmIVcXGHA.1476@TK2MSFTNGP03.phx.gbl...
> Eric,
>
> Thanks. Schema is deployed and the namespace does match. I think I am
> missing some step.
>
> Before doing this, I tried a tutorial that shipped with BTS 2006. In that
> tutorial there were some steps in which one has to specify Schema Editor
> Extension=Flat File Extension and set Structure to either Positional or
> Delimited. I haven't done anything like that because my input file is a
> XML file. Do I need to do that?
>
> Thanks.
>
> Rahul
>
> "Eric Stott" <eric@stottcreations_nospam.com> wrote in message
> news:eOLErlYXGHA.1084@TK2MSFTNGP04.phx.gbl...
>
>
| |
| Yakov72 2006-04-18, 12:46 am |
| Besides what Eric said I remember I had this error due to some other reason.
I can't recall the reason but it was something gross (read: stupid  ).
Like applying a different schema... or missing some basic settings in schema.
I posted this just to say that I remember I fixed it pretty quick when go
through the receiving chain.
Sorry for such indefinite post.
| |
| Learner 2006-04-18, 12:46 am |
| Greg,
That was a great suggestion. I think it indeed was an encoding problem. I
edited input files using a non-Unicode aware editor. Your email triggered a
thought. So I opened the files using Notepad and saved. That must have fixed
the encoding. After that the files were processed correctly.
Rahul
"Greg Forsythe" <greg.forsythe@gmail.com> wrote in message
news:%23uYV1qcXGHA.3972@TK2MSFTNGP04.phx.gbl...
> Could be an encoding problem.
> Do you have a processing instruction preceding the Xml
> e.g. <?xml version="1.0" encoding="UTF-16"?>
> If not you need to use UTF-8 encoding.
> You may also need BOM - Byte order mark characters at the beginning of the
> file
>
> Greg
>
> "Learner" <learner@msn.com> wrote in message
> news:O7BmIVcXGHA.1476@TK2MSFTNGP03.phx.gbl...
>
>
| |
| Learner 2006-04-18, 12:46 am |
| Yakov,
Been there and done that ;-) Almost all the time it is a user error,
otherwise it has to be a bug. If it is working for others and not for me, it
must be my mistake. And in this case it was my mistake. I used a non-Unicode
aware editor to edit the files. When I used Notepad, the files were saved
with proper encoding and the pipeline processed the files correctly.
Rahul
"Yakov72" <yakovUnderscoreKuznetsov@hotmail.com> wrote in message
news:7C18F5B8-A027-4115-9F2D-1D0C8B26AE5D@microsoft.com...
> Besides what Eric said I remember I had this error due to some other
> reason.
> I can't recall the reason but it was something gross (read: stupid ).
> Like applying a different schema... or missing some basic settings in
> schema.
> I posted this just to say that I remember I fixed it pretty quick when go
> through the receiving chain.
> Sorry for such indefinite post.
|
|
|
|
|