Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

How to Ensure that the recipient 'ServiceDirectory' on endpoint '' [local] is running?

Hi All,

I wonder what type of object is this below when I got this error and the suggestion to fix it?

TITLE: Ping all registered message subscribers (Agent Infrastructure)
DISCOVERED: 20/10/2020 12:16:10 PM
RESOLUTION: Ensure that the recipient 'ServiceDirectory' on endpoint '1ab2116f-1ab2116f' [local] is running.
DESCRIPTION: Pinging recipient 'ServiceDirectory' on endpoint '1ab2116f-1ab2116f' [local] has failed because no response was received in the defined timeout 15000 ms.

This message was generated when going through the Orion Health Checks.

Find more posts tagged with

Accepted answers

akhasheni

Heard back from Support on this (case 00668144):

We are writing to inform you that we are closing this case. Our Engineering team are currently unable to implement a fix for your issue at this time. You can check back on the status of SAM-12484 in the future to get a status update on when the fix will be available.

All comments

amoss24

I have a similar issue to this - wondering what the troubleshooting steps look like. I tried searching our AD for the GUID that is listed using get-adobject but there does not seem to be anything that matches.

akhasheni

Same here:

Ping all registered message subscribers

Pinging recipient 'ADM' on endpoint 'd4beb8b9-6689-4399-b3ff-80fde796d471' [local] has failed because of the error: DeliveryFailedPing message received:The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it has been Aborted.

What you can do
Ensure that the recipient 'ADM' on endpoint 'd4beb8b9-6689-4399-b3ff-80fde796d471' [local] is running.

mikeba

Our organization just applied the latest security updates due to the December 2020 supply chain attack (Orion Platform version 2020.2.1 HF 1) and we're seeing this similar error now.

Pinging recipient 'ADM' on endpoint '522fbb57-<full guid removed by me>' [local] has failed because of the error: DeliveryFailedPing message received:The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it has been Aborted.

 Pinging recipient 'ServiceDirectory' on endpoint '522fbb57-<full guid removed by me>' [local] has failed because no response was received in the defined timeout 15000 ms.

What you can do

Ensure that the recipient 'ADM' on endpoint '522fbb57-<full guid removed by me>' [local] is running.

Ensure that the recipient 'ServiceDirectory' on endpoint '522fbb57-<full guid removed by me>' [local] is running.

itengineer

Yes, me too, looks like this is an ongoing issue that is left forgotten by the Solarwinds Support team.

if anyone know how to fix it, please share it here.

akhasheni

Heard back from Support on this (case 00668144):

We are writing to inform you that we are closing this case. Our Engineering team are currently unable to implement a fix for your issue at this time. You can check back on the status of SAM-12484 in the future to get a status update on when the fix will be available.

itengineer

Thanks for sharing @akhasheni I thought so.

FirstTimeCaller

I am also seeing this error after applying the 2020.2.4 updates.

What went wrong

Pinging recipient 'ADM' on endpoint '29bd6b57-redacted' [local] has failed because of the error: DeliveryFailedPing message received:The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it has been Aborted.

What you can do

Ensure that the recipient 'ADM' on endpoint '29bd6b57-redacted' [local] is running.