WINS Consistency Checking May Not Start at Scheduled TimeLast reviewed: November 21, 1997Article ID: Q159599 |
The information in this article applies to:
SYMPTOMSConsistency Checking is not scheduled to run at the exact interval specified. For example, if Consistency Checking is set to start at 1:00AM with an interval of 24 hours, and if it takes 30 minutes to complete, it will start at 1:30PM next day rather then at 1:00 AM as expected.
CAUSEThe next scheduled time (which is based on time interval) was set after a full Consistency Checking was done. RESOLUTIONTo resolve this problem, obtain the following fix or wait for the next Windows NT service pack. This fix should have the following time stamp:
08/14/97 04:38p 191,248 Wins.exe (Intel) 08/14/97 04:37p 343,312 Wins.exe (Alpha) STATUSMicrosoft has confirmed this to be a problem in Windows NT version 4.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.
MORE INFORMATIONFor more information on Consistency Checking, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q167704 TITLE : Explanation of Windows NT 4.0 WINS Consistency Checking |
Additional reference words: 4.00
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |