WCF返回错误“没有端点在net.pipe ....上侦听”

由于某些原因，我无法获取我的服务的Net.Pipe端点（EP）工作。WCF返回错误“没有端点在net.pipe ....上侦听”

这是一个在IIS7中托管的.Net 4.0 WCF服务。

有两种故障...

首先在EP将不提供元数据。
其次，EP不会真正起作用 - 我正在通过VS2010的WCF测试客户端进行测试。

我认为两者实际上都是同一个问题。

实际收到的错误是...

There was no endpoint listening at net.pipe://[machinename].[domainname]/Services/TestService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

我注意到的第一件事是，无论什么我打电话给我管道在基本解决了它被重新命名为[计算机]。[域名]这看起来很奇怪。这在输出的服务元数据中很明显。但是，如果我在测试客户端中使用我的管道名称或这个重命名的名称，那么这两者都不起作用。

我还启用了Windows功能中的WAS，为IIS中的所有协议设置站点绑定，并在IIS（http，net.tcp，net）中的“启用协议”框中键入协议名称。管）。我还检查了“Net.Pipe侦听器适配器”是否在Windows Servics中启动。

我的http和net.tcp EP的工作正常，并返回元数据。

我的配置如下 - 有谁知道什么可以阻止这个EP工作？我很确定它的简单！

<system.serviceModel> 
    <behaviors> 
     <!-- EP Behaviors --> 
     <endpointBehaviors> 
     <behavior name="PayloadMessageInspector"> 
      <MessageHeaderBehavior /> 
      <MessagePayloadBehavior /> 
     </behavior> 
     </endpointBehaviors> 
     <!-- Service Behaviors --> 
     <serviceBehaviors> 
     <behavior name="GenericServiceBehavior"> 
      <serviceDebug includeExceptionDetailInFaults="true" /> 
      <serviceMetadata httpGetEnabled="true" policyVersion="Policy15" /> 
     </behavior> 
     </serviceBehaviors> 
    </behaviors> 
    <!-- Bindings Section --> 
    <serviceHostingEnvironment multipleSiteBindingsEnabled="true" /> 
    <bindings> 
     <!-- Basic Http Binding --> 
     <basicHttpBinding> 
     <binding maxReceivedMessageSize="10485760" maxBufferSize="10485760" maxBufferPoolSize="10485760"> 
      <security mode="TransportCredentialOnly"> 
      <transport clientCredentialType="Windows" /> 
      </security> 
     </binding> 
     </basicHttpBinding> 
     <!-- Net TCP Binding --> 
     <netTcpBinding> 
     <binding maxReceivedMessageSize="10485760" maxBufferSize="10485760" maxBufferPoolSize="10485760" />   
     </netTcpBinding> 
     <!-- Net Pipe Binding --> 
     <netNamedPipeBinding> 
     <binding maxReceivedMessageSize="10485760" maxBufferSize="10485760" maxBufferPoolSize="10485760" /> 
     </netNamedPipeBinding>  
    </bindings> 
    <!-- Services Section --> 
    <services>  
     <!-- Membership Service --> 
     <service name="TestService" behaviorConfiguration="GenericServiceBehavior"> 
     <host> 
      <baseAddresses> 
      <add baseAddress="http://localhost/Services/TestService.svc" /> 
      <add baseAddress="net.tcp://localhost/Services/TestService.svc"/> 
      <add baseAddress="net.pipe://Dev/Services/TestService.svc"/> 
      </baseAddresses> 
     </host> 
     <!-- HTTP --> 
     <endpoint 
      address="" 
      binding="basicHttpBinding" 
      contract="ITestService" name="TestServiceBasicHttp" behaviorConfiguration="PayloadMessageInspector" /> 
     <!-- NetTCP --> 
     <endpoint 
      address="" 
      binding="netTcpBinding" 
      contract="ITestService" name="TestServiceNetTcp" behaviorConfiguration="PayloadMessageInspector" /> 
     <!-- NetPipe --> 
     <endpoint 
      address="" 
      binding="netNamedPipeBinding" 
      contract="ITestService" name="TestServiceNetPipe" behaviorConfiguration="PayloadMessageInspector" /> 
     <!-- Mex (Net.Tcp/Net.Pipe) --> 
     <endpoint name="TestServiceNetTcpMex" address="mex" binding="mexTcpBinding" contract="IMetadataExchange" /> 
     <endpoint name="TestServiceNetPipeMex" address="mex" binding="mexNamedPipeBinding" contract="IMetadataExchange" /> 
     </service> 
    </services> 
    <!-- Extensions --> 
    <extensions> 
     <behaviorExtensions> 
     <add name="MessageHeaderBehavior" type="ServiceMessageHeaderBehavior, TestService.Logging" /> 
     <add name="MessagePayloadBehavior" type="ServiceMessagePayloadBehavior, TestService.Logging" /> 
     </behaviorExtensions> 
    </extensions> 
    </system.serviceModel>

来源

2012-05-28 Remotec

WCF测试客户端能看到我的命名管道终点后，我增加了以下MEX终结：

通过观察测试客户端生成的配置，我发现我让我的客户的端点地址错误。这结束了我的工作...

net.pipe://localhost/{webapproot}/{path}/ServiceName.svc/{relativeaddress}

我希望这可以帮助某人。

来源

2013-02-24 02:14:22

WCF返回错误“没有端点在net.pipe ....上侦听”

回答

相关问题