Solution Easy Fix W32time Error ID 14

You may encounter an error stating error ID 14 w32time. There are several ways to solve this problem, and we will look at that in a moment.

Keep track of unlimited servers
Log events filter
Create reports by email and on the web

Direct access to articles from Microsoft
Custom keywords for major search engines
Access to premium content

Event ID: 14 ​​Source: W32Time

Description

The NtpClient time provider could not find a domain controller that can be used as a time source. NtpClient will retry in 15 minutes.

This information is not available to you. Use other websites to find free information.

Splunk Windows Event Log Analysis Application

Build a great reporting interface with Splunk, a leading security information and event management (SIEM) provider that connectsPulls collected Windows events from www.eventid.net.

Learn more …

Cisco ASA Log Analyzer Splunk Application

Free Firegen for Cisco ASA Splunk provides better visibility to Cisco ASA firewall logs. Take advantage of dashboards designed to streamline your threat intelligence process.

Learn more …

Reason

On a host server running Windows Server 2008 with Hyper-V, virtualized domain controllers running in the guest operating system can synchronize their system clock with the host operating system clock. The events that are listed in the Symptoms section are logged in the syslog because domain controllers have their own time synchronization mechanism. Can domain controllers synchronize domain controller time with their own and host source. Controller Tasks domains are associated with system time, a jump in system time can cause objects to remain in the cache and stop replication.

Resolution

The third example is This is the main error line recorded by Microsoft Windows Time Service event 142:

“Time Service stopped serving ads as a time source because no provider is running.”

1. Run the action plan in technets “ Event ID 142 – Time Service Advertising “

2. Ensure that the forest root PDC is online and healthy, and that the current PDC of the root domain (1.) is properly configured to synchronize time with an external time source and (2.) can reliably receive time from that source.

3. Check service startup values ​​and service status: running automatically

4. Verify DC registration event 142 can be detected by the time server using DCLocator

   nltest / dsgetdc: / timeserver / force
   nltest / dsgetdc: / gtimeserv / force <- if gtimesrv is configured in environment

5. Check port and protocol connections to even-time servers

   w32tm / query / source

6. Check your use of duel time logs by looking for the following events:

   Service Eventtime Microsoft Windows 35	note the log event source domain controller
   Microsoft Windows Time Service Event 37
   Microsoft Windows Generic Event 1	Microsoft-Windows-Kernel-General-Event 1 indicates that the virtual machine time has changed. This event is logged every time W32time updates the clock. Microsoft-Windows-Kernel-General-Event 1 is logged every time Hyper-V time sync updates the clock. This event is not relevant to virtual machines as it is also logged on physical computers when w32time updates the clock.

7. Other reasons

   AnnounceFlags = 10 on the forest root domain controller. This parameter can be set explicitly, in the registry, or in Group Policy.

   If the computer logging the Microsoft Windows Time Service event 142 is a virtualized guest computer that is on the Hyper-V host, disable VMICTimeSync on the Hyper-V host.