This monitor checks the backlog of inbox\hman.box\ForwardingMsg on site server. It raises alert if the backlog exceeds the threshold.
The total number of files in the hman.box\ForwardingMsg inbox of Hierarchy Manager on the site server has exceeded the standard operational threshold.
This folder temporarily stores Hierarchy Manager files.
If the file count keeps going beyond the threshold, hierarchy information is not reflected in the Configuration Manager site database in a timely manner.
The total number of hierarchy manager files can exceed the threshold because:
The SMS_Executive service is stopped or is not responding on the site server.
The site server file processing rate is slower than the incoming rate of hierarchy manager files.
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 might have lost connectivity to the Configuration Manager site database server.
To resolve this issue and to decrease the number of hierarchy manager 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.
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.
Verify that the site server has connectivity to the Configuration Manager site database server.
Target | MECM.SiteServerRoleBaseClass | ||
Parent Monitor | System.Health.PerformanceState | ||
Category | PerformanceHealth | ||
Enabled | True | ||
Instance Name | SMS Inbox | ||
Counter Name | File Current Count | ||
Frequency | 900 | ||
Alert Generate | True | ||
Alert Severity | MatchMonitorHealth | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | System.Performance.ConsecutiveSamplesThreshold | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Default |
<UnitMonitor ID="MECM.SiteServer.HmanInboxForwardingMsgBacklog.FileCurrentCount.PerfThreshold.Monitor" Accessibility="Public" Enabled="true" Target="MECM.SiteServerRoleBaseClass" ParentMonitorID="Health!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="Perf!System.Performance.ConsecutiveSamplesThreshold" ConfirmDelivery="false">
<Category>PerformanceHealth</Category>
<AlertSettings AlertMessage="MECM.SiteServer.HmanInboxForwardingMsgBacklog.FileCurrentCount.PerfThreshold.Monitor.AlertMessage">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/InstanceName$</AlertParameter1>
<AlertParameter2>$Data/Context/ObjectName$</AlertParameter2>
<AlertParameter3>$Data/Context/CounterName$</AlertParameter3>
<AlertParameter4>$Data/Context/SampleValue$</AlertParameter4>
<AlertParameter5>$Data/Context/TimeSampled$</AlertParameter5>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="ConditionFalse" MonitorTypeStateID="ConditionFalse" HealthState="Success"/>
<OperationalState ID="ConditionTrue" MonitorTypeStateID="ConditionTrue" HealthState="Error"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<CounterName>File Current Count</CounterName>
<ObjectName>SMS Inbox</ObjectName>
<InstanceName>hman.box>ForwardingMsg</InstanceName>
<AllInstances>false</AllInstances>
<Frequency>900</Frequency>
<Threshold>10000</Threshold>
<Direction>greater</Direction>
<NumSamples>12</NumSamples>
</Configuration>
</UnitMonitor>