[Resolved] DCOM issues, ID 10016 [Resolved]

Muttley Mutterson

Reputable
May 30, 2014
6
0
4,510
Having issues with DCOM crashing computer, followed advice on windows site but it ends up with, "check permissions are set correctly" and well, I don't know diddly.

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
and APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
to the user (xyz) SID (S-1-5-21-2213316653-2133240355-1257971409-1002) from address LocalHost (Using LRPC) running in the application container Microsoft.SkypeApp_12.7.597.0_x64__kzf8qxf38zg5c SID (S-1-15-2-2246530975-808720366-1776470054-230329187-4153223113-3550430174-4193313734). This security permission can be modified using the Component Services administrative tool.

 
More of the same

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.

I've been following a bunch of advice found from the web but end up with issues with dcom components being greyed out, then when trying to change key to allow administrator with full access, then back to trusted installer, it gives me an error message not allowing it.


 
I've followed the guides on MS and toms hardware elsewhere but keep running into problems not being able to change permissions on CLSID, let alone the greyed out options on APPID.

However, I found another guide that uses elevated command prompt to change permissions which allowed me to resolve the issue:

I've followed the guides on MS and toms hardware elsewhere