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
    2016-10-17T02:23:16+00:00

    I found the items referenced in this help file, but system would not allow me to change the items. Correction changed them but could not save changes.

    Suggestions?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-08-31T14:25:12+00:00

    Yes, that's a very good point. The instructions are very clear that you should click "cancel" at this point but they then seem to imply that you can edit the permissions by adding accounts - but that's certainly not the case for me and as you point out the pop-up does say it will be "read-only". It does seem to leave no way forward.

    For the record, I'm getting the 10016 code in my event log when trying to use the Firebird ODBC driver. My application shows "Provider error 8000ffff catastrophic failure". Clicking "Test" in the ODBC Data Sources desktop app causes the app to fall over immediately. In both cases the event log shows the 10016 code. I've had to find a workaround on another computer to get the job done. I would love to get to the bottom of this though, as I have encountered the error code at other times.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-08-17T17:36:00+00:00

    This is exactly the point I reached this morning. I have made all the suggested registry edits and taken ownership. The Custom edit buttons that were greyed out before on the Security tab in Component Services are now available. But I get the popup about removing settings and when I click cancel, I can't add other groups or users because the Add and Remove buttons are greyed out.

    I've been googling all day and have concluded that there is a Group Policy in place which is preventing me adding users here. The advice is to alter this using gpedit.

    However, I am on Windows 10 Home Edition and gpedit is not included.

    I have investigated downloading it from here:

    http://drudger.deviantart.com/art/Add-GPEDIT-msc-215792914

    This seems risky. Having edited the registry several times today already, I would be more open to making the necessary changes directly with regedit, than downloading something unapproved, provided I can get good clear instructions. But I don't know how to find out the changes to make.

    This page:

    https://www.wavesys.com/support/edit-limits-button-grayed-out-dcom-launch-and-activation-permissions

    seems to suggest the following is the policy to edit:

    DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) syntax

    Can anyone advise?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-08-08T21:23:17+00:00

    Take a look at this one

    https://support.microsoft.com/en-us/kb/2798317

    It's for Windows 8 which is much more like Windows 10 than the older KBs.

    Admittedly it doesn't refer to Event 10016 directly, but it addresses related components of the error message. I found that implementing the Resolutions in it seem to have resolved all my 10016 issues without having to mess with Ownership or DCOM activation settings.  (I didn't have the actual 5961 event message the article refers to so I can't speak to whether it addresses other issues, just the 10016 events for me.)

    As always, if you do apply the resolution be sure to keep track of what you changed so you can roll back if needed.

    Was this answer helpful?

    0 comments