If we look at Windows Server and Windows Client OS Event Log, we can see Events 10016:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID … and APPID …
This means that specific user does not have local launch and local activation permission to run specific DCOM object.

 

For instance we can look at fresh installed Windows 10 (version 1607 – Anniversary Update).

If we look at System Windows Log in Event Viewer, we can find this type of Error:

 

DCOM 10016

 

In this example user System does not have permission to Local Launch (Local Activation) DCOM Application with ID: {F72671A9-012C-4725-9D2F-2A4D32D65169}.

 

Solution:

 

We have to set DCOM Application permissions for specific user in Component Services (we have to launch app as Administrator).
Then we have open Component Services, Computers, My Computer, DCOM Config and select Detail View from View Menu.

From the list we have to find DCOM Application ID with problematic permissions.

 

Component Services

 

If we right click on selected Application ID and select Security Tab, everything is gray, because as administrator we don’t have permission to change DCOM Application permissions.

 

DCOM Permissions

 

It is easy to change permissions for selected Application with Registry Editor (regedit.exe).

With Edit/Find command, we can find problematic Application ID in Registry.

It is located in HKEY_CLASSES_ROOT\AppId\{F72671A9-012C-4725-9D2F-2A4D32D65169}.

 

DCOM App Registry

 

With right click and selected Permissions.., we can change permissions for specific AppId. First we need to change owner of registry Key.

Go to Advanced, Change Owner to Administrators group (local Administrators group, if computer is member of domain), select OK twice. Then open Permissions window once again and change permissions of Administrators group to Full Control.

 

AppId Permissions

 

Now we can return to Component Services Application (restart application after changing registry permissions or simply Refresh application list), find our Application ID, as it is written above.
If we right click on selected Application ID, we can now change Launch and Activation Permissions of Application.

We have to Add user that doesn’t have Local Activation Permission from Error Event. In our case we have to set Local Launch and Local Activation Permissions for user System.

 

Launch Permissions

 

That’s it. We will not see Event 10016 for selected application ID and specific user any more in our OS.

 

Enjoy!!!

mm
Written by Simon Abolnar
I am a lecturer of Informatics subjects at Higher Vocational College at the School Center Nova Gorica, located in Slovenia-EU. I have been a System Administrator of Microsoft Servers at SCNG for over 20 years.