Re: Windows Server 2003 Time Service Error

Giganews Newsgroups
Subject: Re: Windows Server 2003 Time Service Error
Posted by:  Bill (it_professional_0812 at yahoo.com)
Date: Fri, 31 Mar 2006

If you are Server 2003 SP1, the time service not starts as "local service"
instead of "local system".  Change your policy so that "local service" has
"logon as service" and "change system time" permissions.

"Gibson710" <bgibson7…@gmail.com> wrote in message
news:1143823710.485353.301…@z34g2000cwc.googlegroups.com...
> Okay this all began when we took down a windows 2000 Server, formatted
> it, and then installed Windows Server 2003 Standard on it.  We did
> demote the old server out of the AD before formatting, however when we
> brought up the new server (gave it a different name) it had to have the
> same IP address (we have limited few to use for servers with internet
> access).  There were some replication errors at first, which seem to
> have worked themselves out.  However there are 4 services that show up
> failed everytime I run a DCDIAG on it.
>
> rpclocator
> w32time
> TrkWks
> TrkSrv
>
> I am able to manually start the RPClocator, but w32time gives me an
> event 7000 error in the system log.
>
> The full error text is as follows:
>
> The Windows Time Service failed to start due to the following error:
> The executable program that this service is configured to run in does
> not implement the service.

Replies

In response to

Windows Server 2003 Time Service Error posted by Gibson710 on 31 Mar 2006