Win32 Time Service Informational, Warning, and Error Messages

ID: Q232209


The information in this article applies to:
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server
  • Microsoft Windows 2000 Professional
  • Microsoft Windows 2000 Server


SUMMARY

Windows 2000 uses a new time synchronization service to synchronize the date and time of computers on a Windows 2000-based network. Synchronized time is critical in Windows 2000 because the default authentication protocol (Kerberos version 5) uses workstation time as part of the authentication ticket generation process. The Windows Time Synchronization service (W32Time) is a fully compliant implementation of the Simple Network Time Protocol (SNTP) as detailed in IETF RFC 1769 viewable at the following Web site:

http://www.ietf.org/rfcs/rfc1769.txt
The remainder of this article describes messages related to the Time Service in Windows 2000.


MORE INFORMATION

The body consists of zero or more message definitions. Each message definition begins with one or more of the following statements:

MessageId = [number|+number]
Severity = severity_name (Informational, Warning, or Error)
Facility = facility_name
SymbolicName = name

MessageId=0x0
Severity=Informational
SymbolicName=MSG_TIMESET_SMALL
Language=English
Time set (offset < .5 second)


MessageId=0x1
Severity=Informational
SymbolicName=MSG_TIMESOURCE
Language=English
Registry LanmanServer\Parameters\timesource is not set, maybe it should be set

MessageId=0x2
Severity=Informational
SymbolicName=MSG_CHANGE
Language=English
Changing TimeAdjustment from default increment (to compensate for skew)

MessageId=0x4
Severity=Informational
SymbolicName=MSG_TOO_OFTEN
Language=English
Potential for skew compensation disabled because period is too frequent

MessageId=0x5
Severity=Informational
SymbolicName=MSG_LEAP
Language=English
A leap second seemed to be inserted within the last 24 hours

MessageId=0x06
Severity=Informational
SymbolicName=MSG_TIMESET_LARGE
Language=English
Time set (offset > .5 second)

MessageId=0x07
Severity=Informational
SymbolicName=MSG_TOO_MUCH_SKEW
Language=English
Skew > 15 seconds per day, compensation not attempted

MessageId=0x0a
Severity=Warning
SymbolicName=MSG_INET_FAILED
Language=English
Couldn't reach USNO or NIST by Internet (maybe blocked by a firewall)

MessageId=0x0b
Severity=Warning
SymbolicName=MSG_NTPTROUBLE
Language=English
The NTP server %1 didn't respond

MessageId=0x0c
Severity=Warning
SymbolicName=MSG_NTPBAD
Language=English
The NTP server %1 isn't sync'd, time not set

MessageId=0x0e
Severity=Warning
SymbolicName=MSG_TOOBIG
Language=English
Attempt to set time which differs by more than 12 hours aborted

MessageId=0x0f
Severity=Warning
SymbolicName=MSG_DST
Language=English
The reference and system don't appear in sync with DST change, time not set

MessageId=0x16
Severity=Warning
SymbolicName=MSG_PRIMARY_FAILED
Language=English
NetRemoteTOD failed for each PrimarySource

MessageId=0x17
Severity=Warning
SymbolicName=MSG_SECONDARY_FAILED
Language=English
Couldn't find a timesource in SecondaryDomain

MessageId=0x18
Severity=Warning
SymbolicName=MSG_TOD_FAILED
Language=English
NetRemoteTOD failed

MessageId=0x19
Severity=Warning
SymbolicName=MSG_LONG_TIME
Language=English
It has been over 24 hours since we received a network success

MessageId=0x1a
Severity=Warning
SymbolicName=MSG_NO_DELAY
Language=English
Couldn't measure the line delay (accuracy is reduced)

MessageId=0x1c
Severity=Warning
SymbolicName=MSG_DELAY_FAIL
Language=English
Difficulty measuring network delay, check the link to your server(s)

MessageId=0x1f
Severity=Warning
SymbolicName=MSG_TOOEARLY
Language=English
Attempt to set date prior to 1995 aborted

MessageId=0x20
Severity=Error
SymbolicName=MSG_EVENT_KEY
Language=English
Could not create EventLog registry key (higher privilege needed?)

MessageId=0x21
Severity=Error
SymbolicName=MSG_EVENT_MSG
Language=English
Could not set event message file

MessageId=0x22
Severity=Error
SymbolicName=MSG_EVENT_TYPES
Language=English
Could not set supported event types

MessageId=0x23
Severity=Error
SymbolicName=MSG_SCM_FAILED
Language=English
OpenSCManager failed

MessageId=0x24
Severity=Error
SymbolicName=MSG_CS_FAILED
Language=English
CreateService failed

MessageId=0x25
Severity=Error
SymbolicName=MSG_OPT_FAILED
Language=English
OpenProcessToken failed

MessageId=0x26
Severity=Error
SymbolicName=MSG_ATPE_FAILED
Language=English
AdjustTokenPrivileges enable failed (higher privilege needed)

MessageId=0x27
Severity=Error
SymbolicName=MSG_ATPD_FAILED
Language=English
AdjustTokenPrivileges disable failed

MessageId=0x2d
Severity=Error
SymbolicName=MSG_SLT_FAILED
Language=English
SetLocalTime failed

MessageId=0x2e
Severity=Error
SymbolicName=MSG_SST_FAILED
Language=English
SetSystemTime failed

MessageId=0x30
Severity=Error
SymbolicName=MSG_SSS_FAILED
Language=English
SetServiceStatus failed

MessageId=0x32
Severity=Error
SymbolicName=MSG_WNOE_FAILED
Language=English
WNetOpenEnum failed

MessageId=0x33
Severity=Error
SymbolicName=MSG_SOCKET_FAILED
Language=English
Invalid socket (TCP/IP might not be loaded)

MessageId=0x34
Severity=Error
SymbolicName=MSG_NTP_NAME
Language=English
gethostbyname failed for server %1 (NTP or USNO)

MessageId=0x35
Severity=Error
SymbolicName=MSG_BAD_SIGNATURE
Language=English
NTP server %1 (%2) returned an incorrectly signed time stamp.

MessageId=0x36
Severity=Error
SymbolicName=MSG_NO_DC_LOCATED
Language=English
The Windows Time Service was not able to find a Domain Controller. A time and date update was not possible.

MessageId=0x37
Severity=Informational
SymbolicName=MSG_NEW_DC_LOCATED
Language=English
New DomainController time source is %1 (%2) located in %3

MessageId=0x38
Severity=Error
SymbolicName=MSG_BAD_DC_SIGNATURE
Language=English
The Domain Controller %1 (%2) in %3 returned an incorrectly signed time stamp. If this\nDC is from the machine's parent domain then the trust link between the domains may be broken and must be fixed. If the DC is from this machine's own domain, then the machine password for this machine is incorrect and should be corrected.

MessageId=0x39
Severity=Error
SymbolicName=MSG_NODLL_IN_REGISTRY
Language=English
Service configuration is for a third-party DLL but the DLL name is not in the registry.

MessageId=0x3a
Severity=Error
SymbolicName=MSG_DLL_LOAD_FAILED
Language=English
The DLL for time sync does not have the proper entry point.

MessageId=0x3b
Severity=Warning
SymbolicName=MSG_NO_XSUM
Language=English
The NetLogonComputeServerDigest call returned an error. This is an internal failure but it will prevent this machine from providing correctly signed time.

MessageId=0x3c
Severity=Warning
SymbolicName=MSG_NTPNOXSUM
Language=English
The NTP time source %1 (%2) returned an unsigned time stamp. This likely means that the server experienced an internal failure. Please check the event log on that server.

Additional query words:

Keywords : kbtool
Version : WINDOWS:2000
Platform : WINDOWS
Issue type : kbinfo


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