The total number of queued software inventory (.sic or .sid) files on the site server has exceeded the standard operational threshold. This condition will increase unless it is resolved. If the queued site server software inventory file count keeps going beyond the threshold, software inventory will not be reflected in the SMS site database in a timely manner, and collections and reports may not accurately represent the software on the network.
The total number of queued software inventory files can exceed the threshold because:
The SMS Executive service is stopped or not responding on the site server.
Software Inventory Processor could be sending inventory details to a new parent site. These changes take priority over normal software inventory file processing, which is suspended until they are processed.
The site server processing rate is slower than the incoming rate of incoming software inventory files.
The site server has insufficient resources such as CPU, memory, or disk space.
The SMS site database has no more space.
Software inventory has been modified to collect additional information and the resulting larger file requires increased processing time.
A large number of clients has recently been inventoried.
The site server has lost connectivity with the SMS site database.
To resolve this issue and lower the number of queued software 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 server is performing properly.
Determine whether the increased load is due to an infrequent influx of new software 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 SMS site 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.
Modify the software inventory client agent inventory collection properties to inventory fewer files.
Verify that the site server can connect to 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 software 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 software inventory files (SINVs) on site servers:
In the Operations Manager 2007 Operations Console, select Monitoring and then expand Microsoft Systems Management Server (SMS) 2003, expand Performance, expand Processing Rates, and click Site Servers.
Click SINVs/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 SINV backlog:
In the Operations Manager 2007 Operations Console, select Authoring and then Rules.
In the details pane, expand Microsoft SMS 2003 Primary Site Server Installation, right-click Site Server SINV 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 software inventory file alert. Depending on the cause, it is likely that other types of backlogs (hardware inventory, data discovery records, software metering) on the site server are also increasing and corresponding alerts are occurring.
Target | Microsoft.SMS.2003.Microsoft_SMS_2003_Primary_Site_Servers_Installation | ||
Category | PerformanceHealth | ||
Enabled | True | ||
Instance Name | SMS Software Inventory Processor | ||
Counter Name | Total SINVs Enqueued | ||
Frequency | 900 | ||
Alert Generate | True | ||
Alert Severity | Warning | ||
Alert Priority | Low | ||
Remotable | True | ||
Alert Message |
| ||
Comment | Mom2005ID='{05E46414-A115-4383-A96A-4338CCFFF829}';MOM2005ComputerGroupID={5BCC9E15-4EC1-49AB-AABC-E63CFC1D0F31} |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
_0E726505_562A_4076_AE8B_4813FBE35905_ | DataSource | System.Mom.BackwardCompatibility.Performance.FilteredDataProvider | Default |
AverageFilter | ConditionDetection | System.Performance.AveragerCondition | Default |
GenerateAlert | WriteAction | System.Mom.BackwardCompatibility.AlertResponse | Default |
<Rule ID="SMS_2003_Perf_Threshold__Site_Server_SINV_Backlog__10000_over_3_hours_8_Rule" Target="Microsoft.SMS.2003.Microsoft_SMS_2003_Primary_Site_Servers_Installation" Enabled="true" ConfirmDelivery="false" Comment="Mom2005ID='{05E46414-A115-4383-A96A-4338CCFFF829}';MOM2005ComputerGroupID={5BCC9E15-4EC1-49AB-AABC-E63CFC1D0F31}">
<Category>PerformanceHealth</Category>
<DataSources>
<DataSource ID="_0E726505_562A_4076_AE8B_4813FBE35905_" Comment="{0E726505-562A-4076-AE8B-4813FBE35905}" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.Performance.FilteredDataProvider">
<ComputerName>$Target/Host/Property[Type="WindowsLibrary!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<CounterName>Total SINVs Enqueued</CounterName>
<ObjectName>SMS Software Inventory 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="MomBackwardCompatibility!System.Mom.BackwardCompatibility.AlertResponse">
<AlertGeneration>
<GenerateAlert>true</GenerateAlert>
<Owner/>
<Description>$Target/Host/Property[Type="WindowsLibrary!Microsoft.Windows.Computer"]/NetbiosComputerName$ - SMS 2003 Perf Threshold: Site Server SINV Backlog > 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>SMS 2003 Perf Threshold: Site Server SINV Backlog > 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>
</AlertGeneration>
<InvokerType>0</InvokerType>
</WriteAction>
</WriteActions>
</Rule>