Multiple error messages that are similar to Event ID: 29 may occur when you work on a Microsoft Cluster Service (MSCS) cluster that is running Microsoft Windows Server 2003

Consider the following scenario:

• You work on a Microsoft Cluster Service (MSCS) cluster that is running Windows Server 2003.
• One of the virtual groups in this cluster owns more than two virtual Internet Protocol (IP) addresses.

When this scenario occurs, multiple error messages that are similar to the following are logged in the System log:

Event Type: Error
Event Source: W32Time
Event ID: 29
Description: 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 The number of error messages that are logged in the System log depends on the number of IP addresses that are declared on the virtual group.

Windows Time Server (W32Time) updates the peerlist when the network topology changes. When a fail over happens in the Cluster service, the network topology changes. When a network adapter is assigned multiple IP addresses, a "W32Time Event ID 29" error may be logged. This is because of a timing issue that occurs when the peerlist is updated.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
In this scenario, time synchronization succeeds. You can safely ignore the "W32Time Event ID 29" error.

If W32Time is currently working in NT5DS mode, changing the type to Network Time Protocol (NTP) may resolve the issue. To change the server type to NTP, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\
3. In the right pane, right-click Type, and then click Modify.
4. In the Edit Value box, type NTP under Value data, and then click OK.

For more information, visit the following Microsoft TechNet Web sites:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.