MECM Site server inbox statmgr.box statmsgs backlog Monitor

Summary

The total number of files that are in the Status Manager's statmgr.box\statmsgs inbox on the site server has exceeded the standard operational threshold.

This folder stores status messages (.svf) from Configuration Manager site systems and clients before the messages are processed by the Status Manager. This includes replicated status messages from child sites.

This condition increases unless it is resolved. If the file count continues beyond the threshold, replicated information is not reflected in the Configuration Manager site database in a timely manner, and Configuration Manager status and reports might not accurately represent the status for this site and its child sites.

Causes

The total number of files can exceed the threshold because:

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

• The Status Manager could be processing a large number of received status messages.

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

• The Configuration Manager site database has no more space.

• A large number of clients has recently been discovered.

• The site server might have lost connectivity to the Configuration Manager site database server.

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.

• Run Configuration Manager Service Manager and verify that the SMS_STATUS_MANAGER component is running. If not, start it.

• Determine whether the increased load is due to an infrequent influx of new status messages, or whether the status 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 received status messages, the issue may resolve itself if there are sufficient resources to process pending messages in addition to the standard status message load.

• 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.

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

• Examine status messages for the Status Manager for possible problems.

• Examine the statmgr.log file in the <ConfigMgrInstallationPath>\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 that are more appropriate for your environment.

This alert is best handled by Configuration Manager Administrators.

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 or memory. These alerts are the potential cause of the Status Manager problems. 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.