Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 35 Source: WLBS
NLB Cluster 0.0.0.0 : Cluster mode cannot be enabled due to parameter errors. All traffic will be passed through to TCP/IP. Restart cluster operations after fixing the problem by running "wlbs reload" followed by "wlbs start".
|English: This information is only available to subscribers. An example of English, please!|
T787810 says that one should look for additional Network Load Balancing (NLB) events that indicate errors reading from the registry or other configuration problems. After fixing these errors, run nlb reload' followed by 'nlb start'.
As per Microsoft: "This event is probably logged because of incorrectly configured settings that are being read from the registry: in particular, IP addresses, IP subnet masks, or MAC addresses. Until this problem is corrected, this host will remain stopped and will not join the cluster". See MSW2KDB for additional information about this event.
NLB is not configured properly. In my specific case, I had NLB configure on a SBS 2003 Server, this caused exchange and a lot of other services to fail. Removed NLB from the Network connection properties and this solved my problem.
|Private comment: Subscribers only. See example of private comment|
|Links: MSW2KDB, T787810|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated