MECM Site server inbox compsumm.box backlog Monitor

Summary

The total number of files in Component Status Summarizer’s compsumm.box\repl inbox on the site server has exceeded the standard operational threshold.

This folder temporarily stores Configuration Manager component status files (.sum) that need to be replicated to the parent site server.

This condition will increase unless it is resolved. If the file count keeps going beyond the threshold, component status will not be replicated and reflected in the parent Configuration Manager site database in a timely manner, and status and reports may not accurately represent the components in this site and its child sites.

Causes

The total number of files can exceed the threshold because:

• The SMS Executive service is stopped or not responding on the site server.

• Component Status Summarizer could be processing changes to the parent site, or it could be sending status details to a new parent site. These changes take priority over normal status processing, which is suspended until they are processed.

• The site server has insufficient resources such as CPU, memory, or disk space.

• The Configuration Manager site database has no more space.

• The site server may have lost connectivity with the Configuration Manager site database server.

• Sending data to the parent site may be impacted or not possible at this time.

Resolutions

To resolve this issue and lower the number of files:

• Verify that the threshold for this alert is not too low and 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 not responding, restart the service.

• Verify that the Configuration Manager site database is performing properly.

• Verify that the Configuration Manager site database has sufficient space. If the database is set to autogrow, verify that there is sufficient disk space for the database to expand.

• Set the priority for replicating component status summarizer data to the parent site. Conduct performance testing to verify the infrastructure can accommodate the status load.

• Verify that the site server can connect to the Configuration Manager site database server.

• Verify that the site server can send to the parent site.

• Examine status messages for the Component Status Summarizer for possible problems.

• Examine the Compsumm.log file in the Configuration Manager Logs folder for errors or additional information.

Additional

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.

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 component status summarizer not replicating component status. Depending on the cause, it is likely that other types of backlogs (hardware inventory, software inventory, software metering) on the site server are also increasing and corresponding alerts are occurring.