Link to home
Create AccountLog in
Avatar of Thomas N
Thomas NFlag for United States of America

asked on

Trying to start time server on domain controller and it errors out.

I am running 2008R2 .I try to start "Windows Time" service and it errors with message below.

"Error 1058: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it"

I try to change some settings on the actual service and I get error:
"The specified service has been marked for deletion"

Anybody have any idea what I should do? I have searched and tried editing the registry "w32time","tapisrv" registry key. I tried registering W32tm but says it is marked for deletion.
Avatar of Shaun Vermaak
Shaun Vermaak
Flag of Australia image

Close Services.msc snap-in and run
w32tm /register

Open in new window

If that doesn't work, restart and run register command
ASKER CERTIFIED SOLUTION
Avatar of K B
K B
Flag of United States of America image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
Avatar of Thomas N

ASKER

I type in net stop w32time and it tells me the service name is invalid.

I tried typing in w32tm /register and it tells me "the specified service has been marked for deletion"
try to unregister it? from elevated command prompt?
SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Is the service disabled?  if so set to automatic

edit: i see you get this: "The specified service has been marked for deletion"
if you can't unregister I agree with Shaun, you will probably need a reboot.
Okay so I  "regsvr32 wuapi.dll" and now it allows me to run w32tm /register. So I try to go through KB's suggestion and it I try to run "net stop w32time" and it gives me access denied.

Maybe a reboot will help? I cant reboot this machine until after hours though.
Please see my video. If commands do not work initially, restart
http://screencast-o-matic.com/watch/cbfrb5X6lc
SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Glad we could help.

@OP, experts and future visitors:
Please remember to endorse my, or any other expert's comments that you found helpful by clicking on the "Thumb's Up" button

Read more on endorsements
https://www.experts-exchange.com/discussions/218503/What-are-Endorsements.html
@Thomas N

For the benefit of future readers, ultimately, what was the solution?
•      Deleted the registry key: W32Time from the location: HKLM\SYSTEM\CurrentControlSet\Services.

•      Refreshed the services.msc console so that the w32time service was not listed in the console.

•      Attempted to register the w32time service using the command below:
Z:\>w32tm /register
W32Time successfully registered.

•      separated the w32time service into a separate svc instance using the command below:
C:\> sc config w32time type= own

•      Attempted to restarted w32time service --------- able to start the service

•      Verified that the PDC is fetching the time from time.windows.com from the Windows time debug logs
152051 20:08:40.4784306s - Logging information: The time service is now synchronizing the system time with the time source time.windows.com,0x8 (ntp.m|0x8|0.0.0.0:123->13.65.245.138:123).
152051 20:09:30.0294760s - ListeningThread -- response heard from 13.65.245.138:123 <- 165.184.59.9:123

•      Attempted to run the commands below:
C:\>w32tm /query /source
C:\>w32tm /resync
C:\>w32tm /resync /rediscover
Which resulted in the error - The following error occurred: Access is denied. (0x80070005). ------------------- Known issue as an attempt was made to re-register the w32time service.

Next Steps:



1.      Run the command below:
C:\> sc config w32time type= share

2.      Run a w32tm /resync command and see if it’s successful.

3.      Reboot the PDC.