|
it
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
7023 - Windows Time Service - Not all privileges referenced are assigned to the callerwindows time service starts. Event Type: Error Event Source: Service Control Manager Event Category: None Event ID: 7023 Description: The Windows Time service terminated with the following error: Not all privileges referenced are assigned to the caller. I found a MSKB article on the error: http://support.microsoft.com/default.aspx?scid=kb;en-us;892501 However both the resolutions did not work. I initially tried method 1 and modified the domain controller security policy and then told the service to start, but got the same error. I then tried method 2 and set it to use LocalSystem and I get a completely different error. "The account specified for this service is different from the account specified for other services running in the same process." I also tried to set it to use my account and got the same error, now I'm screwed because I can't set it back to NT AUTHORITY\LocalService since I don't have a clue what the password is and there's not chance to start it up while its not using the same account as the other services. Anyone have any idea what I can do here to fix this? I've upgraded other servers to SP1 and never ran into this problem, so I'm not sure why mine was even doing this, but I guess now I've got to find out how to get the service set back to the proper account too. Ugh. Thanks, mike If you set it back to "NT AUTHORITY\LocalService" and leave the password
blank it'll fill the password in for you, then if you've given LocalService rights to change the system time it should start OK. I had the same problem on one of my DCs peter Lawton Show quoteHide quote "Mike" <istan@alltel.net.No.Spam.Please> wrote in message news:%23d$raW0SFHA.1040@TK2MSFTNGP10.phx.gbl... > After upgrading my W2K3 PDC to SP1, I'm now getting this error when the > windows time service starts. > > Event Type: Error > Event Source: Service Control Manager > Event Category: None > Event ID: 7023 > Description: > The Windows Time service terminated with the following error: > Not all privileges referenced are assigned to the caller. > > I found a MSKB article on the error: > > http://support.microsoft.com/default.aspx?scid=kb;en-us;892501 > > However both the resolutions did not work. I initially tried method 1 and > modified the domain controller security policy and then told the service > to start, but got the same error. I then tried method 2 and set it to use > LocalSystem and I get a completely different error. > > "The account specified for this service is different from the account > specified for other services running in the same process." > > I also tried to set it to use my account and got the same error, now I'm > screwed because I can't set it back to NT AUTHORITY\LocalService since I > don't have a clue what the password is and there's not chance to start it > up while its not using the same account as the other services. > > Anyone have any idea what I can do here to fix this? I've upgraded other > servers to SP1 and never ran into this problem, so I'm not sure why mine > was even doing this, but I guess now I've got to find out how to get the > service set back to the proper account too. Ugh. > > Thanks, > mike > > If you set it back to "NT AUTHORITY\LocalService" and leave the password Thanks Peter, i was able to get it to work!> blank it'll fill the password in for you, then if you've given > LocalService rights to change the system time it should start OK. > > I had the same problem on one of my DCs laters, mike
Other interesting topics
|
|||||||||||||||||||||||