MECM Site server inbox schedule.box repl backlog Monitor

Summary

The total number of files that are in the Scheduler's schedule.box\requests inbox on the site server has exceeded the standard operational threshold.

This folder temporarily stores the initial send request files (.srq) before the Scheduler transfers the files to a sender. This folder also stores send request files that are returned when the sender cannot connect to the target site.

This condition increases unless it is resolved. If the file count continues beyond the threshold, sending jobs to parent and child sites is delayed, resulting in replicated information not being reflected in the Configuration Manager site databases of those sites in a timely manner. Configuration Manager objects and reports might not accurately represent the state of the parent or child sites.

Causes

The total number of files can exceed the threshold because:

• The Configuration Manager Scheduler component is stopped or not responding.

• The Configuration Manager Scheduler could be processing other outbound jobs.

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

• An event has occurred that requires the replication of a large amount of data.

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

• The Scheduler is experiencing problems creating the package to send, or the package is corrupted.

• The sender selected by Scheduler cannot connect to the target site.

• The sender selected by Scheduler is experiencing sending errors to the target site.

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

• Run Configuration Manager Service Manager and verify that the SMS_SCHEDULER component is running.

• Determine whether the increased load is due to an infrequent influx of new data, or the data load has remained 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 data from new sites or site changes, the issue may resolve itself if there are sufficient resources to process pending jobs in addition to the standard load.

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

• Verify that the sender can connect to the target site.

• Examine status messages for Scheduler for possible problems.

• Examine the sched.log file in the <ConfigMgrInstallationPath>\Logs folder for errors or additional information.