The total number of queued hardware inventory files (.hic or .hid) on the site server has exceeded the standard operational threshold. This condition will increase unless it is resolved. If the queued site server hardware inventory file count keeps going beyond the threshold, hardware inventory will not be reflected in the SMS site database in a timely manner, and collections and reports may not accurately represent the devices on the network.
The total number of queued hardware inventory files can exceed the threshold because:
The SMS Executive service is stopped or not responding on the site server.
Inventory Data Loader could be sending inventory details to a new parent site. These changes take priority over normal hardware inventory file processing,which is suspended until they are processed.
The site server file processing rate is slower than the incoming rate of hardware inventory files.
The site server has insufficient resources such as CPU, memory, or disk space.
The SMS site database has no more space.
The SMS_def.mof file has been modified to collect additional information and the resulting larger inventory file requires increased processing time. Also, modifying the SMS_def.mof file will force a hardware inventory resynchronization which will result in more hardware inventory files to be processed.
The site server may have lost connectivity with the SMS site database server.
To resolve this issue and lower the number of queued hardware inventory files:
Verify that the threshold for this alert is not too low and is beyond the standard operating threshold for this specific SMS site.
Verify that the SMS Executive service is running on the site server. If it is stopped or not responding, restart the service.
Verify that the SMS site database is performing properly.
Determine whether the increased load is due to an infrequent influx of new hardware inventory records, or whether the file load remains relatively constant. If the load is constant, update the SMS infrastructure to achieve zero processing backlogs. If the load is due to a large number of newly inventoried computers, the issue may resolve itself if there are sufficient resources to process pending files in addition to the standard file load.
Verify that the SMS site database has sufficient space. If the database is set to autogrow, verify that there is sufficient disk space for the database to expand.
Adjust frequency of inventory collection to allow for a longer interval for files to be processed.
Plan carefully before modifying the SMS_def.mof file. Conduct performance testing to verify that the infrastructure can accommodate the extra load, including hardware inventory resynchronizations. If the infrastructure cannot accommodate the extra load you may need to return the SMS_def.mof back to the default settings.
Verify that the site server has connectivity with the SMS site database server.
For more information about server sizing, see Scenarios and Procedures for Microsoft Systems Management Server 2003: Planning and Deployment at the Systems Management Server 2003 Product Documentation Web page.
For more information about backlogs and site maintenance, see Scenarios and Procedures for Microsoft Systems Management Server 2003: Maintenance, Backup and Recovery at the Systems Management Server 2003 Product Documentation Web page.
For more information about troubleshooting hardware inventory, see the Troubleshooting Flowcharts at the Systems Management Server 2003 Product Documentation Web page.
For more assistance, a list of additional support options is available in the support section of the SMS Web site at Support for Systems Management Server.
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.
To view a graph that plots the trend in processing rates for hardware inventory files (HINVs) on site servers:
In the Operations Manager 2007 Operations Console, select Monitoring, expand Microsoft Systems Management Server (SMS) 2003, expand Performance, expand Processing Rates, and then click Site Servers.
Click HINVs/minute in the last 24 hours.
Processing rates will not show on the graph unless the corresponding performance measure is enabled first. To enable the performance measure for HINV backlog:
In the Operations Manager 2007 Operations Console, select Authoring and then Rules.
In the details pane, expand Microsoft SMS Primary Site Server Installation, right-click Site Server HINV Backlog, and then click Enable.
This alert is best handled by SMS administrators.
Related Events
You can also look for alerts relating to the SMS Executive service being stopped or the site server having insufficient resources (such as CPU, memory). These alerts are the potential cause of the hardware inventory file alert. Depending on the cause, it is likely that other types of backlogs (software inventory, data discovery records, software metering) on the site server are also increasing and corresponding alerts are occurring.
| Target | Microsoft.SMS.2003.SMS_Server_Class | ||
| Parent Monitor | SS | ||
| 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 | Internal | ||
| Alert Message |
| ||
| RunAs | Default | ||
| Comment | Mom2005ID='{BBFB7F3C-271D-4D8A-BDCE-6E9CBC2B7103}' |
Home
ENU <UnitMonitor ID="SMS_2003_Perf_Threshold__Site_Server_HINV_Backlog__10000_over_3_hours_8_Rule.AdvancedAlertCriteriaMonitor" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.PerformanceThreshold.ThreeStateMonitorType" Accessibility="Internal" Target="Microsoft.SMS.2003.SMS_Server_Class" Enabled="true" ParentMonitorID="SS" Comment="Mom2005ID='{BBFB7F3C-271D-4D8A-BDCE-6E9CBC2B7103}'">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="SMS_2003_Perf_Threshold__Site_Server_HINV_Backlog__10000_over_3_hours_8_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>SS</Component>
<ServerRoleInstance>$Target/Property[Type="Microsoft.SMS.2003.SMS_Server_Class"]/Name_1$</ServerRoleInstance>
<RuleId>$MPElement[Name="SMS_2003_Perf_Threshold__Site_Server_HINV_Backlog__10000_over_3_hours_8_Rule"]$</RuleId>
<ErrorThreshold>10000</ErrorThreshold>
<ErrorOperator>Greater</ErrorOperator>
<WarningThreshold>5000</WarningThreshold>
<WarningOperator>Greater</WarningOperator>
</Configuration>
</UnitMonitor>