SharePoint

If you find a lot of DCOM errors with event ID 10016 in your application server role, this may be due to Windows Server 2008 R2. Here’s how to resolve these isuses

On the failing server open Server Manager, and under Roles select Application server. You will most probably find quite a lot of DCOM errors. Open one of those errors to see for which user and for which service the authentication is failing. In the open window copy the GUID of the failing service. It will help you identify the service.

Next open registry editor and select the root node. In Edit menu select Find, paste the GUID and click Find next.

You can find the service name in one of the registry’s values (as seen on the screenshot below, in my case it was IIS WAMREG).

Leave the registry editor open (you might still need it).

Next in Start menu under Administrative tools click Component Services. Expand the Computers node and My Computer. Select DCOM Confing. Now locate the service you identified in your registry, right click it and select Properties.

In the open dialog select Security tab and in the Launch and activation permissions group click the Edit button.

If you have this entire tab grayed out, you need to do the following (outlined in the gray, otherwise skip the gray part below):

In the permissions dialog for the service grant the failing user (or group the account is in) Local Launch and Local Activation permissions. And in case the event log says it is failing remote launch, grant the user remote launch and service also.

Confirm all the changes and close registry editor and Component services window.