Re: Failure executing the receive pipeline

I am building a BTS 2006 project that includes a custom pipeline (only needed to validate the incoming XML against a schema.) The schemas, orchestration, pipeline, etc are all in one project/assembly and deployed within the same application. The custom pipeline appears in the Pipelines folder under the app in the Admin console, and there is no problem with configuring the app (the receive location is bound to use the custom pipeline.)

However, at runtime I always get this error message:

There was a failure executing the receive pipeline: \"R3_DM_Movement.ReceivePipeline_XMLValidator, R3_DM_Movement, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7073308a899d0ce8\" Source: \"Unknown \" Receive Port: \"Receive_Movement\" URI: \"C:\\R3_DataMigration\\Movement\\*.xml\" Reason: Failed to get pipeline: R3_DM_Movement.ReceivePipeline_XMLValidator, R3_DM_Movement, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7073308a899d0ce8. Please verify that the pipeline strong name is correct and that the pipeline assembly is in the GAC.

If I reconfigure the port to use the XML receive pipeline, everything works fine (except the XML validation, of course) which proves that the assembly is indeed installed in the GAC.

Is there a requirement to deploy custom pipelines is their own assembly?

Any help with this would be much appreciated. :-)

Is this custom pipleline on your project, or on an external project?
I've never heard of strong naming pipelines! :? (maybe I could be missing something)

You can try and delete all DLL files rebuilding and deploying the project with a new assembly version!

You should put the custom pipeline in a seperate project, such as C# Library project. And create a strong name .snk file in the project, build it. Put the generated .dll file to GAC, can use command line or .NET Framework Configuration Tool.

And then copy the .dll file to \"your_biztalk_installation_folder\\Pipeline Component\".

Add the custom pipeline to tool box. Then you can use it freely in your biztalk project.

Just restart your host instance.

That did the trick for me! Thanks!