1 of 1 people found this helpful
Ah, I know just what's going on.
The traceroute, whois, and nslookup commands route through an agent rather than requiring you to install some extra component into your LEM console or some other tricksy way that would probably make you uncomfortable about your browser executing commands on disk.
How it works:
- The FIRST agent that connects that has the capability to run these commands (i.e. any modern agent) will get assigned the role of "Default Commands Agent"
- Whenever you use those explorer utilities, the Console will ask the manager to ask the agent to run the command, and as results are retrieved, they are displayed in the Console
What happened in your situation is that that agent was either deleted or is offline. In the case where the agent is deleted, you'll have to select a new one to take on that role. Other reasons you might want to do that include the ability to choose which "path" or network those utility explorers use (in case you have multiple networks or agents that are external to your LAN).
To fix it, go to Manage > Appliances, click on "Settings" in the Properties area, and pick a new agent from the "Explorer Command Agent" area's "Default Agent" dropdown.
I am having the same problem. I don't see anything posted since 2012.
I installed a windows agent and it is set up and the Explorer Command Agent, the the "agent not found" error still occurs.
Do you by chance have more than one agent with the same name? It might be hooked up to an old/nonexistent one and not to the correct one.