Home
  •  

MECM Sender fails to connect to a remote site over LAN advanced security Event Rule

MECM.LanSender.FailedToConnectToRemoteSite.Event.Rule (Rule)

The rule generates alert when a sender fails to connect to a remote site over the LAN under advanced security.

Knowledge Base article:

Summary

The Configuration Manager LAN sender cannot connect to the remote site. If there are no other senders configured to connect to the remote site, there will be no communication from this site to the remote site until this condition is resolved. Communication can still be received from the remote site.

If the remote site is a parent site, this site cannot send any inventory or status messages up the site hierarchy. If the remote site is a child site, this site cannot send any package information or site configuration requests down the hierarchy.

The LAN sender automatically retries the connection and send operations.

Causes

This condition could occur because:

Resolutions

This alert is best handled by Configuration Manager administrators.

Element properties:

TargetMECM.LanSender
CategoryEventCollection
EnabledTrue
Event_ID3530
Event SourceSMS Server
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
RemotableTrue
Alert Message
MECM Sender connection failure alert
A sender failed to connect to remote site over the LAN under advanced security
Event Description: {0}
Event LogApplication

Member Modules:

ID Module Type TypeId RunAs 
DS DataSource Microsoft.Windows.EventProvider Default
Alert WriteAction System.Health.GenerateAlert Default

Source Code:

<Rule ID="MECM.LanSender.FailedToConnectToRemoteSite.Event.Rule" Enabled="true" Target="MECM.LanSender" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">

  <Category>EventCollection</Category>

  <DataSources>

    <DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">

      <ComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

      <LogName>Application</LogName>

      <Expression>

        <And>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value Type="UnsignedInteger">3530</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery Type="String">PublisherName</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value Type="String">SMS Server</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

        </And>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="Alert" TypeID="Health!System.Health.GenerateAlert">

      <Priority>1</Priority>

      <Severity>2</Severity>

      <AlertName/>

      <AlertDescription/>

      <AlertOwner/>

      <AlertMessageId>$MPElement[Name="MECM.LanSender.FailedToConnectToRemoteSite.Event.Rule.AlertMessage"]$</AlertMessageId>

      <AlertParameters>

        <AlertParameter1>$Data/EventDescription$</AlertParameter1>

      </AlertParameters>

      <Suppression>

        <SuppressionValue/>

      </Suppression>

      <Custom1/>

      <Custom2/>

      <Custom3/>

      <Custom4/>

      <Custom5/>

      <Custom6/>

      <Custom7/>

      <Custom8/>

      <Custom9/>

      <Custom10/>

    </WriteAction>

  </WriteActions>

</Rule>