Error using ESB toolkit 2.1 BizTalk 2010 Itinerary Selector pipeline component (Exception has been thrown by the target of an invocation. )

Question

Hi all,
I am using using ESB Toollkit 2.1 (NOT 2.2). and the installation and configuration happened without any error. However I am getting the below error when I use ItinerarySelectReceivePassthrough pipeline.
======================================
There was a failure executing the receive pipeline: "Microsoft.Practices.ESB.Itinerary.Pipelines.ItinerarySelectReceivePassthrough, Microsoft.Practices.ESB.Itinerary.Pipelines, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
Source: "ESB Itinerary Selector" Receive Port: "OneWay.OnRamp" URI: "C:\GOD\PROJECTS\Hoople.AdultWellbeingSolution\Testing\BusStop.2\*.txt" Reason: Exception has been thrown by the target of an invocation.
Exception has been thrown by the target of an invocation. 
Source: Microsoft.Practices.ESB.Resolver.ResolverMgr 
Method: System.Collections.Generic.Dictionary`2[System.String,System.String] Resolve(Microsoft.Practices.ESB.Resolver.ResolverInfo, Microsoft.BizTalk.Message.Interop.IBaseMessage, Microsoft.BizTalk.Component.Interop.IPipelineContext) 
Error Source: mscorlib 
Error TargetSite: System.Object InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)  
Error StackTrace:    at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)
   at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   at System.Activator.CreateInstance(Type type, Object[] args)
   at Microsoft.Practices.ESB.Resolver.ResolverFactory.Create(String key)
   at Microsoft.Practices.ESB.Resolver.ResolverMgr.GetResolver(ResolverInfo info)
   at Microsoft.Practices.ESB.Resolver.ResolverMgr.Resolve(ResolverInfo info, IBaseMessage message, IPipelineContext pipelineContext
=====================================
I looked into a thread that talked about regacing assemblies, which was marked as answered however it does not say which dlls needs to be regaced.
Please help
THANKS IN ADVANCE
Surya

Answer 1

Hi Surya,
You are getting an exception in Microsoft.Practices.ESB.Resolver.dll. which has some issues in 2.1 version for calling dynamic resolver .
You can try enabling diagnostics to see some of the trace log
Note :To enable the BizTalk ESB Toolkit trace switch, add the following <switches> element to the
system.diagnostics section of the Machine.config file.
<system.diagnostics>
<switches>
<add name="BizTalkESBToolkit" value="4"/>
</switches>
</system.diagnostics>
@Tomasso has written a great post on  this and changed some of the config setting in ESB.config.
http://www.ithero.nl/post/2013/05/12/How-to-fix-the-error-Exception-has-been-thrown-by-the-target-of-an-invocation-when-using-the-BRI-resolver-in-the-ESB-Toolkit-and-BizTalk-2013.aspx
There is also MSDN article here
https://support.microsoft.com/kb/2887594?wa=wsignin1.0
which again suggest you to modify the ESB.config file
Note: Please take a backup of existing ESB.config before modifying
Here are the settings
Manually modify the existing esb.config file as follows:1.Remove the <typeConfig> element
2.Change the <typeAlias> element to <alias>
3.Change the <type> element to <register>
4.Remove the <containers> elements
5.Remove the <types> elements
6.Remove the <typeAliases> elements
7.Remove the parameterType attribute of the <param> elements.
8.Remove the type attribute of the <value> element within <param name="overrideExistingItinerary">
Its also been well described in below BizTalk Post
https://social.msdn.microsoft.com/Forums/en-US/b92fbd9a-7c6d-4cec-b745-bf092e5e644f/esb-toolkit-22-error-in-using-the-dynamic-itinerary-resolver-bri?forum=biztalkesb
Thanks
Abhishek
As mentioned in my previous post, the fix is provided for ESB Toolkit 2.2 and not for
ESB Toolkit 2.1.
ESB Toolkit 2.2 uses Microsoft Enterprise Library 5.0 and Unity 2.0 whereas
ESB Tookit 2.1 uses Microsoft Enterprise Library 4.1 and Unity 1.2.
REFRAIN FROM DOING ANY CONFIG CHANGES WITHOUT CONSULTING MICROSOFT.
Rachit
Please mark as answer or vote as helpful if my reply does