Submit a ticketCall us

WebinarFREE IT Monitoring Webcast

Don’t miss out on our webcast, Essential IT Monitoring with SolarWinds ipMonitor, where we will show you how to keep an eye on your IT environment from one centralized, affordable, and lightweight monitoring tool: SolarWinds® ipMonitor®.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Connection Timeout: Job cancelled by scheduler in Orion Platform

Connection Timeout: Job cancelled by scheduler in Orion Platform

Updated November 6, 2018

Overview

This article provides brief information and steps to resolve the following error:

Connection Timeout: job cancelled by scheduler

Environment

All SAM versions        

All Orion platforms

Cause

The error is caused by either of the following:

  • Corrupt performance counters
  • No connectivity between devices
  • Over burdened Job Engine handling failing components

Resolution

Note: Resolution 1 and 2 are to be performed on the Target system, not the system hosting the SAM installation or the Additional Poller installation.

 

Resolution 1:

Rebuild performance counters. See How to Rebuild Performance Counters Library (© 2017 Microsoft, available at https://support.microsoft.com, obtained on April 27, 2017.) for more information. 

 

Resolution 2:

Warning: SolarWinds strongly recommends that you create a backup of your registry. The following procedure can create permanent changes on your registry. 

  1. Create a backup of your registry (© 2017 Microsoft, available at https://support.microsoft.com, obtained on April 27, 2017.).
  2. Open the Registry editor. 
    1. Click Start > Run.
    2. Enter CMD.
    3. Enter regedit
  3. Expand HKLM > Software > Microsoft\Windows NT >  CurrentVersion > Perflib.
    • ( HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Perflib\default may not have a value set at all, if so simply add 0 to the value )
  4. Right-click Default.
  5. Check the Data Value. It must NOT be set to 1.
  6. Reboot the server. 

 

Resolution 3:

Go through all of the currently assigned applications and remove any that are failing as down or unknown. If you don't want to remove them figure out why they are failing and resolve it. Failures and unknown components take much much longer to process because the scheduler has to wait for the timeout before it finally gives up.

 

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

 

Last modified

Tags

Classifications

Public