Share via

Configuring ESB Itinerary Selector Component in ESB , facing "Parameter cannot be NULL" error

  • Article

Hi

Well this issues bombed on me when I was preparing for a BizTalk - ESB demo  for one of the customer and again I found that the fault message was the one which really made it such a time consuming issue.

Nevertheless I thought of sharing with the community as it might just save you a couple of hours in crunch situation.

While I was configuring my "Receive Location" with the OOB pipeline "ItinerarySelectReceiveXml" , under the Resolver Component  "ESB Itinerary Selector" ,  the "Resolver Connection String" for Business Rule (Rule being used for resolving the itinerary) was specified incorrectly  with forward slash " // "instead of " \\ " which was causing the error and yes the Error message was'nt helpig me either.

There was a failure executing the receive pipeline: "Microsoft.Practices.ESB.Itinerary.Pipelines.ItinerarySelectReceiveXml, Microsoft.Practices.ESB.Itinerary.Pipelines, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "ESB Itinerary Selector" Reason: Parameter name cannot be null or an empty string. Parameter name: key

 

So simply put , correct the format to " BRI:\\ " and error would be resolved. ( I was using a Business Rules Resolver and hence I have a 'BRI' prefixed to the Connection String ,so have your connection string as per the resolver you need to use).

Keep Biztalkingggg...

 

 

Comments

  • Anonymous
    May 18, 2014
    Hi Amit,Recently I was dealing with ESB Toolkit 2.2 using BizTalk 2013. I had to use BRI to select the itinerary on the fly. But unfortunately I couldn't do it even after lot of guidance I refered online. It seems ESB Toolkit 2.2 has some bugs using the BRI Resolver. Would you please suggest me what are the key factor I need to take care while using BRI to resolve the itinerary selection. It will be great help if you could write me back at logyatso@yahoo.com.ThanksLobsang