Do you have any related errors in the event logs? Have you tried this:

Ensure that the Windows Time service can read its registry configuration settings

To ensure that the Windows Time service can read its registry configuration settings:

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

1. Open Registry Editor. To open Registry Editor, click Start. In Start Search, type regedit, and then press ENTER. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
2. Go to the Config key in the registry by expanding the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time.
3. Right-click the Config key, and then click Permissions. The Permissions for Config dialog box opens.
4. On the Security tab, under Group or user names, ensure that the W32Time account is listed.
5. Click the Advanced button. The Advanced Security Settings for Config dialog box opens.
6. Select the W32Time account in the list of permission entries.
7. Click Edit. The Permission Entry for Config dialog box opens.
8. In the Permission Entry for Config dialog box, ensure that W32Time has the following permissions selected in the Allow column: Query Value, Set Value, Create Subkey, Enumerate Subkeys, Notify, Delete, and ReadControl. If any of those permissions are not set to Allow, select the box next to the appropriate permission in the Allow column. Ensure that there is nothing selected in the Deny column.
9. If you made any changes, click OK. Otherwise, click Cancel. The Permission Entry for Config dialog box closes.
10. Click OK in the Advanced Security Settings for Config dialog box.
11. Click OK in the Permissions for Config dialog box.

I checked everything and it was identical! I tried rerunning the cmd w32tm /query /configuration and the same error, very frustrating.

The following error occurred: Access is denied. (0x80070005)

Hi,

Please also check the similar thread:

w32tm Access is denied. (0x80070005) from elevated prompt        

http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/9bdfc2cc-4775-4435-8868-57d214e1e3ba

If you have any feedback on our support, please click here

Regards.

Hi,

Please also check the similar thread:

w32tm Access is denied. (0x80070005) from elevated prompt        

http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/9bdfc2cc-4775-4435-8868-57d214e1e3ba

Regards.

Hi,

Have you seen any error related to W32TM in the event log? Also, please try to boot the sever into safe mode with network and then verify if this issue happens again.

Hi,

Have you seen any error related to W32TM in the event log? Also, please try to boot the sever into safe mode with network and then verify if this issue happens ag

I thought that by changing the w32time to a shared process it would work, no if failed to start.

C:\Windows\System32>.\net stop w32time
The Windows Time service is stopping.
The Windows Time service was stopped successfully.

C:\Windows\System32>.\sc config w32time type= share
[SC] ChangeServiceConfig SUCCESS

C:\Windows\System32>.\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.

I changed the service back to own and it started.

C:\Windows\System32>.\sc config w32time type= own
[SC] ChangeServiceConfig SUCCESS

C:\Windows\System32>.\net start w32time
The Windows Time service is starting.
The Windows Time service was started successfully.

HI,

Please take a look at following links

http://support.microsoft.com/kb/2512643 

http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/aaee7dec-d1a9-4f8a-a1c1-ee24ff08f0

HI,

Please take a look at following links

http://support.microsoft.com/kb/2512643 

http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/aaee7dec-d1a9-4f8a-a1c1-ee24ff08f0

Did you try running a sfc /scannow?

Also I would try exporting the win32tm reg key from a working computer and importing it. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time

Did you try running a sfc /scannow?

Also I would try exporting the win32tm reg key from a working computer and importing it. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W

Hi,

We may need  more logs to troubleshoot this issue, so please create a case to MS support team. They will help you solve this issue.

 please create a case to MS support team. They will help you solve this is

HI,

It requires your SA agreement, so it needs you pay if you don't have SA agreement. 

HI,

It requires your SA agreement, so it needs you pay if you don't have SA agreement.

Anyone else having this problem and unable to resolve it?  I've tried all of the recommended solutions listed in this thread (as well as the other threads that are linked from this one) and cannot query w32time using w32tm.exe whatsoever.  I continually get the "Access is denied. (0x80070005)" error.  I can verify from the Event Viewer that the service is, in fact, running properly and querying AD for a domain controller to sync time with, but without the use of w32tm.exe, I have no way of querying the service to see what it is doing.  This is happening on two different physical WS08R2 boxes.  Thoughts?

FWIW, these are both non domain controllers that are members of the same domain.

We recently made widespread time changes by removing a GPO that was manually pointing all domain members (including DCs) to a local NTP appliance (against MS best practices), and instead, allowing w32time to query AD find the appropriate time provider.  This has been a really painstaking task -- with a lot of these systems, w32time does not want to "forget" the original/manually configured NTP source.  It has required everything from w32tm /config /syncfromflags:domhier /update to w32tm /unregister then /register to flush out the old settings entirely, and allow the service to do what it's supposed to do.

Everyone seems to suggest the sc config procedure, repeating the /unregister /register steps, rebooting, and checking the registry permissions, all unsuccessfully.  Some folks start suggesting commands to run within w32tm.exe, which I believe to be down the wrong path -- the logical configuration of our time is correct now (and the event 35 from the time system confirms this) -- this is simply the ability to use the diagnostic w32tm.exe tool.

It has now happened to a fourth machine and I think I've found some repeatable behavior to report:

1. These are all WS08R2.
2. On at least two of these boxes, after a reboot, the Windows Time service has disappeared altogether.  Just gone.
3. I run w32tm /register which causes the service to be created.
4. I try net start w32time and get this result: 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.
5. I run sc config w32time type= own, which completes successfully: [SC] ChangeServiceConfig SUCCESS
6. Then I net start w32time, and the service starts OK.  I get an Information event 37 followed by a 35 from Time-Service, indicating that w32time has found a time source in AD and is now sync'ing,
7. But when I use w32tm to do something like w32tm /query /status, I get: The following error occurred: Access is denied. (0x80070005)

I can't explain it.  The time service is actually working, but I can't do a whole lot to troubleshoot with it.  Interestingly, however, a command like /stripchart does work, but anything having to do with /query gives me the aforementioned access denied error.

I found similar and when I ran sc config w32time type= own the service really does not want to be set to own, it wants to be set to shared but it won't run that way eith

Charlie -- give this a go when you have chance (all as administrator, of course):

1. stop w32time
2. w32tm /unregister
3. reboot
4. regsvr32 /u w32time.dll
5. w32tm /register
6. sc query w32time -- you should see that the service is set to shared mode -- this is presumably how it should be -- if you try to start right now, you'll get the expected 1290 SID-related error
7. reboot
8. w32time should now automatically start at boot up and be running -- that was my result -- it's running as shared, started on its own, and I can do the w32tm /query commands successfully

Charlie -- give this a go when you have chance (all as administrator, of course):

1. stop w32time
2. w32tm /unregister
3. reboot
4. regsvr32 /u w32time.dll
5. w32tm /register
6. sc query w32time -- you should see that the service is set to shared mode -- this is presumably how it should be -- if you try to start right now, you'll get the expected 1290 SID-related error
7. reboot
8. w32time should now automatically start at boot up and be running -- that was my result -- it's running as shared, started on its own, and I can do the w32tm /query commands successfully

Please do.  I just tried it on the second machine that was having issues and it fixed the problem.  One notable thing is that if you try running step #4 before #3, you'll get an error about unregistering the DLL....so I'm thinking that the w32tm /unregister step is not able to fully complete w/o a reboot first.

Charlie -- give this a go when you have chance (all as administrator, of course):

1. stop w32time
2. w32tm /unregister
3. reboot
4. regsvr32 /u w32time.dll
5. w32tm /register
6. sc query w32time -- you should see that the service is set to shared mode -- this is presumably how it should be -- if you try to start right now, you'll get the expected 1290 SID-related error
7. reboot
8. w32time should now automatically start at boot up and be running -- that was my result -- it's running as shared, started on its own, and I can do the w32tm /query commands successfully

Thanks for this Ben, fixed the problem for me.

dave

Hey,

this works for me... thanks

Vaibahv

Many Thanks Ben,

Special thanks to CJ for posting this problem that has plagued me for over a year.

Ben, your solution is the missing piece to this puzzle.

Many thanks to both of you.

Raul