Submit a ticketCall us

AnnouncementsSystem Monitoring for Dummies

Tired of monitoring failures disrupting the system, application, and service? Learn the key monitoring concepts needed to help you create sophisticated monitoring and alerting strategies that can help you save time and money. Read the eBook.

Get your free eBook.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > A SAM template status shows Initial Poll in Progress

A SAM template status shows Initial Poll in Progress

Updated March 6th, 2019

Overview

This article provides brief information and steps to resolve the issue when a SAM template has already been assigned but Initial Poll in Progress status still shows after it was successfully added and tested. 

Environment

SAM version 6.0 and later

Cause

In some cases, the SWIS publish-subscribe notification does not work well between the main and additional poller. In such cases, the AP does not recognize that a new application was created and never schedules a polling job. 

Resolution

Note: The changes should be done on the additional poller machines.

This is a workaround. Update the SolarWinds.APM.BusinessLayer.dll.config to add  a query change notifier in addition to pub-sub (publish-subscribe). This is not turned on by default since pub-sub works fine in some case. 

 

1. Go to C:\Program Files (x86)\SolarWinds\Orion\APM\SolarWinds.APM.BusinessLayer.dll.config and open the config file using a text editor. 

2. Find the following string:

<apmSettings checkMaintenanceStatusTimer="06:00:00" maintenanceStatusOverdue="2.00:00:00" MaxNumberOfInitialWaitForAppDiscovery="30"></apmSettings>

3. Add the following lines at the end of the string:

useApplicationChangeQueryNotifier="true"

The string should now look like this:

  <apmSettings checkMaintenanceStatusTimer="06:00:00" maintenanceStatusOverdue="2.00:00:00" MaxNumberOfInitialWaitForAppDiscovery="30" useApplicationChangeQueryNotifier="true">

</apmSettings>

4.  Restart the module engine. 

 

  • This issue can also happen when one has the old license manager installed on the server but their current version uses a web-based license manager instead and this can cause conflict.
  • Please go to control panel and uninstall it.

 

 

Last modified

Tags

Classifications

Public