Developing Pipelines Components – UNC Path Error

Posted: October 16, 2009 in BizTalk
Tags: , , ,

Recently I developed a custom pipeline component, this component as a specified characteristic: it used a third part dll (provided by the client).

After successful compilation, the ALL assembly must to be put on “C:Program FilesMicrosoft BizTalk Server 2006Pipeline Components” folder (Alternative: put component dll in pipeline Components folder and the third part dll in GAC)

But, while adding the component in the VS toolbox, I was surprised with the following error:

“You have selected an invalid pipeline component assembly. Please check security settings for the assembly if you are loading it from an UNC path.”


  • First, check that your pipeline component class is public.
  • Also, make sure any assemblies you reference from the custom pipeline component are in the GAC or Pipeline Components folder (if that’s where you drop your custom pipeline component assembly).
  • Check for missing dependencies, they all have to be put on GAC or Pipeline Components folder

In my case, the dll that I try to used (that was provided by the client), I success build the solution (without error or warning) in Visual Studio, but when I checked the dll have some dependencies that wasn’t install in GAC (in my case nunit.framework.dll version

I install dependencies in GAC and solved the problem.

Tags: BizTalk | Pipeline | Components | Errors and Warnings, Causes and Solutions

  1. Anonymous says:

    if you have changed the name space of the class and you haven’t updated it with resource manager, which would be usually the first line of code , if you are using the pipeline component wizard, – this will also show you the same error

  2. Panjunath P says:

    Thanks @Anonymous, this resolved my UNC path isssue!!

  3. Rob Bowman says:

    Nice post Sandro. This is currently killing me slowly, and painfully. I’ve checked for public class, dependencies and base name passed to resource manager but still no luck. Did anyone ever discover any way to get a more descriptive error message?

    • Anonymous says:

      Check whether ‘description’ method of ‘IBaseComponent’ has been changed to return some string value.Try update the default

      “get { throw new NotImplementedException(); }” into
      get { return “Your description”; }

  4. Anonymous says:

    Move your custom pipeline component *.dll to folder C:\Program Files (x86)\Microsoft BizTalk Server 2010\Pipeline Components

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s