Unable to send alert to Event Engine Service using named pipe.

book

Article ID: 165282

calendar_today

Updated On:

Products

Endpoint Encryption Management Platform (Formerly known as Notification Server)

Issue/Introduction

After finishing an upgrade, in this case ITMS 7.6 HF7, the following errors are noticed in the SMP logs:

Entry 1:
Unable to send alert to Event Engine Service using TCP. Send failed.
Could not connect to net.tcp://localhost:8501/Receptor. The connection attempt lasted for a time span of 00:00:02.0435738. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:8501.
[System.ServiceModel.EndpointNotFoundException @ mscorlib]

 

Entry 2:
Unable to send alert to Event Engine Service using named pipe.
The open operation did not complete within the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout.
[System.TimeoutException @ mscorlib]

Error 1:


Unable to send alert to Event Engine Service using named pipe.
The open operation did not complete within the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout.
[System.TimeoutException @ mscorlib]


Server stack trace:
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)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at System.ServiceModel.ICommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.ClientBase'1.System.ServiceModel.ICommunicationObject.Open(TimeSpan timeout)
at EventReceiver.ReceiverService.ProcessAlert(Object state)

Open timed out after 00:01:00 while establishing a transport session to net.pipe://localhost/Receptor. The time allotted to this operation may have been a portion of a longer timeout.
[System.TimeoutException @ System.ServiceModel]
at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)

Cannot connect to endpoint 'net.pipe://localhost/Receptor' within the allotted timeout of 00:00:59.8500000. The server has likely reached the MaxConnections quota and is too busy to accept new connections. The time allotted to this operation may have been a portion of a longer timeout.
[System.TimeoutException @ System.ServiceModel]
at System.ServiceModel.Channels.PipeConnectionInitiator.TryConnect(Uri remoteUri, String resolvedAddress, BackoffTimeoutHelper backoffHelper)
at System.ServiceModel.Channels.PipeConnectionInitiator.Connect(Uri remoteUri, TimeSpan timeout)
at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)

A pipe endpoint exists for '\\.\pipe\701d0573-b80c-427f-ab99-579f9e2b22f8', but the connect failed: All pipe instances are busy. (231, 0xe7)
[System.IO.PipeException @ ]

Exception logged from:
at Altiris.Diagnostics.Logging.EventLog.ReportException(Int32 severity, String strMessage, String category, Exception exception, String footer)
at EventReceiver.ReceiverService.LogException(String message, Exception e)
at EventReceiver.ReceiverService.ProcessAlert(Object state)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()

-----------------------------------------------------------------------------------------------------

Date: 5/8/2017 12:48:50 AM, Tick Count: 318577644 (3.16:29:37.6440000), Size: 3.33 KB
Process: EventReceiver (9424), Thread ID: 485, Module: EventReceiver.exe
Priority: 1, Source: EventReceiver.ReceiverService.LogException

 

 

 

Error 2:

Unable to send alert to Event Engine Service using TCP. Send failed.
Could not connect to net.tcp://localhost:8501/Receptor. The connection attempt lasted for a time span of 00:00:02.0435738. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:8501.
[System.ServiceModel.EndpointNotFoundException @ mscorlib]

Server stack trace:
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
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)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at System.ServiceModel.ICommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.ClientBase'1.System.ServiceModel.ICommunicationObject.Open(TimeSpan timeout)
at EventReceiver.ReceiverService.ProcessAlert(Object state)

No connection could be made because the target machine actively refused it 127.0.0.1:8501

[System.Net.Sockets.SocketException @ System]
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)

Exception logged from:
at Altiris.Diagnostics.Logging.EventLog.ReportException(Int32 severity, String strMessage, String category, Exception exception, String footer)
at EventReceiver.ReceiverService.LogException(String message, Exception e)
at EventReceiver.ReceiverService.ProcessAlert(Object state)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()

-----------------------------------------------------------------------------------------------------


Date: 5/8/2017 12:48:50 AM, Tick Count: 318577644 (3.16:29:37.6440000), Size: 2.78 KB
Process: EventReceiver (9424), Thread ID: 280, Module: EventReceiver.exe
Priority: 1, Source: EventReceiver.ReceiverService.LogException

Cause

Issues with the “Altiris Event Engine” service

Environment

ITMS 7.6 HF7

Resolution

Check if the “Altiris Event Engine” service is running. If it is, restart it.