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

  • ID:  SMSv4_Perf_Threshold__Site_Server_SWM_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 SWM Backlog > 10,000 over 3 hours Medium Match Monitor Health Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

The total number of queued software metering files on the site server has exceeded the standard operational threshold. This condition increases unless it is resolved. If the queued site server software metering file count continues beyond the threshold, software metering information is not reflected in the Configuration Manager site database in a timely manner, and collections and reports might not accurately represent the software on the network.

Causes

The total number of queued software metering files can exceed the threshold because:

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

  • The processing rate of site server software metering files is slower than the incoming rate of software metering files.

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

  • The amount of software metering data that is collected, or the frequency of collection is exceeding hardware limitations.

  • Software metering files might be stuck in a retry loop.

Resolutions

To resolve this issue and to decrease the number of queued software metering files:

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

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

  • Verify that the Configuration Manager site database server is performing normally.

  • Determine whether the increased load is due to an infrequent influx of software metering data from new clients, or whether the software metering file load remains relatively constant. If the load is constant, update the Configuration Manager infrastructure to achieve zero processing backlogs. If the load is due to a large number of new software metering clients, the issue can resolve itself if there are sufficient resources to process pending software metering files in addition to the standard software metering file load.

  • Verify that the site server has sufficient resources. If necessary, add more memory, or make more disk space available, or both. If the computer is too slow, upgrade to a more powerful processor or to multiple processors.

  • Configure fewer software metering rules, and meter only those applications that are critical.

  • If the software metering file is caught in a retry loop, no action is necessary. After several retries, the file is discarded.

External References

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

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

For more information about Configuration Manager 2007, see the Configuration Manager Documentation Library Web page.

 

For more assistance, see a list of additional support options in the support section of the Configuration Manager Web site at Support for Configuration Manager.

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