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

SMSv4_Perf_Threshold__Site_Server_SWM_Backlog__10000_over_3_hours_19_Rule (Rule)

Knowledge Base article:

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.

Additional

This alert is best handled by Configuration Manager administrators.

If this alert is generating too many false positives, you can modify the threshold tab of the rule properties to designate values that are more appropriate for your environment.

Related Events:

You can also look for alerts that relate to the SMS_Executive service being stopped or to the site server having insufficient resources (such as CPU, memory). These alerts are the potential cause of the software metering file alert. Depending on the cause, it is likely that other types of backlogs (hardware inventory, software inventory, data discovery records) on the site server are also increasing and corresponding alerts are occurring.

External

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.

For information about Configuration Manager Backup, see Planning for Backup and Recovery at the Configuration Manager Documentation Library Web page.

Element properties:

Target	Microsoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Site_Servers_Installation
Category	PerformanceHealth
Enabled	True
Instance Name	SMS Software Metering Processor
Counter Name	Total SWM Usage Files Enqueued
Frequency	900
Alert Generate	False
Remotable	True
Comment	Mom2005ID='{721FFCC5-640D-4BBC-89AD-3CD99854CF55}';MOM2005ComputerGroupID={D0741372-F3F6-43EB-8B8B-965F937BCC65}

Member Modules:

ID	Module Type	TypeId	RunAs
_03CFECF9_ECF0_4647_B948_241858476780_	DataSource	System.Mom.BackwardCompatibility.Performance.FilteredDataProvider	Default
AverageFilter	ConditionDetection	System.Performance.AveragerCondition	Default
GenerateAlert	WriteAction	System.Mom.BackwardCompatibility.AlertResponse.WithServerRole	Default

Source Code:

<Rule ID="SMSv4_Perf_Threshold__Site_Server_SWM_Backlog__10000_over_3_hours_19_Rule" Target="Microsoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Site_Servers_Installation" Enabled="true" ConfirmDelivery="false" Comment="Mom2005ID='{721FFCC5-640D-4BBC-89AD-3CD99854CF55}';MOM2005ComputerGroupID={D0741372-F3F6-43EB-8B8B-965F937BCC65}">

  <Category>PerformanceHealth</Category>

  <DataSources>

    <DataSource ID="_03CFECF9_ECF0_4647_B948_241858476780_" Comment="{03CFECF9-ECF0-4647-B948-241858476780}" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.Performance.FilteredDataProvider">

      <ComputerName>$Target/Host/Property[Type="WindowsLibrary!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

      <CounterName>Total SWM Usage Files Enqueued</CounterName>

      <ObjectName>SMS Software Metering Processor</ObjectName>

      <Frequency>900</Frequency>

      <Expression/>

    </DataSource>

  </DataSources>

  <ConditionDetection ID="AverageFilter" TypeID="PerformanceLibrary!System.Performance.AveragerCondition">

    <NumSamples>12</NumSamples>

  </ConditionDetection>

  <WriteActions>

    <WriteAction ID="GenerateAlert" TypeID="System.Mom.BackwardCompatibility.AlertResponse.WithServerRole">

      <GenerateAlert>true</GenerateAlert>

      <Owner/>

      <Description>$Target/Host/Property[Type="WindowsLibrary!Microsoft.Windows.Computer"]/NetbiosComputerName$ - ConfigMgr 2007 Perf Threshold: Site Server SWM Backlog &gt; 10,000 over 3 hours.





            $Data/ObjectName$

          :  

            $Data/CounterName$

          :  

            $Data/InstanceName$

           value = 

            $Data/Value$

          </Description>

      <AlertLevel>30</AlertLevel>

      <ResolutionState/>

      <Source>

            $Data/ObjectName$

          :  

            $Data/CounterName$

          :  

            $Data/InstanceName$

          </Source>

      <Name>ConfigMgr 2007 Perf Threshold: Site Server SWM Backlog &gt; 10,000 over 3 hours</Name>

      <ServerRole>SMS Server</ServerRole>

      <ServerRoleInstance>$Target/Host/Property[Type="WindowsLibrary!Microsoft.Windows.Computer"]/NetbiosComputerName$</ServerRoleInstance>

      <Component>SS</Component>

      <ProblemState>1</ProblemState>

      <InvokerType>0</InvokerType>

    </WriteAction>

  </WriteActions>

</Rule>