In this publish I’ll present you methods to repair the error with the EventID 10016 from the DistributedCOM supply on a pc working Windows 10 or Windows Server 2012 R2. The DCOM 10016 occasion is kind of widespread in each shopper and server Windows variations, ranging from Windows XP and you may repair this error the identical approach whatever the Windows model.
The drawback manifests itself as follows: the next error seems in the Windows Event Viewer in the System part when the pc boots or makes an attempt to begin or set up some utility:
Event ID: 10016
Description: The machine-default permission settings don’t grant Local Activation permission for the COM Server utility with CLSID and APPID Unavailable to the consumer IIS APPPOOLappIISPool SID (S-1-5-82-3351576649-1006875745-771203599-42452693-1279824824) from deal with LocalHost (Using LRPC) working in the applying container Unavailable SID (Unavailable). This safety permission may be modified utilizing the Component Services administrative software.
According to the error description: some consumer (for instance, IIS Apppool) or a system (NT AUTHORITYSYSTEM) tries to begin some COM part utilizing DCOM infrastructure and can’t do that because of the lacking of the “Local Launch” or “Local Activation” permission. The error code comprises solely the codes of the lessons for the COM part and the applying. Let’s attempt to decide which specific utility the identifier belongs to and grant the permissions essential to profitable launch and activate it.
Copy the CLSID and APPID from the occasion description. In my case it’s:
(in some instances, the applying identifier might not be specified – APPID Unavailable).
Also notice what permissions are lacking (Local Activation permission) and for which account (NT AUTHORITYSYSTEM or IIS APPPOOLappIISPool SID — S-1-5-82-3351576649-1006875745-771203599-42452693-1279824824).
In every case the category, utility, account identifiers, and entry sort might differ.
- Run the Registry Editor (regedit.exe);
- Go to the registry key equivalent to your CLSID. In my case it’s HKEY_CLASSES_ROOTCLSID;
In some instances, you have to examine additionally the registry key HKEY_CLASSES_ROOTWow6432NodeCLSID. When you remotely related to the registry, will probably be positioned in the registry part HKEY_LOCAL_MACHINESOFTWAREClassesAppID.
- In the category parameter the app title have to be specified (in my case it’s Microsoft Word Application);
Most typically the DCOM error 10016 happens with the next parts: Immersive Shell
- Right-click on the registry key and choose Permissions;
- Click on the Advanced button;
- NT ServiceTrustedInstaller or SYSTEM might be specified in the Owner part;
- Click the Change button and specify the title of your administrator account. Save the adjustments;
- Please notice that the title of the present registry key proprietor has modified to your account. Check the field Replace proprietor on subcontainers and objects and click on “OK”;
- Add your administrator account to the permissions record and grant Full Control permissions to it;
- You have granted the permissions to the registry key with CLSID. Now you have to repeat the earlier steps and alter possession and permissions for administrator account on the registry key of your APPID from the error description (for instance, HKEY_CLASSES_ROOTAppID;
- Now run the part administration console (dcomcnfg) as administrator (Control Panel -> All Control Panel Items -> Administrative Tools -> Component Services);
- In the part console go to the part Component Services -> Computers -> My pc -> DCOM Config. In the COM part record discover the title of the part that you simply outlined in the second step (the worth in the Application ID column should match your CLSID from the DCOM 10016 error description);
If you can’t discover your part in the record, you most likely use a 64-bit model of Windows, and the part you need to run is 32-bit one. In this case, you have to begin the DCOM console utilizing the command:
mmc comexp.msc /32.
- Click the Security tab. All of the shape controls to be accessible to vary;
If you open the dcomcnfg console earlier than altering permissions on the part registry key, all of the settings on the Security tab might be locked (can’t be modified), even supposing you began the console as an administrator.
- In my case, the applying didn’t have the permission for Local Activation. In the Launch and Activation Permissions part, choose Customize and click on the Edit button;
- You want so as to add to the ACL an account that was specified in the error desctiption. Depending on the textual content in the DCOM 10016 error, this could possibly be SYSTEM, a particular consumer, or the account below which the IIS pool runs (in this case, you have to add entry for the native IIS_IUSR group);
If NT AUTHORITYNETWORK SERVICE was specified in the preliminary error as an alternative of NT AUTHORITYSYSTEM, you should assign the native launch and activation permissions for the NetworkService account.
- Grant the mandatory permissions for the account. For instance, Local Launch = Allow and Local Activation = Allow.
- Restart the pc and examine the occasion logs. The error DCOM 10016 ought to disappear.