Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Application Dependency polling creates event if node is down (SAM)

Application Dependency polling creates event if node is down (SAM)

Updated February 9, 2018


Application Dependency polling triggers an event for "down" nodes instead of skipping them. A message similar to this example appears: ADM polling failed for node WIN-TESTNODE: Request failed - ErrorCode:AgentDeliveryTimeout, Message:'', DetailInfo:2D2816FE for NodeID:2 AgentID:2"


  • SAM 6.6


Application Dependency polling does not currently ignore "down" nodes. 


Here are two workarounds:

  • Fix the issue causing the node to be Down.
  • Disable Application Dependency polling for the node until the issue is fixed, then re-enable polling. There are two ways to disable polling at the node level:
    • On the Edit Node page, clear the Application Dependency Mapping Enabled check box.
    • Use SolarWinds Query Language (SWQL) to disable polling in the ADM_NodeInventory table. 
Last modified