- This topic has 7 replies, 1 voice, and was last updated 9 years, 1 month ago by
.
-
Posts
-
-
I have 2 application. App1 depends on AppPipe.
In Application AppPipe, i only have one custom pipeline, using "BTS.soap_encoding_1__1+anyType, Microsoft.BizTalk.GlobalPropertySchemas, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" for Flat File Disassember Document Schema.
The problem began when i try to change the pipeline, it says there's a dependency on this AppPipe, so that i cannot modify(overwrite) or delete. I undeployed the whole App1, still doesn't work, a dependency exists between the artifacts.
I redeploy everything back, then the pipeline stopped working. The error is:
There was a failure executing the receive pipeline……….Reason: unable to match the data in the input stream.
When i undeploy or deploy i will always restart the Host Instance.
What is the possible cause? I totally got lost. What a pain!
Cheers
Merry
-
Seems like something is messed up inside the pipeline. Are you using a flat file?
If so, were is the schema for the flat file located?
If not, you might want to check your pipeline. It looks like it's using the flat file disassembler.
-
Yes, the flat file schema is deployed in App1 application.
When the file is picked up, it will first go through the pipeline, with a flat file disassembler — "BTS.soap_encoding_1__1+anyType, Microsoft.BizTalk.GlobalPropertySchemas", and then then file go into an orchestration with a message defined by the schema.
The pipeline has been working fine for quite a long time, and then now just not working any more.
-
So you have a circular dependency? Not sure if that’s allowed (it isn’t in VS but BizTalk Admin is outside that domain) and at the minimum it’s not a very good idea.
Maybe move the schema to a 3rd Application or just put everything into one.
As to why it worked before, not sure. Maybe you were just luck?
-
-
No, it's not circular dependency. (Not that complicated, yet. 🙂
My main Application depends on a simple app only including a pipeline. After trying to break the dependency (but failed), the pipeline stopped working. There's a flat file dissasember with a document schema defined to using built-in Global Property Schema –"BTS.soap_encoding_1__1+anyType, Microsoft.BizTalk.GlobalPropertySche"
The error says: Unable to match the data in the input stream. Fialed to execute the flatfile disassembler.
But i didn't change any schema and the one used in pipeline is a built-in, how come have this error…..
I deleted those 2 applications and rebuild all, still no luck.
-
Your pipelines have hard coded values for the full assembly name of your schema. So, if you move the schema from one project to another or change strong name keys, you need to remove the flat file disassembler from the pipeline and re add it.
Could this be the problem? Did you change strong name keys?
-
-
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.