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

Anonymous

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

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

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}

0 comments

214 additional answers

Anonymous

2016-01-29T06:42:07+00:00

That would be my interest too, but sometimes you have to cut your losses. I never did figure out how to get the infuriating temp profile problem to stop happening in older versions of Windows (fortunately, I've never seen it in Win8/Win10), just how to undo it. Fortunately, it only happened a few times a year.

On retrospect, it's kind of funny that you bring it up in the context of this DCOM issue, which is another intractable one where I learned to stop worrying and love the bomb. I really do hope MS fixes it though, since I sigh every time I open up Event Viewer.
Was this answer helpful?

0 comments No comments
Anonymous

2016-01-29T09:19:44+00:00

I thought it worth mentioning for some with the "RuntimeBroker" problem to mention what worked for us. For myself I took ownership of the CLIDs and added my user name. I then restored ownership to the original owner. I had a few sporadic errors after that for a while and then they seemed to disappear. I wondered if Microsoft had finally fixed the original problem. Then I start to use Cortana and boy do the DCOM 10016 errors flow forth. I had problems in the original 10 upgrade because I had Media Center, and other errors seem to come from changing the computers name and other problems with homegroup.
Was this answer helpful?

0 comments No comments
Anonymous

2016-01-30T03:05:25+00:00

I don't think MS has fixed anything. I followed probably the same instructions you did with RuntimeBroker. Before I did this the errors were enormous, and after I did it the errors were gone.
Was this answer helpful?

0 comments No comments
Anonymous

2016-02-03T12:51:48+00:00

After this in Event viewer, my computer halt ant reboot :/

Latest Windows 10 x64

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.

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.

The operating system started at system time ‎2016‎-‎02‎-‎03T11:20:48.496694700Z.

...

The previous system shutdown at 12:18:54 PM on ‎2/‎3/‎2016 was unexpected.

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Was this answer helpful?

0 comments No comments