none
system error 1290 after register w32time service

    Domanda

  • Hello all

    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?

     

    martedì 19 ottobre 2010 07:53

Risposte

  • 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 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
    .\w32tm /resync
    popd
    • Proposto come risposta VBdP giovedì 1 novembre 2012 13:46
    • Contrassegnato come risposta Yagmoth555MVP, Moderator martedì 25 febbraio 2014 19:58
    giovedì 1 novembre 2012 13:46
  • 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:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TapiSrv

    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.
    giovedì 21 ottobre 2010 07:15
    Moderatore

Tutte le risposte

  • 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:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TapiSrv

    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.
    giovedì 21 ottobre 2010 07:15
    Moderatore
  • We are getting the following error message at our end while trying to start the Routing and Remote Access Service.

    ---------------------------
    Services
    ---------------------------
    Could not start the Routing and Remote Access service on Local Computer.  Error 1290: 0x50a
    ---------------------------
    OK  
    ---------------------------

    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??

    Thanks,

    Prashant

    martedì 28 dicembre 2010 06:13
  • I am confused why modifying the TAPI server would affect the Time Server.
    Harold Naparst
    giovedì 10 marzo 2011 08:57
  • 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. 

    Thanks.


    • Modificato jason404 martedì 10 aprile 2012 14:49
    martedì 10 aprile 2012 14:48
  • It 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.
    • Modificato stangm mercoledì 2 maggio 2012 19:02
    mercoledì 2 maggio 2012 19:02
  • That's true.

    The problem was solved just restarting the server.

    domenica 30 settembre 2012 05:19
  • 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 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
    .\w32tm /resync
    popd
    • Proposto come risposta VBdP giovedì 1 novembre 2012 13:46
    • Contrassegnato come risposta Yagmoth555MVP, Moderator martedì 25 febbraio 2014 19:58
    giovedì 1 novembre 2012 13:46
  • Thanks VBdP the sc config command worked Cheers.
    mercoledì 28 novembre 2012 22:43
  • Worked like a charm, thanks for your brain time VBdP.
    venerdì 21 dicembre 2012 16:07
  • Hello,

    I did all the first 7 passages (with another NTP sorce) succesfully, but when I put

    .\w32tm /resync

    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?

    Thank you


    • Modificato Lgalver giovedì 10 gennaio 2013 10:06
    giovedì 10 gennaio 2013 01:24
  • 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 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
    .\w32tm /resync
    popd

    The problem with your fix is when running a DCDiag it comes up with this..

    Starting test: Services
           Invalid service type: w32time on DCSERVER, current value WIN32_OWN_PROCESS, expected value
           WIN32_SHARE_PROCESS
        ......................... DCSERVER failed test Services


    Thanks, Charlie


    • Modificato CJlindell venerdì 31 maggio 2013 00:07
    venerdì 31 maggio 2013 00:06
  • Stop the elevated service and restart it normally again then.
    lunedì 3 giugno 2013 22:03
  • This isn't even in the same hemisphere as a correct answer.  In fact, this is "wronger" than two boys caught naked in the woods with the chaplain's assistant.
    lunedì 29 luglio 2013 16:03
  • Careful with that registry change, I just blew my TMG to space.
    martedì 25 febbraio 2014 10:54
  • Hi, I seen there is one abuse report in that thread, I Sean Zhu's answer talk about TAPI, but is it a error he wrote ?, no way to know. As .\sc control w32time type=own from VBdP's script do the same check, but of course flagged for the w32time. I will remove the abuse report and mark VBdP's answer.

    Just a small reference for the issue too; Getting Started with SVCHOST.EXE Troubleshooting


    Regards, Philippe

    martedì 25 febbraio 2014 19:58
    Moderatore
  • The:sc config w32time type= own

    trick fixed it for me.


    Chris

    • Proposto come risposta jtibbitts mercoledì 16 aprile 2014 10:42
    lunedì 17 marzo 2014 17:22
  • Fantastic! I have been stuck for days! Trying everything that I could find on the net! Including Microsoft! Brilliant
    martedì 8 luglio 2014 15:41
  • Yes, Sean, but it can be most clear:

    HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\TapiSrv\\ImagePath
    Value name: ImagePath
    Value Data:
    %SystemRoot%\System32\svchost.exe -k NetworkService

    A.B. IT PRO (aka Jane Doe)

    martedì 16 settembre 2014 21:46
  • Windows time service problematic key
    HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services

    \TapiSrv\\ImagePath
    Value name: ImagePath
    Value Data:
    %SystemRoot%\System32\svchost.exe -k NetworkService

    However, Rebooot is seems inevitably !

    martedì 16 settembre 2014 22:29
  • Thanks VBdP!
    lunedì 13 luglio 2015 20:38
  • Hi VBdP,

    I want the above fix to be applied in prod domain controller where I have the same time service issue. I was just testing it in test dc prior applying in production. I have received below message when I ran dcdiag.

     DCTest passed test RidManager
       Starting test: Services
             Invalid service type: w32time on DCTest, current value
             WIN32_OWN_PROCESS, expected value WIN32_SHARE_PROCESS
          ......................... DCTest failed test Services

    What I want to know here is , Is there any side effects of running the command .\sc config w32time type= own  production domain controller ?

    martedì 3 novembre 2015 09:24
  • You can set the service config to "own" so it uses its own svchost process and this "works", but after doing so typically you cannot use the w32tm /query commands, because you get Access Denied error messages. Not only that, but the dcdiag Domain Controller testing fails because the service is not using a type of "share".

    See https://social.technet.microsoft.com/Forums/windowsserver/en-US/9eeab977-6c94-43d1-8f2f-3cb1eb525744/w32tm-query-status-access-is-denied-0x80070005-from-elevated-prompt?forum=winserverDS for a better answer to this issue.

    The solution is not only perform w32tm /unregister & /register, but in between those commands, ALSO to execute a "regsvr32 /u w32time.dll" command. I'm guessing that the w32tm /unregister (at least in the broken state) does not unregister the DLL or fails trying.

    Do it in this order in an administratively elevated command prompt, reboot as specified - twice! (Copied from other thread above, thanks to the writer!)

    1. net stop w32time
    2. w32tm /unregister
    3. --- REBOOT ---
    4. regsvr32 /u w32time.dll
    5. w32tm /register (this will re-register the DLL, no need to do it separately)
    6. sc query w32time -- you should see that the service is set to shared mode -- if you try to start right now, you'll get the expected 1290 SID-related error
    7. --- REBOOT ---

    Follow the above instructions, and you do not need to do anything with the TapiSrv registry key or service configuration.

    sabato 12 dicembre 2015 06:04
  • Thank you so much!

    Using the SC Config command proposed in the marked answer would cause w32tm to start the service but with Access denied errors whenever I tried to do anything with it.

    Following your steps EXACTLY as you proposed fixed my issue 100%.

    I've proposed it as the answer as it 100% works with no side effects.

    Martin

    giovedì 7 gennaio 2016 01:35
  • Hi all,

    same problem .. I solved this without the reboot, on 2012 r2: 

    sc config w32time type=own and on Log On tab I selected "Local System Account".

    Now the service is working fine.

    Alex

    lunedì 18 gennaio 2016 14:34
  • Hi all,

    same problem .. I solved this without the reboot, on 2012 r2: 

    sc config w32time type=own and on Log On tab I selected "Local System Account".

    Now the service is working fine.

    Alex

    Careful with this method, as initially this also "worked" for me, but I was then unable to run any w32tm commands and kept getting "Access Denied" errors.  Only by following the steps exactly as described did the whole thing get back to a full, proper, working state.
    mercoledì 20 gennaio 2016 21:54
  • Nice solution as my time was continually changing to 6 hours ahead. After your suggestions I can now start service but when trying to resync it fails for following:

    Sending resync command to local computer
    The following error occurred: Access is denied. (0x80070005)

    lunedì 20 febbraio 2017 03:31
  • When you in-register and re-register the W32Time service, the service is set as a shared service (WIN32_SHARE_PROCESS) - As shared services have a hard time registering themselves outside of the boot process, this shows a lot of the issues that have been pointed out on the thread.  Setting the service to Own (WIN32_OWN_PROCESS) will make it look like the issue has been fixed, but causes the Access is denied issues.  The correct fix it to unregister the service, and the re-register the service and reboot.  If you have set the server to WIN32_OWN_PROCESS, then setting it back to WIN32_SHARE_PROCESS [sc config w32time type= share] and rebooting will resolve the issue.
    mercoledì 5 aprile 2017 17:20
  • thank you!!!

    saludos

    mercoledì 18 aprile 2018 12:44
  • +1 million to net-bytes, all the other fixes were not helping, your addition of unregistering the DLL is the fix for my problem
    mercoledì 16 maggio 2018 17:13