.net – 没有端点监听net.pipe:// localhost /

前端之家收集整理的这篇文章主要介绍了.net – 没有端点监听net.pipe:// localhost /前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。
我在 Windows Server 2003机器上的单个Windows服务中托管了两个WCF服务.如果Windows服务需要访问任何WCF服务(例如发生定时事件),则它将使用暴露的五个命名管道端点之一(不同的服务合同).该服务还会为两个服务中的每一个公开HTTP MetadataExchange端点,并为服务器外部的用户提供net.tcp端点.

通常情况下,事情会很好,但是每隔一段时间,我会收到一条像这样的错误消息:


System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.pipe://localhost/IPDailyProcessing that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException,if present,for more details. —> System.IO.PipeException: The pipe endpoint ‘net.pipe://localhost/IPDailyProcessing’ could not be found on your local machine.
— End of inner exception stack trace —

Server stack trace:
at System.ServiceModel.Channels.PipeConnectionInitiator.GetPipeName(Uri uri)
at System.ServiceModel.Channels.NamedPipeConnectionPoolRegistry.NamedPipeConnectionPool.GetPoolKey(EndpointAddress address,Uri via)
at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel,TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout,CallOnceManager cascade)
at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action,Boolean oneway,ProxyOperationRuntime operation,Object[] ins,Object[] outs,TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action,Object[] outs)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall,ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

它不会可靠地发生,这是令人生畏的,因为我不能重复,当我想.在我的Windows服务中,我也有一些定时事件和一些文件监听器,但这些事件是非常罕见的事件.有谁有任何想法为什么会遇到一个问题?任何帮助将不胜感激.

解决方法

检查“Net.Pipe监听器适配器”服务是否在服务管理控制台中运行.这被WAS用于接收任何命名管道上的请求.

猜你在找的HTML相关文章