asp.net – WCF – 找到了该合同的多个端点配置 – 错误

前端之家收集整理的这篇文章主要介绍了asp.net – WCF – 找到了该合同的多个端点配置 – 错误前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。
我们有工作ASP.Net Web应用程序与WCF. wcf服务作为Windows服务托管.一切皆好.然后我们进行了更改,以便服务合同将具有不同的命名空间(从Namespace1.IserviceContract到Namespace2.IserviceContract).更改后,我们部署到服务器,并在尝试实例化服务对象时收到以下错误.
System.InvalidOperationException: An endpoint configuration section for contract 'Namespace2.IserviceContract' could not be loaded because more than one endpoint configuration for that contract was found. Please indicate the preferred endpoint configuration section by name.

Generated: Fri,06 Jul 2012 21:02:56 GMT


System.Web.HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.InvalidOperationException: An endpoint configuration section for contract 'Namespace2.IserviceContract' could not be loaded because more than one endpoint configuration for that contract was found. Please indicate the preferred endpoint configuration section by name.
   at System.ServiceModel.Description.ConfigLoader.LookupChannel(String configurationName,String contractName,Boolean wildcard)
   at System.ServiceModel.Description.ConfigLoader.LoadChannelBehaviors(ServiceEndpoint serviceEndpoint,String configurationName)
   at System.ServiceModel.ChannelFactory.ApplyConfiguration(String configurationName,Configuration configuration)
   at System.ServiceModel.ChannelFactory.ApplyConfiguration(String configurationName)
   at System.ServiceModel.ChannelFactory.InitializeEndpoint(String configurationName,EndpointAddress address)
   at System.ServiceModel.ChannelFactory`1..ctor(String endpointConfigurationName,EndpointAddress remoteAddress)
   at System.ServiceModel.EndpointTrait`1.CreateSimplexFactory()
   at System.ServiceModel.EndpointTrait`1.CreateChannelFactory()
   at System.ServiceModel.ClientBase`1.CreateChannelFactoryRef(EndpointTrait`1 endpointTrait)
   at System.ServiceModel.ClientBase`1.InitializeChannelFactoryRef()
   at System.ServiceModel.ClientBase`1..ctor()
   at TestApplication.ManagementWrapper.VerifyAuthentication(Int32 appId,String Token)
   at TestApplication.VerifyAuthentication(String tokenstring)

我们对此问题进行了研究,发现如果我们的web.config文件中定义了两个客户端点,则会出现异常.但是我们确信我们只定义了一个客户端.更多此异常仅在服务器中显示.当地工程很好这里是我们的服务模式:

<system.serviceModel>
    <bindings>
      <netTcpBinding>
        <binding name="NetTcpBinding_Management" closeTimeout="00:01:00" openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00" transactionFlow="false" transferMode="Buffered" transactionProtocol="OleTransactions" hostNameComparisonMode="StrongWildcard" listenBacklog="10" maxBufferPoolSize="4194304" maxBufferSize="2147483647" maxConnections="10" maxReceivedMessageSize="2147483647">
          <readerQuotas maxDepth="32" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="32768" maxNaMetableCharCount="2147483647" />
          <reliableSession ordered="true" inactivityTimeout="00:10:00" enabled="false" />
          <security mode="None" />
        </binding>
      </netTcpBinding>
    </bindings>
    <client>
      <endpoint address="net.tcp://servername:9010/Management/service/ManagementService" binding="netTcpBinding" bindingConfiguration="NetTcpBinding_Management" contract="Namespace2.IserviceContract" name="NetTcpBinding_IserviceContract" />
    </client>
  </system.serviceModel>

我们也尝试重新启动IIS和应用程序池.仍然得到同样的例外.

解决方法

尝试搜索您的web.config另一个正在使用Web地址作为您的ManagementService.另外,在web.config中搜索对旧命名空间的任何引用(contract =“Namespace1.IserviceContract”).不要忘记检查额外的.config文件.那个小骗子以前烧了我.

猜你在找的asp.Net相关文章