If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Windows Time Service will not start
When I try starting it I see this error:
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. Google found some suggestions, including one that would appear to solve the problem by divorcing the time service from the "other services". I ran the sc command to change this (type= own) and it succeeded but the problem persists. |
Ads |
#2
|
|||
|
|||
Windows Time Service will not start
Jason wrote:
When I try starting it I see this error: 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. Are you logged in using an admin-level Windows account when trying to start/stop services? Each account has a SID (Security Identifier) assigned to it. The SAM (Security Accounts Manager) database determines what privileges your account's SID will have. Google found some suggestions, including one that would appear to solve the problem by divorcing the time service from the "other services". When I go into services (services.msc) and look at the Dependencies tab for the "Windows Time" services, no dependencies are listed. Other than dependencies, I don't know what your term "divorcing" means. When I look at the Log On tab, the Windows Time service starts under the Local Service account. You can run "control.exe userpasswords2", Advanced tab, and click on Advanced User Management (not available in Home editions). See: http://windowsitpro.com/systems-mana...rvice-accounts |
#3
|
|||
|
|||
Windows Time Service will not start
On Mon, 28 Sep 2015 16:30:17 -0500 "VanguardLH" wrote in
article .... Are you logged in using an admin-level Windows account when trying to start/stop services? Yes Google found some suggestions, including one that would appear to solve the problem by divorcing the time service from the "other services". I don't know what your term "divorcing" means. It means to separate the time service from others that might share an svchost. When I look at the Log On tab, the Windows Time service starts under the Local Service account. You can run "control.exe userpasswords2", Advanced tab, and click on Advanced User Management (not available in Home editions). See: http://windowsitpro.com/systems-mana...rvice-accounts Thanks for the pointer. I am running Win 7 Pro. I looked at user management and don't see anything suspicious. |
#4
|
|||
|
|||
Windows Time Service will not start
On Mon, 28 Sep 2015 21:42:06 +0000 "Stormin' Norman"
wrote in article Have you tried the following: net stop w32time w32tm /unregister w32tm /register sc config w32time type= own net start w32time It worked. That's mystifying, because I had done those steps before (or so I thought) to no effect. hmmm. |
#5
|
|||
|
|||
Windows Time Service will not start
Stormin' Norman wrote:
On Mon, 28 Sep 2015 17:07:12 -0400, Jason wrote: When I try starting it I see this error: 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. Google found some suggestions, including one that would appear to solve the problem by divorcing the time service from the "other services". I ran the sc command to change this (type= own) and it succeeded but the problem persists. Have you checked your event log for any other errors? Is this a stand alone machine or is it a member of a domain? Have you tried the following: net stop w32time w32tm /unregister w32tm /register sc config w32time type= own net start w32time What's weird about that problem, is after you try some tricks to work around it, there seem to be side effects. https://social.technet.microsoft.com...m=winservergen One person fixed it via sfc /scannow and that implies some file property is important. This may seem an odd question, but do you use pool.ntp.org as the time source ? Have you considered switching back to time.windows.com ? The ntp.org consists of hundreds of machines, and the economics of volunteering machines for this purpose means that "scumbags" will be attracted. People who want your IP address. Or perhaps people who have found an exploit they can carry out via w32time.dll. I've stopped using ntp.org here, as it just doesn't seem a good idea. Paul |
#6
|
|||
|
|||
Windows Time Service will not start
I looked at the Windows Time registry entry at:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\servic es\W32Time It has a ServiceSidType data entry. Mine is set to 1. When I looked at the service definition (services.msc, Log On tab in properties), it said it logged in under the Local Service account. So I'm guessing 1 in the registry means under which account the service runs. https://msdn.microsoft.com/en-us/lib...ql.120%29.aspx That was worthless for telling me what that data entry does. https://msdn.microsoft.com/en-us/lib...=vs.85%29.aspx That gave some more info, specially what the constant vars meant for their actual numerical value. 1 means Service_SID_Type_Unrestricted (which the article delineates what attributes are associated to that value -- but you'll have to delve into more programming to figure out what those mean). In the service properties under the Log On tab, I changed the account from Local Service to Local System (the SYSTEM account) and clicked Apply. There was no change in the ServiceSidType value (still 1). I did notice the ObjectName data entry changed to LocalSystem. To change back to the Local Service account under which the service runs, I was asked for a password. I didn't know it had a password plus I wouldn't know what it was. Eventually I blanked out the password and verify fields and it accepted that, so I'm back to running the Windows Time service under the Local Service account. You could try changing the Log On property for the Windows Time service to see if it loads okay under the more privileged SYSTEM account. The Local Service account was created to permit a limited set of privileges compared to Local System (SYSTEM) which has all privileges. The new Local Service account (I think it was introduced back in Windows XP to eliminate some escalation of privilege vulnerability) is used to limit privileges for services since they usually do not need full SYSTEM privileges. Not all services need SYSTEM-level privileges. If you look at the services listed in services.msc, you'll see some that run under Local Service and others that run under Local System. "sc sidtype" can change the service SID type. When I run "sc qsidtype w32time", it says "SERVICE_SID_TYPE: UNRESTRICTED". I don't know that changing the SIDtype will help since the problem for you appears Windows is somehow mixing restricted and unrestricted services into the same svchost.exe instance and maybe that's a bad thing. SID type is for service isolation but I don't that means not mixing different SID types together under the same svchost.exe instance. Some info about service isolation found at: http://windowsitpro.com/security/q-h...i-set-service- I'd first try changing the service to run under the SYSTEM account before monkeying around with service SID types. Note that the W32Time service does not run constantly. It is set for Manual startup mode which means a caller (process) must request use of the service. That's why when I used SysInternals' Process Explorer that I could not find the service rolled into an instance of svchost.exe: the service wasn't running at the time I checked. I can start the service but it would be a waste of resources to do so. Leaving it running all the time is a waste. It only needs to run when something calls it. It is defined as a service but it is a utility called by something else to do the NTP (network time protocol) process to update the OS clock. |
#7
|
|||
|
|||
Windows Time Service will not start
En el artículo ,
Jason escribió: When I try starting it I see this error: System error 1290 has occurred. Does "net time \\%computername%" from the command prompt work? If yes, the time service is running ok. -- (\_/) (='.'=) Bunny says: Windows 10? Nein danke! (")_(") |
#8
|
|||
|
|||
Windows Time Service will not start
|
#9
|
|||
|
|||
Windows Time Service will not start
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|