Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Server & Application Monitor (SAM) > SAM real-time controls no longer work on additional polling engine that resides in another domain

SAM real-time controls no longer work on additional polling engine that resides in another domain

Updated January 6, 2017

Overview

Real-time controls such as Process Explorer, Service Control Manager or Event Viewer fail on additional polling engines in another domain after upgrading to or installing SAM 6.3. 

 

The APM business layer log located in C:\ProgramData\SolarWinds\Logs\APM\APM.BusinessLayer.log may show the following:

 ERROR SolarWinds.APM.BusinessLayer.JobResultProcessing.JobManagerBase`1 - Exception
occurred when processing Job (6885be55-663e-4588-b77b-58fb356ef182) progress
System.NullReferenceException: Object reference not set to an instance of an object.
at SolarWinds.APM.BusinessLayer.JobResultProcessing.JobProgressManager.ForwardJobProgress
(JobProgress item)
at SolarWinds.APM.BusinessLayer.JobResultProcessing.JobProgressManager.
ProcessSingleQueueItem(JobProgress item)
at SolarWinds.APM.BusinessLayer.JobResultProcessing.JobManagerBase`1.QueueWorker
(TQueueItem queueItem)

 

If you change the APM Business Layer to DEBUG via logadjuster located in \Volume:\program files x86\Solarwinds\Orion\LogAdjuster.exe\

 

 

It may show the following entries:

 

DEBUG SolarWinds.APM.Common.BusinessLayerFactory - Creating proxy to APM Business Layer
listening on net.tcp://SOLARWINDS.DOMAIN.local:17777/orion/apm/businesslayer [try: 16]

[STP JobProgress Thread #0] DEBUG SolarWinds.APM.Common.BusinessLayerFactory -
There was no response from the SAM Business Layer located at
"net.tcp://
SOLARWINDS.DOMAIN.local:17777/orion/apm/businesslayer".

Environment

SAM 6.3.0

Cause 

SAM 6.3.0 made changes to the APM Business layer and communication to the primary polling engine that require FQDN name resolution.

Resolution

  1. Update the host file on the additional polling engines to reflect the FQDN of primary polling engine.
  2. Go to C:\Windows\System32\Drivers\etc\hosts
  3. Add a new line of entry. For example:
    You may have had this entry: SOLARWINDS 192.168.0.1
    Add a new line under: SOLARWINDS.DOMAIN.LOCAL 192.168.0.1
  4. Restart Orion module engine on the additional polling engine in question.
 

 

Last modified
23:51, 9 Apr 2017

Tags

Classifications

Public