none
No compatible TransportManager for customBinding RRS feed

  • Question

  • Hi All

     we defined an wcf servcice,this service has two endpoints:one use tcpbinding endpoint,another use custombinding(TcpTransport enabled) endpoint.

    the config file is as below:

    <service name="OutboundHandler">
            <endpoint binding="netTcpBinding" name="OutboundHandler_NetTcp" contract="IMessageTransfer" bindingConfiguration="CISInternalNetTcpBinding"/>
            <!--Callback Service-->
            <!--<endpoint address="/EndPointHandlerCompleted" binding="netTcpContextBinding" name="OutboundHandler_CallBackAddresss" contract="ICallBackService" bindingConfiguration="CISInternalDualDuplexBinding" />-->
      <endpoint address="/EndPointHandlerCompleted" binding="customBinding" name="OutboundHandler_CallBackAddresss" contract="ICallBackService" bindingConfiguration="CISInternalDualDuplexBinding_c" />
          </service>

    <binding name="CISInternalDualDuplexBinding_c" closeTimeout="00:01:00" openTimeout="00:05:00" receiveTimeout="00:20:00" sendTimeout="00:20:00">
              <textMessageEncoding>
                <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384" maxBytesPerRead="4096" maxNameTableCharCount="16384"/>
              </textMessageEncoding>
              <tcpTransport listenBacklog="200" maxBufferSize="524288000" maxBufferPoolSize="1048576000" maxReceivedMessageSize="524288000">
                <connectionPoolSettings leaseTimeout="00:00:30"/>
              </tcpTransport>
            </binding>

    when I look the metedata in internet explorer,the below exception throws

    There is no compatible TransportManager found for URI 'net.tcp://eitinvpv200.eit.ssn.hp.com:8446/InternalOutboundHandler/OutboundHandler.xamlx/EndPointHandlerCompleted'. This may be because that you have used an absolute address which points outside of the virtual application, or the binding settings of the endpoint do not match those that have been set by other services or endpoints. Note that all bindings for the same protocol should have same settings in the same application.

    when the two endpoints both use cutombinding,this service can work.

    So I have some question: should I define two custombinding configuration? one work as nettcpbinding the other one work like nettcpcontextbinding.

     what is the difference between these configuration?

           
    Thursday, January 16, 2014 8:43 AM

Answers

  • Hi,

    >>should I define two custombinding configuration?

    Yes, you can define the two custombinding, one for the nettcpbinding, the other for the nettcpcontexbinding.

    >>what is the difference between these configuration?

    These bindings are equivalent. Custom binding is special type of binding for defining bindings which are not supported in predefined bindings (BasicHttp, WsHttp, NetTcp, ...). So there are no difference between these configuration.

    Best Regards,
    Amy Peng


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Friday, January 17, 2014 5:39 AM
    Moderator