Nonstop Time-Service Event 35 and 37 - Server 2016 / HyperV Role

Rootaah 0 Reputation points
2023-01-30T16:16:28.8166667+00:00

Fully updated Windows 2016 Standard / HyperV role installed. Hosted VMs are simple RDS servers and do not have Time Syncronization enabled. HV gets time from public site, VMs from local DC. Patched over the weekend and as of this morning, the SYSTEM event logs of the HV host are being constantly updated with informational EVENT IDs 35 and 37 Time-Service. I'm not seeing any related issues or problems, but this stood out as something very odd. It was not happening prior to patching this weekend (01/28/2022). Other similar servers that I have looked at are not flagging these information events like this in such a repeating fashion. I've even changed the time service to a different one, such as time.windows.com, etc...and same thing.

TIME

TIME2

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,528 questions
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,738 questions
{count} votes

5 answers

Sort by: Most helpful
  1. Anonymous
    2023-01-30T16:36:18.4866667+00:00

    I see the log is filtered. What else is in there error-wise?


  2. Anonymous
    2023-01-31T22:48:31.0833333+00:00

    Might try resetting things.

    w32tm /unregister
    net stop w32time
    w32tm /register
    net start w32time
    w32tm /config /manualpeerlist:<ntp ip address> /syncfromflags:manual /reliable:yes /update
    net stop w32time
    net start w32time
    #then check
    w32tm /query /source
    w32tm /query /configuration
    
    

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  3. Anonymous
    2023-02-01T01:46:42.6133333+00:00

    What are the 7036's ? Does it happen to be the Windows Time service?


  4. Anonymous
    2023-02-03T15:33:00.83+00:00

    Well, yes, we know something is causing it. The problem is what. There has to be some trouble shooting steps in order to figure things out and standing up a new virtual machine should be a fairly simple process. But if you can't for some reason then you can't. A wild guess from here (nothing to base this on because of no trouble shooting steps) is that it is something network related, or possible ISP related, but we may never know. You could also start a case here with product support.

    https://support.serviceshub.microsoft.com/supportforbusiness

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  5. Anonymous
    2023-02-03T20:21:09.3333333+00:00

    Ok, that's good info. If it were me, I'd save the $500 support call and export / move the VMs off to removeable, clean install host, patch fully, add hyper-v role, import VMs, and move on.

    --please don't forget to upvote and Accept as answer if the reply is helpful--


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.