BizTalk Server General - failure executing the receive pipeline

Author

failure executing the receive pipeline

Bob Corcoran

2005-01-04, 5:56 pm

I'm am receiving the following error when I try to run a process:

[There was a failure executing the receive pipeline:
"Microsoft.BizTalk.DefaultPipelines.XMLReceive" Source: "XML disassembler"
Receive Location: "\\Benefitsxmlone\D\BeneFix\Mapping
Tests\ReceiveHRXML\*.xml" Reason: The disassembler cannot retrieve the
document specification by using this type: "Enrollment". Either the schema is
not deployed correctly, or more than one schema is deployed for the same
message type. ]

I should add that when I run a 'Test Map' inside my project, it works fine.
The Enrollment schema is a complicated industry schema, with many includes in
it. I have included all of the referenced schemas in the project, and the
Enrollment schema does validate.

This is my first Deploy, so maybe I didn't deploy correctly. I just right
clicked on the solution and selected 'Deploy' (after building, of course)

Thanks,
Bob Corcoran

Danny Buysse

2005-01-04, 5:56 pm

Are you sure you don't have 2 schemas with hte same namespace deployed. Add a
unique namespace to the schema you'll try to receive and see what happens.

Danny Buysse.
http://dannybuysse.blogspot.com/

"Bob Corcoran" wrote:

> I'm am receiving the following error when I try to run a process:
>
> [There was a failure executing the receive pipeline:
> "Microsoft.BizTalk.DefaultPipelines.XMLReceive" Source: "XML disassembler"
> Receive Location: "\\Benefitsxmlone\D\BeneFix\Mapping
> Tests\ReceiveHRXML\*.xml" Reason: The disassembler cannot retrieve the
> document specification by using this type: "Enrollment". Either the schema is
> not deployed correctly, or more than one schema is deployed for the same
> message type. ]
>
> I should add that when I run a 'Test Map' inside my project, it works fine.
> The Enrollment schema is a complicated industry schema, with many includes in
> it. I have included all of the referenced schemas in the project, and the
> Enrollment schema does validate.
>
> This is my first Deploy, so maybe I didn't deploy correctly. I just right
> clicked on the solution and selected 'Deploy' (after building, of course)
>
> Thanks,
> Bob Corcoran

Bob Corcoran

2005-01-04, 5:56 pm

Thanks Danny. I think that might be it. But, when I try to undeploy, I get
the following error:

Some items in the removed assembly are still being used by items not defined
in the same assembly, thus removal of the assembly failed.
Make sure that items in the assembly you are trying to remove fulfill the
following conditions:
1. Pipelines, maps, and schemas are not being used by Send Ports or Receive
Locations
2. Roles have no enlisted parties.

I have stopped the receive and send ports. I'm using the default xml
pipelines. I'm not sure what else to do.

Thanks,
Bob

"Danny Buysse" wrote:
[vbcol=seagreen]
> Are you sure you don't have 2 schemas with hte same namespace deployed. Add a
> unique namespace to the schema you'll try to receive and see what happens.
>
> Danny Buysse.
> http://dannybuysse.blogspot.com/
>
> "Bob Corcoran" wrote:
>

MattBell

2005-01-04, 5:56 pm

Hi Bob,
Having just dealt with this error quite a bit, the one thing that people
have been recomending is to put your schema files into a seperate BizTalk
project. Then if you still have the problem create a receive pipeline and
specify the Document schema that you are looking for within.
See this post for more details:
http://www.traceofthought.net/Perma...e8d1b2867c.aspx

It has some good information about what causes that error.

Hope this helps
Matt Bell

"Bob Corcoran" wrote:
[vbcol=seagreen]
> Thanks Danny. I think that might be it. But, when I try to undeploy, I get
> the following error:
>
> Some items in the removed assembly are still being used by items not defined
> in the same assembly, thus removal of the assembly failed.
> Make sure that items in the assembly you are trying to remove fulfill the
> following conditions:
> 1. Pipelines, maps, and schemas are not being used by Send Ports or Receive
> Locations
> 2. Roles have no enlisted parties.
>
> I have stopped the receive and send ports. I'm using the default xml
> pipelines. I'm not sure what else to do.
>
> Thanks,
> Bob
>
>
>
>
> "Danny Buysse" wrote:
>

Danny Buysse

2005-01-04, 5:56 pm

Probably you'll have still a map or a custom pipeline on your receive or send
ports. Remove them and try again.

Danny Buysse
http://dannybuysse.blogspot.com/

"Bob Corcoran" wrote:
[vbcol=seagreen]
> Thanks Danny. I think that might be it. But, when I try to undeploy, I get
> the following error:
>
> Some items in the removed assembly are still being used by items not defined
> in the same assembly, thus removal of the assembly failed.
> Make sure that items in the assembly you are trying to remove fulfill the
> following conditions:
> 1. Pipelines, maps, and schemas are not being used by Send Ports or Receive
> Locations
> 2. Roles have no enlisted parties.
>
> I have stopped the receive and send ports. I'm using the default xml
> pipelines. I'm not sure what else to do.
>
> Thanks,
> Bob
>
>
>
>
> "Danny Buysse" wrote:
>

Bob Corcoran

2005-01-04, 5:56 pm

Thanks Matt. I guess this means I'll have to redo my maps, since the source
schema will now be in a different project?

"MattBell" wrote:
[vbcol=seagreen]
> Hi Bob,
> Having just dealt with this error quite a bit, the one thing that people
> have been recomending is to put your schema files into a seperate BizTalk
> project. Then if you still have the problem create a receive pipeline and
> specify the Document schema that you are looking for within.
> See this post for more details:
> http://www.traceofthought.net/Perma...e8d1b2867c.aspx
>
> It has some good information about what causes that error.
>
> Hope this helps
> Matt Bell
>
> "Bob Corcoran" wrote:
>

MattBell

2005-01-04, 5:56 pm

Yes, unfortunatly the maps will have to be redone. But it does make thing
easier in the long run. Also make sure that you deploy the Schema Project
when you deploy the rest of your projects. (It'll bark at you if you don't)

"Bob Corcoran" wrote:
[vbcol=seagreen]
> Thanks Matt. I guess this means I'll have to redo my maps, since the source
> schema will now be in a different project?
>
> "MattBell" wrote:
>

Bob Corcoran

2005-01-04, 5:56 pm

Matt,

I put the schema files in a separate project like you said, but the same
error message is still rearing its ugly head. So, I guess the next step is to
create a receive pipeline...does this mean I have to create a custom
component?

Thanks,
Bob

"MattBell" wrote:
[vbcol=seagreen]
> Hi Bob,
> Having just dealt with this error quite a bit, the one thing that people
> have been recomending is to put your schema files into a seperate BizTalk
> project. Then if you still have the problem create a receive pipeline and
> specify the Document schema that you are looking for within.
> See this post for more details:
> http://www.traceofthought.net/Perma...e8d1b2867c.aspx
>
> It has some good information about what causes that error.
>
> Hope this helps
> Matt Bell
>
> "Bob Corcoran" wrote:
>

Bob Corcoran

2005-01-05, 5:53 pm

MattBell

2005-01-05, 5:53 pm

No, it's actually really easy to do. In your main BizTalk project add a new
item select Receive Pipeline from the list of possible biztalk objects.
Then drop the Xml Dissassembler onto the proper place, click on it to see
the properties, then where it says xml Document, click the ... button and
select your schema from the list and hit add. Then on your recieve port, just
select your new pipeline in place of the default microsoft pipeline.

HTH Matt

"Bob Corcoran" wrote:
[vbcol=seagreen]
> Matt,
>
> I put the schema files in a separate project like you said, but the same
> error message is still rearing its ugly head. So, I guess the next step is to
> create a receive pipeline...does this mean I have to create a custom
> component?
>
> Thanks,
> Bob
>
> "MattBell" wrote:
>

Bob Corcoran

2005-01-05, 5:53 pm

Matt,

I've done this. I've also put the schema I reference in a differenct
project. I'm still getting the same error. Any thoughts?

Thanks,
Bob

"MattBell" wrote:
[vbcol=seagreen]
> No, it's actually really easy to do. In your main BizTalk project add a new
> item select Receive Pipeline from the list of possible biztalk objects.
> Then drop the Xml Dissassembler onto the proper place, click on it to see
> the properties, then where it says xml Document, click the ... button and
> select your schema from the list and hit add. Then on your recieve port, just
> select your new pipeline in place of the default microsoft pipeline.
>
> HTH Matt
>
> "Bob Corcoran" wrote:
>

MattBell

2005-01-05, 5:53 pm

Hmm, are you using an envelope?

"Bob Corcoran" wrote:
[vbcol=seagreen]
> Matt,
>
> I've done this. I've also put the schema I reference in a differenct
> project. I'm still getting the same error. Any thoughts?
>
> Thanks,
> Bob
>
> "MattBell" wrote:
>

Bob Corcoran

2005-01-05, 5:53 pm

No, I'm not usng an envelope. Should the root element in the instance
document include a reference to the local schema? Our instance documents all
reference the schema at the HR-XML site, e.g.
xsi:schemaLocation="http://ns.hr-xml.org/2004-08-02
http://ns.hr-xml.org/2_3/HR-XML-2_3.../Enrollment.xsd"

Could this be messing us up?

"MattBell" wrote:
[vbcol=seagreen]
> Hmm, are you using an envelope?
>
> "Bob Corcoran" wrote:
>

MattBell

2005-01-05, 5:53 pm

I'm not entirely certain, as I'm still fairly new to BizTalk myself. I think
this is going beyond my scope of knowledge unfortunatly. But I will point
you towards the XMLdasm.exe tool that is included in the BizTalk SDK
directory, under utilities I think. It's a straightforward tool that takes a
document and a schema and shows you what the output would be. It's much
easier to use it to debug these sorts of issues than re-deploying to BizTalk
every small change that you need to make.

Other than that I apologize for my lack of knowledge.

"Bob Corcoran" wrote:
[vbcol=seagreen]
> No, I'm not usng an envelope. Should the root element in the instance
> document include a reference to the local schema? Our instance documents all
> reference the schema at the HR-XML site, e.g.
> xsi:schemaLocation="http://ns.hr-xml.org/2004-08-02
> http://ns.hr-xml.org/2_3/HR-XML-2_3.../Enrollment.xsd"
>
> Could this be messing us up?
>
> "MattBell" wrote:
>

Bob Corcoran

2005-01-05, 5:53 pm

Thanks for your help, Matt. One possilble clue is that the schema I want to
use includes 17 other schemas, and all of these schemas show up in the Schema
Collection Property Editor. I even tried adding all of these schemas to the
collection for the pipeline; at least I get a different error when I do this

. I have the sinking feeling that after three months of development and
training with BizTalk that we are screwed. The only silver lining is that we
are still in the evaluation period for BizTalk, so at least we never paid for
any licenses.
Thanks again for your help.
regards,
Bob

"MattBell" wrote:
[vbcol=seagreen]
> I'm not entirely certain, as I'm still fairly new to BizTalk myself. I think
> this is going beyond my scope of knowledge unfortunatly. But I will point
> you towards the XMLdasm.exe tool that is included in the BizTalk SDK
> directory, under utilities I think. It's a straightforward tool that takes a
> document and a schema and shows you what the output would be. It's much
> easier to use it to debug these sorts of issues than re-deploying to BizTalk
> every small change that you need to make.
>
> Other than that I apologize for my lack of knowledge.
>
> "Bob Corcoran" wrote:
>

MattBell

2005-01-05, 5:53 pm

Have you added a web reference to your project which points to the xsd on the
remote site? That might allow your project to get better access to the
schema referenced.

"Bob Corcoran" wrote:
[vbcol=seagreen]
> Thanks for your help, Matt. One possilble clue is that the schema I want to
> use includes 17 other schemas, and all of these schemas show up in the Schema
> Collection Property Editor. I even tried adding all of these schemas to the
> collection for the pipeline; at least I get a different error when I do this
>

. I have the sinking feeling that after three months of development and
> training with BizTalk that we are screwed. The only silver lining is that we
> are still in the evaluation period for BizTalk, so at least we never paid for
> any licenses.
> Thanks again for your help.
> regards,
> Bob
>
> "MattBell" wrote:
>

Bob Corcoran

2005-01-05, 5:53 pm

Well, I may have found one problem. The root name of my monster schema was
the same as the 'type' name. Once I changed the type name to something
unique, it still didn't work, but at least I git a different error:

There was a failure executing the receive pipeline:
"EnrollmentPipeline.EnrollmentReceivePipeline" Source: "XML disassembler"
Receive Location: "\\Benefitsxmlone\D\BeneFix\Mapping
Tests\ReceiveHRXML\*.xml" Reason: Loading document specification
<HRXMLEnrollmentSchema.HRXMLEnrollment> from assembly <HRXMLEnrollmentSchema,
Version=1.0.0.0, Culture=neutral, PublicKeyToken=ec0744427cc10a6c> failed.
Verify that the schema is deployed properly and that the schema assembly
implements the document spec.

Have you seen this one?

"MattBell" wrote:
[vbcol=seagreen]
> Have you added a web reference to your project which points to the xsd on the
> remote site? That might allow your project to get better access to the
> schema referenced.
>
> "Bob Corcoran" wrote:
>

N Thorell

2005-06-29, 7:52 am

I think I have a problem because I do not make the distiction between
'namespace' and 'target namespace'. Which ones should match, and which ones
should be unique? (in a receive pipeline split (envelope) scenario)

"Danny Buysse" wrote:
[vbcol=seagreen]
> Are you sure you don't have 2 schemas with hte same namespace deployed. Add a
> unique namespace to the schema you'll try to receive and see what happens.
>
> Danny Buysse.
> http://dannybuysse.blogspot.com/
>
> "Bob Corcoran" wrote:
>