Pages

BizTalk 2010 WCF Custom Adapter Error : Unable to create binding configuration element for editing. Check the values of the bindyingType and BindingConfiguration properties.

Wednesday, August 31, 2011

Q: 
I have a project that was tested and is working fine in dev. I have exported it from dev and imported it to the production successfully (or at least the I had the impression that it was successful as BizTalk message said so). The project polled a record from Oracle db and does some transformation. We have one test and one production Oracle database. Since it is now in production, I want BizTalk to poll record from the production database and therefore went in the Receive port to configure the database. However, I can not do so as I got this message:
"Unable to create binding configuration element for editing. Check the values of the bindyingType and BindingConfiguration properties. (Microsoft.BizTalk.Adapter.Wcf.Converters.CreateBindingException) Unable to get binding type for binding extension "string". Verify the binding extersion is registered in the machine .config."
Please advise how to solve the issue? I used the import/export MSI to get and put from dev to the production.

Possible Sol 1 :
This error means that custom binding extension for a WCF-Custom or a WCF-CustomIsolated transport was not configured properly. To resolve this error do one or more of the following:
  • Ensure the machine.config file in %WinDir%\Microsoft.NET\Framework\v4.0.30319\Config has the <bindingExtensions> element configured properly.
  • In Windows Explorer, go to %WinDir%\Assembly, and make sure the assemblies implementing the custom binding extension are installed properly.
  • For the WCF-Custom adapter, in the BizTalk Administration console, restart the host instance running the WCF transport.
  • For the WCF-CustomIsolated adapter, in the IIS Management console, restart the application pool hosting the WCF transport.
  • Open and close the BizTalk Administration console if it was opened.
    If you do not have binding for WCF-Custom or WCF-CustomIsolated than first point (machine.config) still applies.
    HTH

    No comments:

    Post a Comment

    Post Your Comment...