Net Start W32time System Error 1290
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered error 1290 mysql by: system error 1290 after register w32time service Windows
Error 1290 Windows Update Service
Server > Windows Server General Forum Question 0 Sign in to vote Hello all I'm
W32tm /resync Access Is Denied
getting a system error 1290, when i try to use the command "net start w32time". The output from cmd looks like this: System error
W32tm /query /status Access Denied
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 error 1290 the service start failed windows update SID type for this service was just configured, the hosting process must be restarted in order to start this service. How do i recover from this error? Tuesday, October 19, 2010 7:53 AM Reply | Quote Answers 15 Sign in to vote Troubleshooting an unrelated issue, I think I've finally found the solution to this error (sometimes, rebooting also fixes this specific error). See the underlined command below, and mind the required space between = and own. The command puts the w32time service in it's own svchost process, so it doesn't have to share the process with other services which may have been configured with an service SID type incompatible with w32time's. Running the following from an elevated command prompt seems to be a pretty surefire way to fix your Windows Time service. pushd %SystemRoot%\system32.\net stop w32time.\w32tm /unregister.\w32tm /register.\sc
be down. Please try the request again. Your cache administrator is webmaster. Generated Wed, 19 Oct 2016 14:13:57 GMT by s_ac5 (squid/3.5.20)
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow http://serverfault.com/questions/378161/time-service-will-not-start-on-windows-server-system-error-1290 the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join http://www.worldtimeserver.com/atomic-clock/solutions-to-time-service-problems.aspx them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Time Service will not start error 1290 on Windows Server - System error 1290 up vote 2 down vote favorite I have been trying to sort out some time sync issues involving two domain controllers and seem to have ended up with a bigger problem. It's horrible. They are both virtual machines (one being on Amazon EC2), which I think may complicate things regarding time servers. The primary DC with all the FSMO roles is on the LAN. I reset its net start w32time time server configuration like this (from memory): net stop w32time w23tm /unregister shutdown /r /t 0 w32tm /register w32tm /config /manualpeerlist:”0.uk.pool.ntp.org,1.uk.pool.ntp.org,2.uk.pool.ntp.org,3.uk.pool.ntp.org” /syncfromflags:manual /reliable:yes /update W32tm /config /update net start w32time reg QUERY HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config /v AnnounceFlags I checked to see if it was set to 0x05, which it was. The output for... w32tm /query /status Leap Indicator: 0(no warning) Stratum: 1 (primary reference - syncd by radio clock) Precision: -6 (15.625ms per tick) Root Delay: 0.0000000s Root Dispersion: 10.0000000s ReferenceId: 0x4C4F434C (source name: "LOCL") Last Successful Sync Time: 10/04/2012 15:03:27 Source: Local CMOS Clock Poll Interval: 6 (64s) While this was not what was intended, I thought I would sort it out after I made sure that the remote DC was syncing with it first. On the Amazon EC2 remote replica DC (Windows Server 2008 R2 Core)... net stop w32time w32tm /unregister shutdown /r /t 0 w32time /register net start w32time This is where it all goes wrong 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 pro
capability to repair the Windows Time Service in by stopping, unregistering, registering and restarting the service. Unfortunately, there is a potential problem that has been confirmed by Microsoft for users with Windows 7, Windows Vista, Windows Server 2008 R2, and Windows Server 2008. When you attempt to start the time service, some users will receive an error claiming the service could not be started. There are a few errors that all seem to end up with a similar solution: Message 1 Windows could not start the Windows Time Service on Local Computer. Error 1290: 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. Message 2 The Windows Time service failed to start due to the following error: 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. Message 3 Error 1079: The account specified for this service is different from the account specified for other services running in the same process Solution Using Atomic Clock Sync, unregister and re-register the Time Service. When you unregister the W32Time service, Microsoft clears all the current registry values guiding the sync process. When you re-register the W32Time Service, Microsoft sets everything back to their default values. One of these default values sets the system account used to run the service to "Local Service". The problem is that this Local Service account also needs an appropriate password to run. Click Start, type "Services.msc" in the Search programs and files box, and then press ENTER. (Alternatively, go to your Control Panel, launch Administrative Tools, then launch Services.) Find the Windows Time service on the list and double-click to edit the properties. Go to the tab at the top for Log On. "This account" should be selected, NOT Local System