Event ID 10016 - The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

Anonymous
2012-11-20T22:14:35+00:00

Lately I get this system error a lot now that I have upgraded to Windows 8 Pro is a DistributedCom Event ID 10016. Below is the error text:

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\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.

Anybody have any idea why I'm getting this error?

Walt

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2013-12-22T16:53:28+00:00

Same thing here. Greyed out. Windows 8.1 seems to fill the Event viewer with far more errors than previous versions.

edit: OK, found out why it was greyed out. There are 2 reg keys you have to set permissions to before you go to the DCOM Configuration in Component services. The CLSID key and the APPID key.

From another forum, although it applies to a different app, same principle:

*1. Open Regedit.2. Go to HKEY_Classes_Root\CLSID\*CLSID*.Note: *CLSID* stand for the ID that appears in your event viewer error. In your case, it's {C2F03A33-21F5-47FA-B4BB-156362A2F239}.3. Right click on it then select permission.4. Click Advance and change the owner to administrators. Also click the box that will appear below the owner line.5. Apply full control.6. Close the tab then go to HKEY_LocalMachine\Software\Classes\AppID\*APPID*.Note: *AppID* is the ID that appears in your event viewer. In your case it's {316CDED5-E4AE-4B15-9113-7055D84DCC97}.7. Right click on it then select permission.8. Click Advance and change the owner to administrators.9. Click the box that will appear below the owner line.10. Click Apply and grant full control to Administrators.11. Close all tabs and go to Administrative tool.12. Open component services.13. Click Computer, click my computer, then click DCOM.14. Look for the corresponding service that appears on the error viewer.15. Right click on it then click properties.16. Click security tab then click Add User. Add SYSTEM then apply.17. Tick the Activate local box.So use the relevant keys here and the DCOM Config should give you access to the greyed out areas:*CLSID:

{D63B10C5-BB46-4990-A94F-E40B9D520160}

and APPID

{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}

Was this answer helpful?

500+ people found this answer helpful.
0 comments

214 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-04-07T19:04:53+00:00

    Thank You DelZoppo,

    Now it came up again with other Event id, it is really annoying, I have original Win10, and only legal softwares...  Why is it happening ... isnt there a better fix?

    The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID

    {7022A3B3-D004-4F52-AF11-E9E987FEE25F}

     and APPID

    {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}

     to the user DESKTOP-VDBLGSE\gergo SID (S-1-5-21-777097218-497088624-898119774-1002) 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.

    :(:(

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-04-06T10:24:07+00:00

    In DCOM conf. you will find : Shell Service Host

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-04-02T21:00:30+00:00

    Hi all, I have this issue for long time, and I made a clean install, and still had it, then i made a research, did the changes written above, but after a week or so, it came out again, only for an other App ID:

    Now it is:

    {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}

     and APPID

    {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}

    I did grant access for admin in registry, but  I can not find these two in the Component Services -> Computers -> My Computer  -> DCOM Config.

    I searched trough line by line several times, but I can't find it.

    If someone could help me, I would be very happy

    EDIT: I have found this, {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}, but still can not find the 6b3

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-03-24T19:47:33+00:00

    I think that part of the problem is that for every network connection a  DCOM Message will take a different amount of time to get a response, and for a variety of reasons. Whoever wrote the original code for the messages did NOT take into account that networks run at different speeds and that different functions will take different time periods to respond positively/negatively or with a shrug of the shoulders.  I have seen a number of cases where the DCOM response has taken just a second or less longer to respond than the timeout. I have also seen where the response was being processed and sitting on a queue in the storage of the requestor while it was giving the error.

    Was this answer helpful?

    0 comments