NLB Cluster %2 %1: Unable to update the NLB host state in the registry. This will affect the ability of NLB to persist the current state across a reboot if NLB has been configured to do so. To predict the state of NLB at the next reboot, please delete the HKLM\SYSTEM\CurrentControlSet\Services\WLBS\Parameters\{GUID}\%3 registry value, which will cause the state at the next reboot to revert to the user-specified preferred initial host state. %4

Details
Product: Windows Operating System
Event ID: 74
Source: WLBS
Version: 5.2
Symbolic Name: MSG_WARN_HOST_STATE_UPDATE
Message: NLB Cluster %2 %1: Unable to update the NLB host state in the registry. This will affect the ability of NLB to persist the current state across a reboot if NLB has been configured to do so. To predict the state of NLB at the next reboot, please delete the HKLM\SYSTEM\CurrentControlSet\Services\WLBS\Parameters\{GUID}\%3 registry value, which will cause the state at the next reboot to revert to the user-specified preferred initial host state. %4
   
Explanation

A Network Load Balancing (NLB) host can be in one of three states: started, stopped or suspended. The preferred state of NLB on startup can be configured to be any one of the three available states. Each time the server restarts, the host assumes that initial state. However, NLB can be configured to remember a suspended state. This can be used to override the preferred initial state if a host is restarted while suspended and this option has been selected. The host will remain suspended upon completion of the restart, regardless of the specified initial state. NLB therefore must track the last known state of the host to correctly configure the host during a restart. If NLB cannot save that information to the registry, the startup state of the cluster at this restart and subsequent restarts might not be what is expected.

   
User Action

The registry key specified in the message is incorrect. To be able to predict the state of the NLB host at the next restart, advanced users should delete the following registry key, if it exists:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\WLBS\Parameters\Interface\{GUID}\HostState

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.

Deleting this key ensures that on the next restart, NLB will use the preferred initial host state.

For more information about Windows Registry best practices, see Help and Support.

Related:

Leave a Reply