Home
  •  

NLB failed to update the NLB host state in the registry

Microsoft.Windows.NetworkLoadBalancing.6.2.NLB.failed.to.update.the.NLB.host.state.in.the.registry (Rule)

Knowledge Base article:

Summary

When configured to do so, the Network Load Balancing (NLB) host state will persist whenever the NLB cluster shuts down and restarts.

Resolutions

Confirm that the initial host state is correct

To check the initial Network Load Balancing (NLB) host state, you must first delete the registry key defined in the event log, and then confirm that the initial host state is correct.

Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on your computer.

Delete the registry key defined in the event log entry

To delete the registry key defined in the event log entry:

The GUID is the globally unique identifier of the network adapter that is experiencing the problem. This will be the network adapter that is bound to NLB. If NLB is, or has been, bound to multiple network adapters, you can find the correct adapter by looking at the value for the ClusterIPAddress key for each GUID entry in the registry.

Confirm that the NLB initial host state is correctly configured

To confirm the NLB initial host state is correctly configured:

Element properties:

TargetMicrosoft.Windows.NetworkLoadBalancing.6.2.ServerRole
CategoryAlert
EnabledTrue
Alert GenerateFalse
RemotableTrue

Member Modules:

ID Module Type TypeId RunAs 
DS DataSource Microsoft.Windows.NetworkLoadBalancing.EventProvider Default
WA WriteAction Microsoft.Windows.NetworkLoadBalancing.6.2.GenerateAlert.SuppressByDescription Default
WriteToDB WriteAction Microsoft.Windows.NetworkLoadBalancing.6.2.CollectEvent Default

Source Code:

<Rule ID="Microsoft.Windows.NetworkLoadBalancing.6.2.NLB.failed.to.update.the.NLB.host.state.in.the.registry" Enabled="onEssentialMonitoring" Target="Microsoft.Windows.NetworkLoadBalancing.6.2.ServerRole" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">

  <Category>Alert</Category>

  <DataSources>

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

      <Criteria>

        <SimpleExpression>

          <ValueExpression>

            <XPathQuery>EventDisplayNumber</XPathQuery>

          </ValueExpression>

          <Operator>Equal</Operator>

          <ValueExpression>

            <Value>74</Value>

          </ValueExpression>

        </SimpleExpression>

      </Criteria>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="WA" TypeID="Microsoft.Windows.NetworkLoadBalancing.6.2.GenerateAlert.SuppressByDescription">

      <Priority>1</Priority>

      <Severity>1</Severity>

      <AlertMessageId>$MPElement[Name="Microsoft.Windows.NetworkLoadBalancing.6.2.NLB.failed.to.update.the.NLB.host.state.in.the.registry.AlertMessage"]$</AlertMessageId>

      <EnableAlert>true</EnableAlert>

    </WriteAction>

    <WriteAction ID="WriteToDB" TypeID="Microsoft.Windows.NetworkLoadBalancing.6.2.CollectEvent">

      <CollectEvent>false</CollectEvent>

    </WriteAction>

  </WriteActions>

</Rule>