在 net.tcp://url 处没有侦听可以接受消息的端点。这通常是由不正确的地址或 SOAP 操作引起的

Question

我有一个使用 net.tcp 协议的 WCF 程序。它托管在 IIS 上并且曾经运行良好，但最近（我猜是在一些 windows 更新之后），客户端在尝试连接服务器时报告了以下错误消息：

Error occurs during register duplex connect service. Error msg: There was no endpoint listening at net.tcp://localhost/xxx/Duplex.svc/tcp that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

我可以在网络浏览器中成功打开“http://localhost/xxx/Duplex.svc”。事件日志中没有错误记录，net.tcp 协议已添加到我的 Web 应用程序中，net.tcp 绑定已添加到默认网站中。 net.tcp 侦听器适配器服务是运行。

我能为这个问题做点什么吗？最近有什么 windows 更新会导致这个问题吗？欢迎任何建议。

下面是我的服务器配置

<system.serviceModel>
    <bindings>
        <netTcpBinding>
            <binding name="tcpCon" closeTimeout="00:03:00" openTimeout="00:03:00" sendTimeout="00:03:00" listenBacklog="2147483647" maxBufferPoolSize="2147483647" maxBufferSize="2147483647" maxConnections="2147483647" maxReceivedMessageSize="2147483647">
                <readerQuotas maxDepth="32" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" />
                <security mode="None" />
            </binding>
        </netTcpBinding>
    </bindings>
    <services>
        <service behaviorConfiguration="ServiceBe" name="UpdateService.Duplex">
            <endpoint address="tcp" behaviorConfiguration="EndpointBe" binding="netTcpBinding" bindingConfiguration="tcpCon" name="tcp" contract="UpdateServiceInterface.IDuplex" />
            <endpoint kind="udpDiscoveryEndpoint" />
        </service>
    </services>
    <behaviors>
      <endpointBehaviors>
        <behavior name="EndpointBe">
          <endpointDiscovery>
            <scopes>
              <add scope="http://xxxxxx" />
            </scopes>
          </endpointDiscovery>
        </behavior>
      </endpointBehaviors>
      <serviceBehaviors>
        <behavior name="ServiceBe">
          <serviceDiscovery />
          <serviceMetadata httpGetEnabled="false" />
          <serviceDebug includeExceptionDetailInFaults="true" />
          <serviceThrottling maxConcurrentCalls="2147483647" maxConcurrentSessions="2147483647" maxConcurrentInstances="2147483647" />
          <dataContractSerializer maxItemsInObjectGraph="2147483647" />
        </behavior>
      </serviceBehaviors>
    </behaviors>
    <protocolMapping>
      <add binding="basicHttpsBinding" scheme="https" />
    </protocolMapping>
  </system.serviceModel>
  <system.webServer>

Answer 1

终于找到了根本原因。默认的 NetTcp 端口 808 被 Intel Graphic Driver 占用。看到这个 link.
我在Intel论坛提交了一个ticket，根据他们的回复，这个问题已经在最新的驱动程序版本中修复了。

在 net.tcp://url 处没有侦听可以接受消息的端点。这通常是由不正确的地址或 SOAP 操作引起的

There was no endpoint listening at net.tcp://url that could accept the message. This is often caused by an incorrect address or SOAP action

c#

wcf

net.tcp