Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

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

SAM Application Dependency polling creates event if node is down

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