Business Process Integration

I received the message in the EventLog: Value cannot be null. Parameter name: binding

xlang/s engine event log entry: Uncaught exception (see the ‘inner exception’ below) has suspended an instance of service ‘project.orchestration(782dca1d-7bf7-acae-1545-cb3861ca1a3b)’.
The service instance will remain suspended until administratively resumed or terminated.
If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
InstanceId: 3404f012-f181-4e83-8d45-d9537f40a712
Shape name: ConstructMessage_1
ShapeId: 52a16d91-9de3-494b-8f43-a9a8f0459371
Exception thrown from: segment 1, progress 25
Inner exception: Value cannot be null.
Parameter name: binding
Exception type: ArgumentNullException
Source: Microsoft.Practices.ESB.Resolver.UDDI3
Target Site: Void ExtractBindingCategoryInfo(Microsoft.Practices.ESB.UDDI3.categoryBag, System.String, System.Collections.Generic.Dictionary`2[System.String,System.String])
The following is a stack trace that identifies the location where the exception occured

   at Microsoft.Practices.ESB.Resolver.UDDI3.ResolveProvider.ExtractBindingCategoryInfo(categoryBag categoryBag, String keyPrefix, Dictionary`2 uddiValues)
   at Microsoft.Practices.ESB.Resolver.UDDI3.ResolveProvider.ResolveUddi(String config, String resolver, String keyPrefix, Dictionary`2 resolutionOrig)
   at Microsoft.Practices.ESB.Resolver.UDDI3.ResolveProvider.Resolve(ResolverInfo resolverInfo, XLANGMessage message)
   at Microsoft.Practices.ESB.Resolver.ResolverMgr.Resolve(ResolverInfo info, XLANGMessage message)
   at Microsoft.Practices.ESB.Resolver.ResolverMgr.Resolve(XLANGMessage message, String config)
   at Microsoft.Practices.ESB.Itinerary.OM.V1.ItineraryV1.Advance(XLANGMessage message, IItineraryStep step)
   at BTAHL7Schemas.ChangeHL7.segment1(StopConditions stopOn)
   at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I ran into this problem earlier, see one of my old posts about manually configuring UDDI. In my case I forgot to enter the Category information for the UDDI service in the tab Categories: