Wednesday, 23 March 2011

BizTalk ESB UDDI Resolver /Static Resolver WCF-BasicHttp Adapter - ContractFilter mismatch

Last 4 hours I was hanging with below error while testing my Itinerary to send an request message to External wcf Service.Lately I found the error was due to Configuration setting at Static / Uddi Resolver.
The message with Action 'http://ExternalWCFSErvice/ManagementService/IdentiyService' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None)
In general Static resolver has Action Property Field to fill the action value for wcf service. However this has not been recognised by ESB and thrown an error below.

Fault Response

Fix is very simpley, Instead of writing Action value at action property filed, write at EndpointConfiguration.

Drop a comment if this article helped you to solve your problem
You can reach me @

Wednesday, 9 March 2011

UDDI3 TestResolver Configuration Error

I have been observing many guys facing the issue while working with UDDI resolver. One of the common error was mentioned below. This error is very generic error and it does not provide any clue for whare to fix. Hope this article might be helpful to resolve this issue quickly.
Error 1 Could not connect to service 'http://localhost/ESB.ResolverServices.WCF/ResolverService.svc' with configuration data 'UDDI3:\\searchQualifiers=andAllKeys;categorySearch=;bindingKey=uddi:esb:GetMasterOrderTransofrms;serviceKey=;'. Error message = An unexpected error occurred attempting to Resolve.Error ID = 5c17d526-d4d5-4ba3-a20f-14ecfb95366aNOTE: Alternatively you can check the Application Event log for the Error ID and on the other hand also check for the current resolver type entry in esb.config file or verify if the configuration data is correct.

All you need to is
Open your UDDI Configuration Binding Instance and add 2 custom categories like
1. BizTalk Application 2. Transport Type.

now test your UDDI Resolver , Hope you will not get above error.
Enjoy ESB::-)

You can reach me @