Submit a ticketCall us

AnnouncementsCome see SolarWinds at VMUG Frankfurt

SolarWinds is delighted to attend the upcoming VMUG which will take place at Kap Europa in Frankfurt on June 19th, 2018.

See event details.

Home > Success Center > Server & Application Monitor (SAM) > Real-time Process Explorer polling times out

Real-time Process Explorer polling times out

Overview

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

Environment

  • Server and Application Monitor 6.0 +

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.

 

Solarwinds SAM 6.0 - 6.3  
  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. Insert the following line directly after the  </configSections> line:
    <realTimeProcessExplorer pollingTimeout="00:03:00" jobLifetime="00:05:00" reschedulePollingBeforeEnd="00:01:00" pollInterval="00:00:05"/>
  4. Restart the SolarWinds Orion Module Engine service to apply this change.

 

 

 

Solarwinds SAM 6.4 And Above:


- Login to the Solarwinds Server.
- Open the SolarWinds.APM.BusinessLayer.dll.config file in a text editor (c:\Program Files(x86)\SolarWinds\Orion\APM\).
- Change the below mentioned line:

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


- Restart All Solarwinds Services on your Polling Engine using the Orion Service Manager

 

 

 

 

 

Last modified

Tags

Classifications

Public