The information in this article applies to:
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe. SYMPTOMSYou may be unable to synchronize the time against a time source on your cluster. You cannot use the Timeserv utility from the Resource Kit because its name is already being used by the cluster Timeserv service. CAUSEThe Timeserv service used in clustering is designed only to provide a consistent cluster-wide time, but does not allow real-time synchronization. Note that this service is not mandatory for cluster reliability purposes and can be deleted to use Resource Kit utilities such as Timeserv or W32Time instead. RESOLUTIONWARNING: Using Registry Editor incorrectly can cause serious problems that
may require you to reinstall your operating system. Microsoft cannot
guarantee that problems resulting from the incorrect use of Registry Editor
can be solved. Use Registry Editor at your own risk.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services ftp://ftp.microsoft.com/reskit/y2kfix/ STATUSMicrosoft has confirmed this to be a problem in Windows NT 4.0, Enterprise Edition. MORE INFORMATION
The Timeserv and W32Time Resource Kit utilities use .ini files to configure their role and primary time source, and run as services.
ftp://ftp.microsoft.com/reskit/y2kfix/For more information about how Microsoft products are affected by year 2000 (Y2K) issues, please see the following Microsoft World Wide Web site: http://www.microsoft.com/year2000/ Additional query words:
Keywords : kbtool |
Last Reviewed: November 2, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |