This monitor checks backlog of offermgr.box on site server. It raises alert if the backlog exceeds the threshold.
Knowledge Base article:
Summary
The total number of files in the Offer Manager's offermgr.box\INCOMING inbox on the site server has exceeded the standard operational threshold.
This folder temporarily stores offer, advertisement, data (.ofr) that is received from a child or parent Configuration Manager site.
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 advertisements and reports might not accurately represent the state of the child sites.
Causes
The total number of files can exceed the threshold because:
The SMS_Executive service is stopped or is not responding on the site server.
The Offer Manager has stopped.
The Offer Manager could be processing received offers or evaluating collection changes.
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 problem and decrease 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 is not responding, restart the service.
Run SMS Service Manager and verify that the SMS_OFFER_MANAGER component is running. If it is not running, start it.
Verify that the Configuration Manager site database is performing properly.
Determine whether the increased load is due to an infrequent influx of new data discovery records (DDR) or whether the DDR 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 discovered client computers, the problem can resolve itself if there are sufficient resources to process pending DDRs in addition to the standard DDR 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.
Plan the type and frequency of your discovery methods carefully. Conduct performance testing to verify that the infrastructure can accommodate the discovery load. Adjust the frequency of discovery to allow for a longer interval for DDRs to be processed.
Modify the discovery configuration to discover fewer resources.
Modify the collection update schedule to have less effect.
Verify that the site server can connect to the Configuration Manager site database server.
Examine status messages for the Offer Manager for possible problems.
Examine the Offermgr.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 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 Offer 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.
Home
ENU