Wednesday, September 24, 2008

Event 10016, Microsoft-Windows-DistributedCOM, The application-specific permission settings do not grant Local Activation permission for the COM Serve

First I found the following DCOM error in the Server Manager -> Application Server -> Summary
Source: Microsoft-Windows-DistributedCOM
Event ID: 10016
Keywords: Classic
User: NETWORK SERVICE
Description: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{629DA12E-9AD5-4FEC-B886-42C5982C5109} to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

After searching various blogs, got a simple procedure to correct this error

Step 1 (Identify Application causing the error):
Run “regedit” from the start menu. Find (Edit -> Find) the CLSID mentioned in the error message. “In my case {629DA12E-9AD5-4FEC-B886-42C5982C5109}” This Key should be in HKEY_CLASSES_ROOT -> CLSID. Against this, there would be a AppID (Key Value). Note down this value, which is the Application which has caused the error. “In my case {6002D29F-1366-4523-88C1-56D59BFEF8CB}”

Step 2 (Locate the Application causing the error):
Run “dcomconfig” from the start menu. Go to Component Services -> Computers -> My Computer -> DCOM Config. Search for the Application with “Application ID” matching the earlier noted AppID

Step 3 (Correct the error):
Go to the security configuration of the Application “Right click -> Properties -> Security Tab -> Launch and Activation Permissions -> Edit”. Add the user name mentioned in the Original error log (In my case NETWORK SERVICE), and select the options allow Local Launch and Local Activiation. Now the error is rectified, what is overall effect of this additional authorizations, or why this error has occurred, I have no clue, but the fact is Error in Server manager is resolved.

1 comment:

Neosol said...

Thank you for this post. I think it may have helped me with this issue. I did want to mention that on Exchange 2007 running under Windows Server 2008 x64, the command for DCOM is "dcomcnfg", and not "dcomconfig" as you have listed. Just a typo, but I thought you might want to correc that. Thanks, again.