This monitor checks that the SQL Server Service Broker port is correct.
This is a well-defined port (default 4022) used for replication communication between the child and parent SQL Servers. When installing a Configuration Manager site server, the Configuration Manager administrator performing the setup will configure a specific port for the SQL Server Service Broker port on which communication occurs between the child and parent SQL Servers. The Configuration Manager administrator installing the site server must have local administrative permissions on the SQL Server machine expected to be used for the site being set up and must know the SQL Server Service Broker port required for communication setup for its parent SQL Server Service Broker. The Configuration Manager administrator specifies this well-known port for the SQL Server service broker.
A SQL Server database Administrator has changed the TCP/IP port used to communicate with the SQL Server Service Broker that is configured for the Configuration Manager site system database server.
A firewall rule on the network is preventing communication using the configured port.
A network issue may have prevented the communication over this port.
When Configuration Manager detects that the SQL Server Service Broker port (default 4022) configured is not able to be reached, it tries to connect to the SQL Server machine containing its database and changes the SQL Server Service Broker port back to its original configuration. . However, if the Configuration Manager site server is unable to contact the SQL Server system, the network administrator needs to check for firewall port or network connectivity issues. Check the hman.log in the [Configuration Manager Installation folder]\Logs for further information.
| Target | MECM.SiteServer | ||
| Parent Monitor | System.Health.ConfigurationState | ||
| Category | ConfigurationHealth | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | MatchMonitorHealth | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | MECM.StatusMessage3State.MT | ||
| Remotable | True | ||
| Accessibility | Public | ||
| Alert Message |
| ||
| RunAs | Default |
Home
<UnitMonitor ID="MECM.SQLSSBPort.StatusMessage.Monitor" Accessibility="Public" Enabled="true" Target="MECM.SiteServer" ParentMonitorID="Health!System.Health.ConfigurationState" Remotable="true" Priority="Normal" TypeID="MECM.StatusMessage3State.MT" ConfirmDelivery="true">
<Category>ConfigurationHealth</Category>
<AlertSettings AlertMessage="MECM.SQLSSBPort.StatusMessage.Monitor.AlertMessage">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Property[Type="MECM.Server"]/SiteCode$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="UIGeneratedOpStateId9a11b765f4eb4ea3afd0e005cf6f23e9" MonitorTypeStateID="Good" HealthState="Success"/>
<OperationalState ID="UIGeneratedOpStateId189967d6d3984b07b78935eedae21d4b" MonitorTypeStateID="Warning" HealthState="Warning"/>
<OperationalState ID="UIGeneratedOpStateIdb97dfde7a3e049269cfd629c2f91e632" MonitorTypeStateID="Error" HealthState="Error"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</ComputerName>
<ComponentName>SMS_HIERARCHY_MANAGER</ComponentName>
<RuleId>D362CF53-926B-4f7d-A4A2-0691D3F177F5</RuleId>
<IntervalSeconds>360</IntervalSeconds>
<MatchCount>3</MatchCount>
</Configuration>
</UnitMonitor>