Windows 10: EventID 10016 - NT AUTHORITY\SYSTEM - name not found

eventid 10010
Code: The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout.[/quote] Eventid 10010
Code: The server microsoft.windowslive.calendar.AppXwkn9j84yh1kvnt49k5r8h6y1ecsv09hs.mca did not register with DCOM within the required timeout.[/quote] Best,
Gelo.[/quote]
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..... *Sad

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

 

eventid 10010
Code: The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout.[/quote] Eventid 10010
Code: The server microsoft.windowslive.calendar.AppXwkn9j84yh1kvnt49k5r8h6y1ecsv09hs.mca did not register with DCOM within the required timeout.[/quote] Best,
Gelo.[/quote] @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

 

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!

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

 

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

 

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

 

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!