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 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


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


SAM 6.3.0


SAM 6.3.0 made changes to the APM Business layer and communication to the primary polling engine that require FQDN name 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
    Add a new line under: SOLARWINDS.DOMAIN.LOCAL
  4. Restart Orion module engine on the additional polling engine in question.


Last modified