Time problems after power outage

I am running a Windows 2008 Server as my PDC. Everything with it seems OK, except I can't keep time services running.  As a matter of fact, the service keeps disappearing!

C:\Users\administrator.XXXEX>dcdiag /q
         Warning: XXXOPS is not advertising as a time server.
         ......................... XXXOPS failed test Advertising
            Could not open w32time Service on XXXOPS, error 0x424
            "The specified service does not exist as an installed service."
         ......................... XXXOPS failed test Services
         Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
         A Time Server could not be located.
         The server holding the PDC role is down.
         Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355
         A Good Time Server could not be located.
         ......................... xxxex.int failed test LocatorCheck
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


This looks like an issue with name resolution.

If you look for the w32tm service in Services.msc - is it there and is the status running?

Does an nslookup of the domain name return the correct ip addresses of the DCs in the domain? e.g. nslookup xxxex.int


Run below Commands on your PDC
Refer below article for descriptions

w32tm /register
net start w32time
net stop w32time & net start w32time
w32tm /config /manualpeerlist:pool.ntp.org /syncfromflags:manual /reliable:yes /update
w32tm /resync /rediscover
net stop w32time & net start w32time 

Open in new window

You should remove the existing NTP configuration completely by issuing "w32tm /unregister"  and reconfigure it as required:
net stop w32time
w32tm /unregister
w32tm /register
net start w32time
w32tm /config /manualpeerlist:"0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org” /syncfromflags:manual /reliable:yes
net stop w32time && net start w32time

Open in new window

Only run this on your PDC emulator, leave all other servers and PCs to update via the domain hierarchy.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

SandeshdubeySenior Server EngineerCommented:
In addition also ensure that latest hotfix for windows time is installed.Check this link if applicable install the same.http://support.microsoft.com/kb/2493006

Also unregister/register w32time as suggested above and configure authorative time server role on PDC.http://support.microsoft.com/kb/816042.Ensure udp port 123 is also open.
Hmmm - looks like just another W32time incarnation that got hickups. From my experience, W32time is a constant source of annoyance - esp. when used in NTP mode.

My recommendation:

Retire W32time, use a Windows port of the classic NTP service, sync a master with an external source (i.e. from pool.ntp.org) and sync the clients to the master. The NTP service software is free. Easy to install and configure, works like a charm and is stable as a rock.

This would also separate the "PDC/BDC" role from the "Timekeeper" role and - if the clients are set up to do so - would allow more redundancy in timekeeping. For maximum reliability let all stations (both DCs and clients) sync directly to servers from pool.ntp.org.

See this article for the "How To".
Given one of the other errors in the snipet of the output of DCDiag is "The server holding the PDC role is down."
It suggests to me that this isnt a case of an issue with w32tm service itself, but rather it is an issue of establishing connectivity with the w32tm service - and others.

In addition to the NSLookup :

Is that DCdiag taken from the PDC itself? Or from a remove client/server?

Is the DC on physical hardware or virtual.

skkinneyAuthor Commented:
The DCdiag was taken from the PDC itself.  The DC is physical hardware not virtual.  

C:\Users\administrator.XXXEX>w32tm /register
W32Time successfully registered.

C:\Users\administrator.XXXEX>net start w32time
System error 1290 has occurred.

The service start failed since one or more services in the same process have an incompatible service  SID type setting. A service with restricted service SID type can only coexist in the same process with other services with a restricted SID type. If the service SID type for this service was just configured, the hosting process must be restarted in order to start this service.

C:\Users\administrator.XXXEX>w32tm /unregister
The following error occurred: Access is denied. (0x80070005)
In that case, I'd agree with the suggestions from sarang_tinguria and n-w, including a reboot and checking that the service is set to "Automatic (delayed start)".
Register again and reboot the server and run remaining commands
SandeshdubeySenior Server EngineerCommented:
No need to re-register again just reboot the server once the windows service will be started mode after reboot.I have seen this issue many time and reboot as always done the trick.After reboot in case if w32time service is not present just execute w32tm /register and start windows time by net start w32time.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.