You are currently offline, waiting for your internet to reconnect

Microsoft-Windows-Time-Service Event 142: The time service has stopped advertising as a time source because ...

Symptoms
Microsoft-Windows-Time-Service Event 142 is logged with one of 4 error strings listed in the table below (less the event_<hex error> string: 

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          <date> <time>
Event ID:      142
Task Category: None
Level:         Warning
Keywords:     
User:          LOCAL SERVICE
Computer:      <hostname>.<domain name>.<top level domain>
Description:
 

Error status

Error string

event_0x0038

The time service has stopped advertising as a time source because the local machine is not an Active Directory Domain Controller.

event_0x0039

The time service has stopped advertising as a time source because there are no providers running.

event_0x003A

The time service has stopped advertising as a time source because there are no providers running.

event_0x003B

The time service has stopped advertising as a good time source.


Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" />
    <EventID>142</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="YYYY-MM-DDTHH:MM:SS.MSZ" />
    <EventRecordID>3965</EventRecordID>
    <Correlation />
    <Execution ProcessID="<PID>" ThreadID="<TID>" />
    <Channel>System</Channel>
    <Computer>DC1.contoso.com</Computer>
    <Security UserID="<SID>" />
  </System>
  <EventData Name="TMP_EVENT_STOP_ADVERTISING">
  </EventData>
</Event>

Cause

  

Error string

Cause

The time service has stopped advertising as a time source because the local machine is not an Active Directory Domain Controller.

The local machine no longer host the DC role or there is a configuration problem with the local machine.

The time service has stopped advertising as a time source because there are no providers running.

 The NTP client service has stopped or is non-responsive

The time service has stopped advertising as a time source because there are no providers running.

 Time on the local computer has fallen out of sync with its peer

The time service has stopped advertising as a good time source.

 The local DC is unable to locate a time server

Resolution

The dominant error string logged by Microsoft-Windows-Time-Service Event 142 is the 3rd example:

"The time service has stopped advertising as a time source because there are no providers running."

  1. Execute the action plan in Technet's "Event ID 142 — Time Service Advertisement"

  2. Verify that the forest root PDC is online, healthy and that the current root domain PDC is both (1.) correctly configured to sync time with an external time source and (2.) able to reliably source time from that source.

  3. Verify service startup values and service state: automatic + running

  4. Verify that the DC logging the 142 event can discovery a time server using DCLocator

    >nltest /dsgetdc:<dns domain> /timeserver /force
    >nltest /dsgetdc:<dns domain> /gtimeserv /force <- if a gtimesrv is configured in the environment

  5. Verify port and protocol connetivity to peer time servers

    >w32tm /query /source

  6.  Check for the use of dueling time protocols by looking for the following events: 
     

    Microsoft-Windows-Time-Service event 35

    note the protocol + source DC in event

    Microsoft-Windows-Time-Service event 37

    <note the protocol + source DC in event

    Microsoft-Windows-Kernel-General event 1.

    The Microsoft-Windows-Kernel-General event 1 indicates that time has been changed in the VM. Every time W32time updates the clock, this event is logged. Every time Hyper-V Time Synch updates the clock, Microsoft-Windows-Kernel-General event 1 is logged. This event is not specific to VMs as it is also logged in physical machines when w32time updates the clock


  7. Other root causes

    AnnounceFlags = 10 on forest-root PDC. This setting may be explicitly set or in the registry or defined in group policy.

    If the computer logging Microsoft-Windows-Time-Service event 142 is a virtualized guest computer residing on a Hyper-V host, disable VMICTimeSync on the hyper-V host.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.
Properties

Article ID: 2468336 - Last Review: 06/05/2012 02:08:00 - Revision: 6.0

Windows Server 2008 R2 Standard, Windows Server 2008 Standard

  • KB2468336
Feedback
&t=">;did=1&t=">