Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

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

Connection Timeout: Job cancelled by scheduler

Updated June 1, 2016


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

Connection Timeout: job cancelled by scheduler


All SAM versions        


The error is caused by either of the following:

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


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


Last modified