Event 10016, DistributedCOM

I have NO idea where to put this, and I figure there have to be a ton of topics about it in these forums, but nothing gets found when I look for Event 10016, so...

I found a number of discussions elsewhere, and at LEAST a dozen different procedures that purport to fix the problem. I tried at least 4 or 5 and that all eventually get me to DCOM config where I can't find whatever it wants me to add LOCAL ACTIVATION to...

SO, can somebody point me to a procedure 'cause I'm not real trusting about procedures that come from strange, random places:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}

I found one procedure that said:
1. Type or paste ‘regedit’ into the Search Windows box.
2. Navigate to ‘HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole’.
3. Delete these four keys if they appear, DefaultAccessPermission, DefaultLaunchPermission, MachineAccessRestriction, MachineLaunchRestriction.
4. Reboot your computer.

That didn't appear to do anything.

Other searches point to links like this: https://support.microsoft.com/en-us/kb/899965
that aren't there any more.


I found another "fix" at Microsoft that had me go into regedit and give ownership of the CLSID to Administrators. And given them full control...

THEN it says:
6. In the similar way, take the ownership of following key and give full control on permissions to yourself and SYSTEM, for it:

HKEY_CLASSES_ROOT\CLSID\{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}Looked at that CLSID and both SYSTEM and Administrators HAVE Full control. I presume it DOESN'T have MY USER account "take the ownership of following key and give full control on permissions to yourself and SYSTEM" , right?

Then it wants me to find the original "application id" in DCOM config (6B3B8D23-FA8D-40B9-8DBD-B950333E2C52), but there's a list of HUNDREDS of application IDs, and as near as I can tell NONE OF THEM are this one... SO, I went to "ShellServiceHost" and there's a COMPLETELY DIFFERENT application ID there.

I can go into properties, Security, and "launch and activation permissions", but at this point I'm dead 'cause I CAN'T hit "Add"........

SO, can someone point me to a procedure that ACTUALLY WORKS, and is as idiot-proof as possible?

https://support.microsoft.com/en-us/...ws-server-2016

Cause

---

These 10016 events are recorded when Microsoft components tries to access DCOM components without the required permissions. In this case, this is expected and by design.A coding pattern has been implemented where the code first tries to access the DCOM components with one set of parameters. If the first attempt is unsuccessful, it tries again with another set of parameters. The reason why it does not skip the first attempt is because there are scenarios where it can succeed. In those scenarios, that is preferable.

Workaround

---

These events can be safely ignored because they do not adversely affect functionality and are by design. This is the recommend action for these events.