The total number of files in the sinv.box inbox of the software inventory processor on this site server has exceeded the standard operational threshold.
This folder temporarily stores client software inventory files (.sic, .sid, and .sis) from down-level Configuration Manager sites, SMS sites; SMS 2003 RTM Management Points and Client Access Points.
This condition increases unless it is resolved. If the file continues beyond the threshold, software inventory is not reflected in the Configuration Manager 2007 site database in a timely manner, and collections and reports might not accurately represent the software on the network.
The total number of software inventory files in the inbox can exceed the threshold because:
The software inventory processor service is stopped or is not responding on the site server.
The software inventory processor could be sending inventory details to a new parent site. These changes take priority over standard 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 Configuration Manager 2007 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. When a new child site is attached, all of its clients will send SIC files which will contribute to this event. If a new child site has been added, all of its clients send .sic files, which contributes to this event.
The site server has lost connectivity to the Configuration Manager 2007 site database.
Examine status messages for the software inventory processor for possible problems.
Examine the Sinvproc.log file in the Configuration Manager Logs folder for errors or additional information.
To resolve this issue and to decrease 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 Configuration Manager 2007 site.
Run SMS Service Manager and verify that the SMS_SOFTWARE_INVENTORY_PROCESSOR component is running. If it is not running, start it.
Verify that the Configuration Manager 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 Configuration Manager 2007 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.
Verify that the Configuration Manager site database has sufficient space. If the Configuration Manager 2007 site database is set to autogrow, verify that there is sufficient disk space for the database to expand.
Adjust the 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 Configuration Manager 2007 site database server.
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.
To view a graph that plots the backlog trend for this inbox on site servers:
In the Operations Console, click Monitoring.
In the Navigation pane, navigate to Microsoft System Center Configuration Manager 2007 > Performance > Backlogs, and then click Site Servers.
Click Inbox sinv.box Backlog in the last 48 hours.
Backlog trending does not appear unless the corresponding performance measure is enabled first. To enable the performance measure for sinv.box backlog:
In the Operations Console, click Authoring.
In the Navigation pane, navigate to Authoring > Management Pack Objects, and then click Rules.
In the Rules pane, right-click the ConfigMgr 2007 Perf Measure: Site Server Inbox sinv.box Backlog rule, navigate Overides > Overide the Rule and click For All Objects of Type: Microsoft ConfigMgr 2007 Primary Site Servers.
Set the Enabled property to True and click OK.
Related Events:
You can also look for alerts that relate 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.
See Planning and Deploying the Server Infrastructure for Configuration Manager 2007 at the Configuration Manager Product Documentation Web page.
For more information about inbox folders and how they are used in Configuration Manager, see the “A description of inbox folders and how they are used in Configuration Manager” Web page ( http://go.microsoft.com/fwlink/?LinkId=99539).
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.
Target | Microsoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Site_Servers_Installation |
Category | PerformanceHealth |
Enabled | True |
Instance Name | SMS Inbox |
Counter Name | File Current Count |
Frequency | 900 |
Alert Generate | False |
Remotable | True |
Comment | Mom2005ID='{0CA6413F-000A-4C6B-B3F3-F783A4C98523}';MOM2005ComputerGroupID={D0741372-F3F6-43EB-8B8B-965F937BCC65} |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
_05CCD6CD_FAC3_42F3_84B3_F733879545B4_ | DataSource | System.Mom.BackwardCompatibility.Performance.FilteredDataProvider | Default |
AverageFilter | ConditionDetection | System.Performance.AveragerCondition | Default |
GenerateAlert | WriteAction | System.Mom.BackwardCompatibility.AlertResponse.WithServerRole | Default |
<Rule ID="SMSv4_Perf_Threshold__Site_Server_Inbox_sinv.box_Backlog__10000_over_3_hours_19_Rule" Target="Microsoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Site_Servers_Installation" Enabled="true" ConfirmDelivery="false" Comment="Mom2005ID='{0CA6413F-000A-4C6B-B3F3-F783A4C98523}';MOM2005ComputerGroupID={D0741372-F3F6-43EB-8B8B-965F937BCC65}">
<Category>PerformanceHealth</Category>
<DataSources>
<DataSource ID="_05CCD6CD_FAC3_42F3_84B3_F733879545B4_" Comment="{05CCD6CD-FAC3-42F3-84B3-F733879545B4}" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.Performance.FilteredDataProvider">
<ComputerName>$Target/Host/Property[Type="WindowsLibrary!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<CounterName>File Current Count</CounterName>
<ObjectName>SMS Inbox</ObjectName>
<InstanceName>sinv.box</InstanceName>
<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 Inbox sinv.box 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>ConfigMgr 2007 Perf Threshold: Site Server Inbox sinv.box 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>
<InvokerType>0</InvokerType>
</WriteAction>
</WriteActions>
</Rule>