NLB cluster [%2]: NLB can't track TCP connections because it was unable to open the TCP connection callback object. Although NLB will still accept new connections, it will not track the connection state until this is resolved. This might result in breaking the affinity maintained by the driver during the connection. To resolve this issue, try to unbind then rebind NLB to the adapters.
NLB cluster %2]: Host %5 converged with legacy host(s)%3. This is expected during rolling upgrades. Until all hosts are upgraded ...
NLB cluster %2]: Invalid bi-directional affinity (BDA) team ID detected. Team IDs must be a GUID of the form {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}. ...
NLB cluster %2]: Invalid bi-directional affinity (BDA) teaming port rules detected. Each member of a BDA team may have no ...
NLB cluster %2]: Last known NLB host state was not found in the registry. The state of this host will revert to the user-specified ...
NLB cluster %2]: NLB can't track TCP connections because it was unable to open the TCP connection callback object. Although ...
NLB cluster %2]: NLB detected a duplicate host priority %5 that is shared between cluster hosts. Each host in the NLB cluster ...
NLB cluster %2]: NLB detected an unequal number of dedicated IP (DIP) addresses and network masks. For all DIP's listed for ...
NLB cluster %2]: NLB detected an unequal number of virtual IP (VIP) addresses and network masks. For all VIP's listed for ...
NLB cluster %2]: NLB detected duplicate cluster subnets. This may be due to network partitioning, which prevents NLB heartbeats ...