martes, 19 de octubre de 2010 7:53
I'm getting a system error 1290, when i try to use the command "net start w32time".
The output from cmd looks like this:
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.
How do i recover from this error?
Todas las respuestas
jueves, 21 de octubre de 2010 7:15Moderador
Hi cliff.ha, I suggest you first try the following steps and see the result:
1.Click Start , type regedit in the Start Search box, and then click regedit.exe in the Programs list.
If you are prompted for an administrator password or for a confirmation, type your password, or click Continue .
2.Locate the following registry subkey, and then click it:
3.In the details pane, right-click ImagePath , and then click Modify .
4.In the Value data box, type the following registry value, and then click OK :
%SystemRoot%\System32\svchost.exe -k NetworkService
Note: If NetworkService does not appear in the %SystemRoot%\System32\svchost.exe -k NetworkService registry value, the problem that is described in the "Symptoms" section may occur.
5.Exit Registry Editor, and then restart the computer.
Note If you try to start the Telephony service before you restart the computer, you may receive the following error message:
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.
Hope this helps!
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
- Marcado como respuesta Sean Zhu -Moderator viernes, 29 de octubre de 2010 6:30
martes, 28 de diciembre de 2010 6:13
We are getting the following error message at our end while trying to start the Routing and Remote Access Service.
Could not start the Routing and Remote Access service on Local Computer. Error 1290: 0x50a
We are also getting a system event 7000 in the event viewer
I wanted to know if the above mentioned issue was resolved by any chance??
jueves, 10 de marzo de 2011 8:57I am confused why modifying the TAPI server would affect the Time Server.
martes, 10 de abril de 2012 14:48
I have the same problem on a Win2008 R2 server on Amazon EC2. I keep on seeing this solution wherever I look, but..
- What has the this RAS service got to do with the time server?
- I do not have this registry key. It is Server Core, so does not have this role.
- It is connected to my LAN using OpenVPN, if that makes a difference.
- The Amazon Ec2Config service cannot start either, as it depends on the w32time service for some reason.
What do I do to fix this problem with the time service, as I do nto have this seemingly irrelevant key in the registry.
This server is a domain controller, and there are only two in total, so it needs to be fixed as soon as possible.
- Editado jason404 martes, 10 de abril de 2012 14:49
miércoles, 02 de mayo de 2012 19:02It is really unfortunate that people are allowed to mark their own posts as answers, as this is a completely bogus answer, the TapiSrv has nothing to do with the time service. The only reason it might fix the problem is the reboot at the end.
- Editado stangm miércoles, 02 de mayo de 2012 19:02
domingo, 30 de septiembre de 2012 5:19
The problem was solved just restarting the server.
jueves, 01 de noviembre de 2012 13:46
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.
.\net stop w32time
.\sc config w32time type= own
.\net start w32time
.\w32tm /config /update /manualpeerlist:"0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org,3.pool.ntp.org",0x8 /syncfromflags:MANUAL /reliable:yes
- Propuesto como respuesta VBdP jueves, 01 de noviembre de 2012 13:46
miércoles, 28 de noviembre de 2012 22:43Thanks VBdP the sc config command worked Cheers.
viernes, 21 de diciembre de 2012 16:07Worked like a charm, thanks for your brain time VBdP.
- Propuesto como respuesta MCPVCP.M-O-U-S-E viernes, 21 de diciembre de 2012 16:07
jueves, 10 de enero de 2013 1:24
I did all the first 7 passages (with another NTP sorce) succesfully, but when I put
It results "Access is denied (0x80070005)
I tried to change MANUAL with DOMHIER, because I've only a DC (windows 2008) but I obtain the same result.
The clock retards 5 minutes. What can I do?
- Editado Lgalver jueves, 10 de enero de 2013 10:06