In Windows Server 2003 and in Windows XP, W32Time frequently logs Event ID 50, and poor time synchronization occurs (830092)



The information in this article applies to:

  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Server 2003, Standard Edition
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, 64-Bit Enterprise Edition
  • Microsoft Windows XP Home Edition
  • Microsoft Windows XP Professional
  • Microsoft Windows XP 64-Bit Edition Version 2003
  • Microsoft Windows XP Professional 64-Bit Edition (Itanium) 2003

Windows SE:157501

SYMPTOMS

When the Windows Time service (W32Time) synchronizes with an external clock, the following event may frequently appear in the System log:
Event ID: 50
Source: W32time
Type: Warning
The time service detected a time difference of greater than 5000 milliseconds for 900 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself. In the default domain hierarchy, when a Microsoft Windows Server 2003-based child domain controller tries to synchronize the time, you may receive the following event messages:
Event ID: 38
Source: W32time
Type: Information
The time provider NtpClient cannot reach or is currently receiving invalid time data from yourpdc.forestroot.com (ntp.d|65.53.232.135:123->65.53.250.22:123).
Event ID: 47
Source: W32time
Type: Warning
Time Provider NtpClient: No valid response has been received from manually configured peer yourpdc.forestroot.com after eight attempts to contact it. This peer will be discarded as a time source, and NtpClient will attempt to discover a new peer with this DNS name.
Event ID: 29
Source: W32time
Type: Error
The time provider NtpClient is configured to acquire time from one or more time sources. However, none of the sources are currently accessible. No attempt to contact a source will be made for 15 minutes. NtpClient has no source of accurate time. Note Event ID 29 may also occur on Windows XP-based computers.

RESOLUTION

Service Pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Server 2003, 32-bit editions
   Date         Time   Version       Size     File name
   ------------------------------------------------------
   31-Jan-2004  02:15  5.2.3790.125  221,696  W32time.dll
Windows Server 2003, 64-bit edition
   Date         Time   Version       Size     File name
   ------------------------------------------------------
   30-Jan-2004  17:15  5.2.3790.125  554,496  W32time.dll
Windows XP, 32-bit editions
   Date         Time   Version        Size     File name
   --------------------------------------------------------
   19-Apr-2005  02:54  5.1.2600.1668  166,400  W32time.dll
   25-Feb-2005  03:53  6.1.22.4       371,936  Updspapi.dll
Windows XP, 64-bit editions
   Date         Time   Version        Size     File name     Platform
   -------------------------------------------------------------------
   19-Apr-2005  02:51  5.1.2600.1668  437,760  W32time.dll   IA-64
   19-Apr-2005  02:54  5.1.2600.1668  166,400  Ww32time.dll  x86
   25-Feb-2005  03:50  6.1.22.4       639,712  Updspapi.dll  IA-64
Important Microsoft recommends that you install this hotfix on all Windows Server 2003 domain controllers. Start by installing this hotfix on the primary domain controller that is the operations master in the root directory of the forest. If you experience this problem only on member servers, install the hotfix on domain controllers first and then install the hotfix on the member servers.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This bug was corrected in Windows Server 2003 Service Pack 1.

MORE INFORMATION

Microsoft recommends that you synchronize the primary domain controller with multiple external Stratum 1 Network Time Protocol (NTP) servers. You should leave all other domain controllers and member servers unchanged. In the default configuration, these servers will synchronize the time with the domain hierarchy.

For additional configuration and deployment suggestions for the Windows Time service in a forest, visit the following Microsoft Web site:
http://technet2.microsoft.com/windowsserver/en/library/a0fcd250-e5f7-41b3-b0e8-240f8236e2101033.mspx

Modification Type:MajorLast Reviewed:5/10/2006
Keywords:kbHotfixServer kbBug kbfix kbQFE kbWinServ2003preSP1fix KB830092 kbAudITPRO