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

"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}"

I am curious..... While working in DCOM, your step #16 states, "Add SYSTEM then apply"..

Q: Was (or is) the word 'SYSTEM' *the name of the User or Group* stated in the Event Log for your *specific 0016 error event???

I'll put it as clear as I can, although I'm sure people will still insist they know better:

* These errors are safe to ignore.

* If you don't know what you're doing then do nothing. The "fixes" suggested here will remove callback permissions and break things most probably. Try and fix your specific problem, like BasilReznor did.

* If you do know what you're doing, then check a few pages back. I have provided the proper way to grant the required permissions.

They do affect some people. For me there is always a lag of several seconds during start up, and a corresponding error event in the application log within a second afterwards. Always. Conversely, when it doesn't happen, the precedent issues don't either. I suppose that's "safe to ignore" as well?

At the very least Windows' measurement is aggregating these into the of general system in Control Panel\System and Security\Security and Maintenance\Reliability Monitor resulting in "an unintended and negative result". A bug or "known issue" back when I was working in PSS. The Safe Mode copy/paste nonsense does jack squat in this situation, because even if COM services ran Safe Mode (hint: they don't) it doesn't help troubleshoot what might involve the network and require Safe Mode w/Networking.