Applications Systems

Real-time Process Explorer polling times out

If the Real-time Process Explorer polling times out in SolarWinds SAM, try extending the default timeout periods.

First published date

10/11/2018 8:53 PM

Last published date

12/23/2025 5:37 PM

Overview

This article discusses some situations where the Real-time Process Explorer polling times out and a possible workaround to overcome the issue.

Product section

Server Application Monitor

Cause

By default, the Real-Time Process Explorer timeout period to start polling is one minute. If it takes longer than this, increasing the timeout period can help.

Resolution

  • Consult your System Administrator before performing the following procedure.
  • SolarWinds strongly recommends that you only edit the SolarWinds.APM.BusinessLayer.dll.config file as instructed. Any additional modifications may result in system performance issues or may create an error state.
  • Save a copy of the original SolarWinds.APM.BusinessLayer.dll.config file to your local drive as a backup file, in case you need to roll back later.
  • Increasing the timeout value to more than 3 minutes is not recommended unless other parameters are adjusted accordingly.

To fix this issue in SolarWinds SAM 6.4 and later: 

  1. Login to the SolarWinds server.
  2. Open the SolarWinds.APM.BusinessLayer.dll.config file in a text editor (c:\Program Files(x86)\SolarWinds\Orion\APM\).
  3. Change the mentioned line below:
<RealTimeSettings ServiceLocalHostUnmanagedServiceNames="Winmgmt, RpcSs, eventlog, MSSQL$SQLEXPRESS, SQLEXPRESS, MSSQLSERVER, OrionModuleEngine, SWJobEngineSvc, SWJobEngineSvc2, SWJobSchedulerSvc, SWCollectorService" ServiceRemoteHostUnmanagedServiceNames="Winmgmt, RpcSs, eventlog" CaptureRecording="false"/>
To the following:
<RealTimeSettings
ServiceLocalHostUnmanagedServiceNames="Winmgmt, RpcSs, eventlog, MSSQL$SQLEXPRESS, SQLEXPRESS, MSSQLSERVER, OrionModuleEngine, SWJobEngineSvc, SWJobEngineSvc2, SWJobSchedulerSvc, SWCollectorService"
ServiceRemoteHostUnmanagedServiceNames="Winmgmt, RpcSs, eventlog"
ProcessPollingTimeout="00:03:00" ProcessJobLifetime="00:05:00" ProcessReschedulePollingBeforeEnd="00:01:00" ProcessPollInterval="00:00:05"
CaptureRecording="false" />
  1. Use the SolarWinds Platform Service Manager, found in the SolarWinds Platform folder of the Start menu, to restart all SolarWinds services on the polling engine.



If the polled node is running an SolarWinds Platform agent, the agent must be investigated. There are a few harmless things that can be tried first

  • Restarting the agent service on the agent
  • Reprovisioning the agent 
    • Windows: \agentserver\c$\Program Files (x86)\SolarWinds\Agent\SolarWinds.Agent.Setup.exe
    • Linux: SSH into agent > Run: service swiagentd init