A system error has occurred.

Issue #26 resolved
Former user created an issue

l[Thu 01/26/2017 23:47:24.40] ### Ancile v1.8 ################################# [Thu 01/26/2017 23:47:24.41] Created by Matthew Linton [Thu 01/26/2017 23:47:24.41] https://bitbucket.org/matthewlinton/ancile/ [Thu 01/26/2017 23:47:24.41] ##########################################################

[Thu 01/26/2017 23:47:24.43] BEGIN NTP SYNC The operation completed successfully.

The command completed successfully. The operation completed successfully.

The operation completed successfully.

The operation completed successfully.

The operation completed successfully.

The operation completed successfully.

The operation completed successfully.

[SC] ChangeServiceConfig SUCCESS The Windows Time service is starting. The Windows Time service could not be started.

A system error has occurred.

System error 2 has occurred.

The system cannot find the file specified.

The following error occurred: The service has not been started. (0x80070426) The following error occurred: The service has not been started. (0x80070426) [Thu 01/26/2017 23:47:26.59] END NTP SYNC

Comments (3)

  1. Matthew Linton

    Windows Time Service fix

    Some people have been seeing issues with Windows Time failing to sync properly. This version (1.9) of Ancile may fix this. To make sure that Windows Time is running correctly, After you have run this version of Ancile run the following command from an administrative prompt:

    C:\>w32tm /resync
    Sending resync command to local computer
    The command completed successfully.
    

    If you get the output above, everything is fine. If you get an error, you will need to fix the Windows Time Service by following the instructions below.

    From an administrative prompt run the following commands

    C:\>net stop w32time
    C:\>w32tm /unregister      <-- If this command fails try running it again
    
    [Reboot Windows]
    
    C:\>w32tm /register
    C:\>net start w32time
    C:\>w32tm /resync
    

    If the resync is successful this time then everything has been fixed.

  2. Log in to comment