The total number of queued software inventory (.sic or .sid) files on the management point has exceeded the standard operational threshold. This condition increases unless it is resolved. If the queued management point software inventory file count continues beyond the threshold, software inventory 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.
The management-point-queued software inventory files can exceed the threshold because:
The SMS Agent Host service (CCMexec) is not running.
The management point file processing rate is slower than the incoming rate of files.
The management point has insufficient resources, such as CPU, memory, or disk space.
The Configuration Manager site database server might have insufficient resources.
The inventory collection settings of the software inventory client agent have been modified to collect a large amount of information, and the resulting larger file requires increased processing time.
A large number of clients has recently been inventoried.
The management point might have lost connectivity to the Configuration Manager site database server.
To resolve this issue and decrease the number of queued management point software inventory files:
Verify that the SMS Agent Host service (CCMexec) is running. If it is stopped, start it. If you encounter errors when starting it, make sure logging is enabled for the service, and examine the CCMexec.log file.
Verify that the threshold for this alert is not too low and is beyond the standard operating threshold for this specific Configuration Manager site.
Determine whether the increased load is due to an infrequent influx of new software inventory files, or whether the 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 newly inventoried computers, the issue can resolve itself if there are sufficient resources to process pending files in addition to the standard file load.
Adjust the frequency of inventory collection to allow for a longer interval for files to be processed.
Modify the inventory collection settings of the software inventory client agent to collect less information.
Verify that the management point can connect to the Configuration Manager site database server.
You can also look for alerts that relate to the SMS_Executive service being stopped or the management point having insufficient resources. such as CPU, memory. These alerts are the potential cause of the alert. Depending on the cause, it is likely that other types of backlogs (hardware inventory, data discovery records, software metering) on the management point are also increasing and corresponding alerts are occurring.
If this alert is generating too many false positives, you can modify the threshold tab of the rule properties to designate values more appropriate for your environment.
This alert is best handled by Configuration Manager administrators.
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 information about Configuration Manager Backup, see Planning for Backup and Recovery at the Configuration Manager Documentation Library Web page.
For more assistance, see a list of additional support options in the support section of Configuration Manager Web site at Support for Configuration Manager.
Target | Microsoft.SystemCenter.ConfigurationManager.2007.SMS_Server_Class | ||
Parent Monitor | MP | ||
Category | StateCollection | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | MatchMonitorHealth | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | System.Mom.BackwardCompatibility.PerformanceThreshold.ThreeStateMonitorType | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Default | ||
Comment | Mom2005ID='{FC05C8B3-2AE4-4B2F-81BA-2FD5D2F5043E}' |
<UnitMonitor ID="SMSv4_Perf_Threshold__MP_SINV_Backlog__10000_over_3_hours_17_Rule.AdvancedAlertCriteriaMonitor" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.PerformanceThreshold.ThreeStateMonitorType" Accessibility="Public" Target="Microsoft.SystemCenter.ConfigurationManager.2007.SMS_Server_Class" Enabled="true" ParentMonitorID="MP" Comment="Mom2005ID='{FC05C8B3-2AE4-4B2F-81BA-2FD5D2F5043E}'">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="SMSv4_Perf_Threshold__MP_SINV_Backlog__10000_over_3_hours_17_Rule.AdvancedAlertCriteriaMonitor.StringResource">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Name$</AlertParameter1>
<AlertParameter2>$Data/Context/Description$</AlertParameter2>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState HealthState="Success" MonitorTypeStateID="Success" ID="AlertLevelSuccess"/>
<OperationalState HealthState="Warning" MonitorTypeStateID="Warning" ID="AlertLevelWarning"/>
<OperationalState HealthState="Error" MonitorTypeStateID="Error" ID="AlertLevelError"/>
</OperationalStates>
<Configuration>
<ServerRole>SMS Server</ServerRole>
<Component>MP</Component>
<ServerRoleInstance>$Target/Property[Type="Microsoft.SystemCenter.ConfigurationManager.2007.SMS_Server_Class"]/Name_1$</ServerRoleInstance>
<RuleId>$MPElement[Name="SMSv4_Perf_Threshold__MP_SINV_Backlog__10000_over_3_hours_17_Rule"]$</RuleId>
<ErrorThreshold>10000</ErrorThreshold>
<ErrorOperator>Greater</ErrorOperator>
<WarningThreshold>5000</WarningThreshold>
<WarningOperator>Greater</WarningOperator>
</Configuration>
</UnitMonitor>