Windows Load Balancing Service Writes Multiple Duplicate Event Log Messages

ID: Q247719


The information in this article applies to:
  • Microsoft Windows NT Server, Enterprise Edition version 4.0
  • Microsoft Windows NT Server version 4.0


SYMPTOMS

If your Windows NT 4.0-based computer is configured to use the Windows Load Balancing Service (WLBS) and experiences network communications problems, multiple, duplicate messages may be written to the computer's event log. If you have auditing enabled, the event log may become filled with these messages and a new event may not be logged, even if it is from a critical service. If the event log fills to its configured capacity, the computer may stop responding (hang).


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Windows NT 4.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or later:

   Date       Time     Size      File name   Platform
   --------------------------------------------------
   10/12/99   07:44p    36,112   Wlbs.exe    x86
   10/29/99   01:06p    60,208   Wlbs.sys    x86
   10/12/99   07:43p    51,472   Wlbs.exe    Alpha
   10/29/99   01:05p   101,104   Wlbs.sys    Alpha 


STATUS

Microsoft has confirmed this to be a problem in Windows NT 4.0.

Additional query words:

Keywords : kbinterop kbnetwork ntsp kbbug4.00 kbfix4.00
Version : winnt:4.0
Platform : winnt
Issue type : kbbug


Last Reviewed: December 22, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.