EventID 10016 - NT AUTHORITY\SYSTEM - name not found

Page 2 of 2 FirstFirst 12

  1. Posts : 56,825
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #11

    Kbird said:
    I looked at my rewritten instructions in the other post and I now think part is wrong that I copy and pasted from Vaio7......

    Local Activation Permission - Page 3 - Windows 10 Forums


    can you confirm F14 and i will edit it.....

    ie Same for the HKEY>LocalMachine\Appid. ( as seen in event log)

    Error? perhaps should be HKey>ClassesRoot>APPID NOT HKEY_LOCAL_MACHINE >AppID ?

    or
    HKEY_LocalMachine\Software\Classes\AppID\*APPID*.



    KB

    Hi, @Kbird ... I was working on 8.1 Patch Tuesday stuff.

    To use one of Gelo31415's examples, it is:
    Computer\HKEY_CLASSES_ROOT\AppID\{9CA88EE3-ACB7-47c8-AFC4-AB702511C276}

    I've never had to change ownership on the Com Server CLSID, only the AppID. The Com Server has no permissions, per se, in DCOM Components, only the APPID. The Com Server application invokes (runs) the APPID and you need to have the proper permissions to locally activate that APPID or the Com Server App throws an error.

    Yes, it's confusing. MS does their best......

    Code:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
    {D63B10C5-BB46-4990-A94F-E40B9D520160}
     and APPID 
    {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
     to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
    TC
      My Computers


  2. Posts : 2,324
    Win10
       #12

    f14tomcat said:
    Hi, @Kbird ... I was working on 8.1 Patch Tuesday stuff.

    To use one of Gelo31415's examples, it is:
    Computer\HKEY_CLASSES_ROOT\AppID\{9CA88EE3-ACB7-47c8-AFC4-AB702511C276}

    I've never had to change ownership on the Com Server CLSID, only the AppID. The Com Server has no permissions, per se, in DCOM Components, only the APPID. The Com Server application invokes (runs) the APPID and you need to have the proper permissions to locally activate that APPID or the Com Server App throws an error.

    Yes, it's confusing. MS does their best......

    Code:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
    {D63B10C5-BB46-4990-A94F-E40B9D520160}
     and APPID{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
     to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
    TC

    THX TC I will edit my other posts , so no one get confused .......

    Thankfully no issues on PC1 after Patch tuesday here , the others (Older pcs) have not mentioned it yet....

    KB
      My Computers


  3. Posts : 15
    Win 10
    Thread Starter
       #13

    One gone, two new! :-P


    f14tomcat said:
    Let me know if this is clear enough and if it helps.
    TC
    Thanks for the effort! Now one of the errors is gone but i got two new ones. Here are the three:

    eventid 10016
    Code:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160}
     and APPID 
    {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
     to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
    eventid 10010
    Code:
    The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout.
    Eventid 10010
    Code:
    The server microsoft.windowslive.calendar.AppXwkn9j84yh1kvnt49k5r8h6y1ecsv09hs.mca did not register with DCOM within the required timeout.
    Best,
    Gelo.
      My Computer


  4. Posts : 2,324
    Win10
       #14

    Gelo31415 said:
    Thanks for the effort! Now one of the errors is gone but i got two new ones. Here are the three:

    eventid 10016
    Code:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160}
     and APPID 
    {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
     to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
    eventid 10010
    Code:
    The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout.
    Eventid 10010
    Code:
    The server microsoft.windowslive.calendar.AppXwkn9j84yh1kvnt49k5r8h6y1ecsv09hs.mca did not register with DCOM within the required timeout.
    Best,
    Gelo.

    I read in other thread to fix all 10016 Errors the same way but I have not had a different one to try it myself .....

    My other computer is now throwing the same F72671A9xxxxxx error too.....

    Description:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
    {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
    and APPID
    {F72671A9-012C-4725-9D2F-2A4D32D65169}
    to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.


    KB
      My Computers


  5. Posts : 56,825
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #15

    Gelo31415 said:
    Thanks for the effort! Now one of the errors is gone but i got two new ones. Here are the three:

    eventid 10016
    Code:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160}
     and APPID 
    {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
     to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
    eventid 10010
    Code:
    The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout.
    Eventid 10010
    Code:
    The server microsoft.windowslive.calendar.AppXwkn9j84yh1kvnt49k5r8h6y1ecsv09hs.mca did not register with DCOM within the required timeout.
    Best,
    Gelo.
    @Gelo31415

    This one is now gone? Good.
    {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}



    Not much you can do about the timeouts on the server connections. At least not thru any permissions in DCOM. They come and go. They automatically retry a few times, but will log the error the first time.

    MS loves to log errors, even when it turns right around and fixes itself. Don't fret these type of errors too much. Looking for a perfectly clean error free event log will drive you nutso! So many things happening at the same time, especially at boot/logon, timing issues will arise. That's why MS built in retries instead of just crashing on the first attempt.
      My Computers


  6. Posts : 2,324
    Win10
       #16

    f14tomcat said:
    @Gelo31415

    This one is now gone? Good.
    {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}



    Not much you can do about the timeouts on the server connections. At least not thru any permissions in DCOM. They come and go. They automatically retry a few times, but will log the error the first time.

    MS loves to log errors, even when it turns right around and fixes itself. Don't fret these type of errors too much. Looking for a perfectly clean error free event log will drive you nutso! So many things happening at the same time, especially at boot/logon, timing issues will arise. That's why MS built in retries instead of just crashing on the first attempt.

    I think Gelo meant the 2 10010 errors were new ones, but I think 9CA88EE3xxxxx might be the Error I saw once or twice after fixing F7267xxxxxx on my other computer , and as you say TC it disappeared the next day.

    KB
      My Computers


  7. Posts : 15
    Win 10
    Thread Starter
       #17

    f14tomcat said:
    @Gelo31415

    This one is now gone? Good.
    {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
    No, the other one is gone. Actually it took a second restart to make it not come back - i wonder why! Who knows, maybe i will get lucky and get rid of the last 10016 today when i come home from work! :-P

    Thanks a lot @f14tomcat! I'll reply later today in any case!
      My Computer


  8. Posts : 56,825
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #18

    Kbird said:
    I think Gelo meant the 2 10010 errors were new ones, but I think 9CA88EE3xxxxx might be the Error I saw once or twice after fixing F7267xxxxxx on my other computer , and as you say TC it disappeared the next day.

    KB
    Yes, those are the timeout errors. We mortals can do little about them.
      My Computers


  9. Posts : 2,324
    Win10
       #19

    On my 2nd computer I had to use the Delete Reg.Key method to fix it whereas on the other One I used the "Usual Method" to fix the {F72671A9-012C-4725-9D2F-2A4D32D65169} error.

    I Edited post #10 incase Others find it to reflect this but there is also an entry in

    HKEY_LocalMachine\Software\Classes\AppID\*APPID*.

    not just

    HKEY_Classes_Root\CLSID\*CLSID*
    and
    HKEY_Classes_Root\AppID\*APPID*

    once fixed both F7267xxx Reg.Entries Show
    CDP Remote Text Handler as the Default Value instead.

    and the 8D8Fxxxx entry will show CDP Activity Store with the AppID as F7267xxxx

    Post #10
    EventID 10016 - NT AUTHORITY\SYSTEM - name not found

    KB
      My Computers


  10. Posts : 15
    Win 10
    Thread Starter
       #20

    Its working! *yey*


    f14tomcat said:
    Yes, those are the timeout errors. We mortals can do little about them.
    Hehe, but awesome mortals, if I may point this out.

    Actually all the errors are gone now! Esp. the info that {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} = Runtime Broker and needs NETWORK SERVICE activation did the trick! I was trying to get NT AUTHORITY/SYSTEM to work, but it would not let me (name not found)...

    Thanks bunches to you people, esp. Tomcat!

    Greetings,
    Gelo!
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 14:45.
Find Us




Windows 10 Forums