ConfigMgr 2007 Perf Threshold: Site Server Scheduler Send Requests Backlog > 10,000 over 3 hours Monitor

  • ID:  SMSv4_Perf_Threshold__Site_Server_Scheduler_Send_Requests_Backlog__10000_over_3_hours_19_Rule.AdvancedAlertCriteriaMonitor
  • Description:   
  • Target:  ConfigMgr Server
  • Enabled:  Yes

Operational States

Name State Description
AlertLevelSuccess Success  
AlertLevelWarning Warning  
AlertLevelError Error  

Overridable Parameters

Parameter Name Default Value Description Override
ErrorThreshold 10000  
WarningThreshold 5000  

Alert Details

Monitor State Message Priority Severity Auto Resolution
  (Warning) ConfigMgr 2007 Perf Threshold: Site Server Scheduler Send Requests Backlog > 10,000 over 3 hours Medium Match Monitor Health Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

The total number of queued scheduler send requests has exceeded the standard operational threshold. Large backlogs indicate that information is not being sent through the site hierarchy. If this condition is caused by isolated events such as a large software distribution package being sent to another site, the problem may resolve on its own if there is sufficient processing time. If the condition is caused by repeated events, such as large numbers of clients sending resynchronized inventory, the problem will not be resolved until you fix the root cause. If the queued scheduler send requests count keeps going beyond the threshold, the length of time required to complete site-to-site communication increases. This could result in delays in processing software distribution to child sites or refreshing inventory information about parent sites.

Causes

The scheduler job messages can exceed the threshold because:

  • The SMS Executive service is stopped or not responding on the site server.

  • The processing rate of site server scheduler send requests is slower than the incoming rate of send requests that must be created.

  • The site server has insufficient resources such as CPU, memory, or disk space.

  • The administrator has sent a large package, or several packages, to one or more child sites.

  • The sender is not functioning properly between the two sites. This could be due to several reasons, such as network connectivity issues, account access problems, or sender configuration errors.

  • The administrator has deleted a large number of inventory records, which triggered a large number of inventory resynchronization requests.

  • A large number of clients has attached to a new site, which triggered a large number of inventory resynchronization requests.

Resolutions

To resolve this issue and lower the number of queued scheduler send requests :

  • Verify that the threshold for this alert is not too low and is beyond the standard operating threshold for this specific Configuration Mangaer site.

  • Verify that SMS Executive service is running on the site server. If it is stopped or not responding, restart the service.

  • Verify that the sender can connect to the destination site.

  • Evaluate the processing rates for software distribution to child sites. If the baseline performance for typical package processing is unacceptable, add resources or upgrade to a more powerful computer.

  • Reduce the size of packages sent to child sites or send them less frequently.

  • Avoid actions that generate large amounts of traffic between sites, like resynchronized inventory.

External References

For more information about server sizing, see Planning and Deploying the Server Infrastructure for Configuration Manager 2007 at the Configuration Manager 2007 Documentation Library web page.

For more assistance, a list of additional support options is available in the support section of the Configuration Manager 2007 web site at Support for Configuration Manager 2007.

See Also for System Center Configuration Manager Management Pack


Downloads for System Center Configuration Manager Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED