This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

How to Identify endpoints referenced in Active Diagnostics?

pwjmailloux over 7 years ago

This may not be the right category, but UDT often deals with endpoints and endpoint names so I assume it will be a good place to ask.

After running the Active Diagnostic tool to resolve some unrelated issues (now solved), I'm having a difficult time identifying what endpoints are being referred to in the issue outlined below. Is there anyway to determine what those UID's are representing? (ie: a7b8ceef-cb20-44e8-a6f8-cd3e3f6ee3d4)

TITLE: Ping all plugins on agents (Agent Infrastructure)

DISCOVERED: 7/25/2016 10:32:35 AM

RESOLUTION: Ensure that the recipient 'Discovery' on endpoint 'a7b8ceef-cb20-44e8-a6f8-cd3e3f6ee3d4' is running.

Ensure that the recipient 'Discovery' on endpoint '3cfe3c75-eebb-4c44-8f66-93bd022db524' is running.

Ensure that the recipient 'NetPath' on endpoint 'a7b8ceef-cb20-44e8-a6f8-cd3e3f6ee3d4' is running.

Ensure that the recipient 'NetPath' on endpoint '3cfe3c75-eebb-4c44-8f66-93bd022db524' is running.

Ensure that the recipient 'Discovery' on endpoint '7c56b704-f426-46ce-b541-c8e44fa32a8e' is running.

Ensure that the recipient 'NetPath' on endpoint '7c56b704-f426-46ce-b541-c8e44fa32a8e' is running.

Ensure that the recipient 'NetPath' on endpoint 'd9b80b3c-fc16-4e18-b8ea-279f369ac779' is running.

Ensure that the recipient 'Discovery' on endpoint 'd9b80b3c-fc16-4e18-b8ea-279f369ac779' is running.

DESCRIPTION: Pinging the service has failed: Object reference not set to an instance of an object.

Pinging the service has failed: Object reference not set to an instance of an object.

Pinging recipient 'NetPath' on endpoint 'a7b8ceef-cb20-44e8-a6f8-cd3e3f6ee3d4' has failed because of the error: DeliveryFailedPing message received:{"errorCode":87,"errorMessage":"AgentTaskHandlerBase::execute: ewException caught: Error [0x57], [WorkerProcessController::GetWorkerProcessProxy - invalid plugin usage: pluginId [NetPath], path [C:\\Program Files (x86)\\SolarWinds\\Agent\\Plugins\\NetPath], process type []], File: AgentTaskHandlerBase.cpp, Line: 116"}

Pinging recipient 'DPIProbe' on endpoint '3cfe3c75-eebb-4c44-8f66-93bd022db524' succeeded with response status 'up'. Version: '2.1.0.174'

Pinging recipient 'JobEngine' on endpoint 'a7b8ceef-cb20-44e8-a6f8-cd3e3f6ee3d4' succeeded with response status 'up'. Version: '2.11.0.223'

Pinging recipient 'JobEngine' on endpoint '3cfe3c75-eebb-4c44-8f66-93bd022db524' succeeded with response status 'up'. Version: '2.11.0.223'

Pinging recipient 'NetPath' on endpoint '3cfe3c75-eebb-4c44-8f66-93bd022db524' has failed because of the error: DeliveryFailedPing message received:{"errorCode":87,"errorMessage":"AgentTaskHandlerBase::execute: ewException caught: Error [0x57], [WorkerProcessController::GetWorkerProcessProxy - invalid plugin usage: pluginId [NetPath], path [C:\\Program Files (x86)\\SolarWinds\\Agent\\Plugins\\NetPath], process type []], File: AgentTaskHandlerBase.cpp, Line: 116"}

Pinging the service has failed: Object reference not set to an instance of an object.

Pinging recipient 'JobEngine' on endpoint '7c56b704-f426-46ce-b541-c8e44fa32a8e' succeeded with response status 'up'. Version: '2.11.0.223'

Pinging recipient 'NetPath' on endpoint '7c56b704-f426-46ce-b541-c8e44fa32a8e' has failed because of the error: DeliveryFailedPing message received:{"errorCode":87,"errorMessage":"AgentTaskHandlerBase::execute: ewException caught: Error [0x57], [WorkerProcessController::GetWorkerProcessProxy - invalid plugin usage: pluginId [NetPath], path [C:\\Program Files (x86)\\SolarWinds\\Agent\\Plugins\\NetPath], process type []], File: AgentTaskHandlerBase.cpp, Line: 116"}

Pinging recipient 'DPIProbe' on endpoint 'd9b80b3c-fc16-4e18-b8ea-279f369ac779' succeeded with response status 'up'. Version: '2.1.0.174'

Pinging recipient 'NetPath' on endpoint 'd9b80b3c-fc16-4e18-b8ea-279f369ac779' has failed because of the error: DeliveryFailedPing message received:{"errorCode":87,"errorMessage":"AgentTaskHandlerBase::execute: ewException caught: Error [0x57], [WorkerProcessController::GetWorkerProcessProxy - invalid plugin usage: pluginId [NetPath], path [C:\\Program Files (x86)\\SolarWinds\\Agent\\Plugins\\NetPath], process type []], File: AgentTaskHandlerBase.cpp, Line: 116"}

Pinging recipient 'Discovery' on endpoint 'd9b80b3c-fc16-4e18-b8ea-279f369ac779' has failed because no response was received in the defined timeout 5000 ms.

Pinging recipient 'JobEngine' on endpoint 'd9b80b3c-fc16-4e18-b8ea-279f369ac779' succeeded with response status 'up'. Version: '2.11.0.223'

0 cnorborg over 7 years ago

So, I've had this same message pop up in my "Solarwinds Active Diagnostics" and I've made the tiniest bit of progress on it.   It's showing up on "Agent Infrastructure" under "Ping all plugins on agents". The error looks like this:
I should note that I have "Success" with the same 3 "endpoints" for the "Discovery", "JobEngine", "DPIProbe" tests, its only on the "NetPath" ping recipient that it fails.
If you go into the table "AgentManagement_Agents", you can find the "endpoint" string (above starting with a69e51a7) for these boxes.   I have 3 boxes in it, all three have the agent on them, but all 3 fail in this "NetPath" test, even though one of the three is my main Orion server and does do NetPath.
So I'm still very unclear what these errors are, but I don't think they're as bad as the red circle icon with the exclamation point in it suggests.
Anyone from Solarwinds want to comment on this?   Is there a good explanation of each test in the ActiveDiagnostics somewhere?
Cancel
Vote Up 0 Vote Down

Cancel
0 wneighbo over 6 years ago

the endpoints reference the column 'AgentGuid' in the AgentManagement_Agents table in your Solarwinds DB. I am experiencing the same issue with Netpath and Discovery pings failing.
Cancel
Vote Up 0 Vote Down

Cancel