Bienvenido! - Willkommen! - Welcome!

Bitácora Técnica de Tux&Cía., Santa Cruz de la Sierra, BO
Bitácora Central: Tux&Cía.
Bitácora de Información Avanzada: Tux&Cía.-Información
May the source be with you!

Thursday, February 21, 2013

Event ID 10016 -DCOM error

Event ID: 10016 error
answers.microsoft.com/en-us/windows/forum/windows_7-performance/error-event-log-10016/8f8416a9-2789-4365-a3f1-9e74c0da1393
follow these steps and check if the issue is fixed.
i. Click Start, type dcomcnfg in the Search bar, and hit enter.
ii. In Component Services, double-click Component Services, and then double-click Computers.
iii. Right-click My Computer, and then click Properties.
iv. Click the COM Security tab.
v. In the Launch and Activation Permissions area, click Edit Default.
vi. Click Add, type Network Service, and then click OK.
vii. While Network Service is selected, click to select the Allow check boxes for the following items:
viii. Local Launch
ix. Remote Launch
x. Local Activation
xi. Remote Activation
xii. Click OK two times.

In addition to this I would point users to setup DCOM Security just for particular app/services that error in Event ID 10016 specifies as ScottH_JAX did. Other wise we're givinng unnecesarry permission (including remote launch and access) to all of the apps/services on your machine. It's like an open door for hijackers to manipulate your pc, don't you think? So, simply saying people...read your event id 10016 to check for which user its reported and take down APPID. Go to Start-> Ctrl Panel-> Admin Tools ->Component Services. In the left pane: click Component Services->Computers->My Computer->DCOM Config. List of apps list show up. Right to the name of app you have Application ID=APPID. Match it to what you have found in your event 10016. Right click->Properties->Security tab->Launch & Activation Permissions->click Edit. Add user that has been mentioned in your event 10016 and give it appropriate permissions.
-----------------------
The above answer changes the default launch permissions, which didn't work for me, but drilling down into the IPBusEnum component (matching the appID 344ED43D-D086-4961-86A6-1106F4ACAD9B), I found the launch permissions were set to "custom", not "default".  I changed the custom launch permissions for the app to give SYSTEM local launch authority.
-----------------------
I followed the instructions. WHen I open the security tab all options are greyed out and I cannot change anything. I am logged in with admin and am on a standalone computer.
I tried running 
comexp.msc
as adminsitrator - same thing - I cannot change the settings for {D3DCB472-7261-43CE-924B-0704BD730D5F} -
I have the same problem with
{145B4335-FE2A-4927-A040-7C35AD3180EF}
They always occur in pairs
regedit identifies both of these as fdPHost.
===========
Here's the solution, that worked:
"I went into component services and tried to change security settings for IPBusEnum...but everything is grayed out."
Try the steps provided under Step 1 in the below article to put your computer in clean boot mode.
http://support.microsoft.com/kb/929135
---------------
For anyone that got Error 10016 follow this link to the Microsoft Article on how to fix this.
------------------
The following is what I had to do before I could grant permissions to the COM component:
1.    Make sure you’re logged on as an administrator.
2.    Click Start, type regedit in the Search bar, then click regedit.exe
3.    In the Registry Editor, press CTRL-F, type {344ED43D-D086-4961-86A6-1106F4ACAD9B} and click “Find Next”.
4.    The first result is located in HKEY_CLASSES_ROOT\AppID\. This is the key we need.
5.    Right-click the key {344ED43D-D086-4961-86A6-1106F4ACAD9B} in the left sidebar, and then press “Permissions…”
6.    We first have to change the ownership of the key. The current owner is TrustedInstaller. We have to change the owner to Administrators. Therefor, click Advanced. Then go to the tab Owner, select Administrators, check the box “Replace owner on subcontainers and objects”  and press OK.
7.    Now that we have changed the ownership to ourself (member of the Administrators group), we can change the permissions on the registry key. In the Permissions window, grant Administrators AND SYSTEM Full Control permissions. Then click OK to confirm the changes. In these 8 steps, we have granted the Administrators and SYSTEM account full permissions to the key HKEY_CLASSES_ROOT\AppID\{344ED43D-D086-4961-86A6-1106F4ACAD9B}.
8.    Verify that in this key, the value of LocalService is IPBusEnum
9.    Click Start, type Component in the Search box, and then click Component Services
10.    In the Component Services window, go to Computers – My Computer – DCOM Config.
 Right-click IPBusEnum and click Properties.
11.    Go to the tab Security. In the Launch and Activate permissions section, select Customize and click Edit.
12.    Select SYSTEM, select the permissions checkbox “Local Launch”. Then click OK to apply the change.
13.    Done!
Credit for this solution goes to
http://www.itexperience.net/event-10016-the-application-specific-permission-settings-do-not-grant-local-launch-permission-for-the-com-server-application-with-clsid-c97fcc79-e628-407d-ae68-a06ad6d8b4d1/

No comments: