Event 10016: The application-specific permission settings do not grant Local Launch permission for the COM Server application

On our Sharepoint server, the following DCOM error message kept returning in the event log (bold text is Event ID-specific information):

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date: Date
Time: Time
(there may be situations in which the user is NT AUTHORITY\LOCAL SERVICE)

Description: The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {AppGUID} to the user User_Name SID User_SID. This security permission can be modified using the Component Services administrative tool.

The solution for this DCOM error is to grant the affected user permissions to start the COM component. To solve event ID 10016, follow these steps:

  1. Go to Start – Run, and type regedit, and press enter
  2. Locate and then click the following registry subkey:
    Note In this subkey, “CLSID value” is a placeholder for the CLSID information that appears in the event error. I.e. in case of Sharepoint, the CLSID would be {61738644-F196-11D0-9953-00C04FD919C1},
  3. Double-click on AppID in the right pane, .
    A dialog box appears. Leave this box open
  4. Go to Start – Run, and type dcomcnfg, and press enter
  5. In the Component Services window, go to Component Services, go to Computers, go to My Computer, and then click DCOM Config.
  6. In the details pane, locate the program by using the friendly name, then choose Properties by right clicking on it
  7. At the Security tab, in the Launch and Activation Permissions area, click Customize, and then click the Edit button.
  8. Add the Local Service or Network Service account by clicking the Add button, typing the user’s account name (Local Service or Network Service, this depends on whats in your event error), and then clicking OK.
  9. Select the account name you just added, click to select the Allow check boxes for the following items:
    • Local Launch
    • Remote Launch
    • Local Activation
    • Remote Activation
  10. Click OK two times and quit the registry editor

17 thoughts on “Event 10016: The application-specific permission settings do not grant Local Launch permission for the COM Server application

  1. This resource is just the beginning of learning fun for toddlers and twos.

    t it be nice if we could sneak in some learning time for them
    as well. Some even feature several voice actors for more variety and characterization.

  2. Howdy just wanted to give you a quick heads up. The text in
    your article seem to be running off the screen in Internet explorer.
    I’m not sure if this is a format issue or something to do
    with web browser compatibility but I thought I’d post
    to let you know. The design look great though!
    Hope you get the problem resolved soon. Many thanks

    1. I have the greyed out issue. I am running Win7 32bit – there is no regedit32. Run regedit and I can find APPID but it isnt friendly. The APPID is the same unfriendly string as the CLSID.

  3. Excellent and clear article.

    For those struggling to find the friendly name (the APPID on my system was the same as the CLSID), you can select the detail view in dcomcnfg, this will allow you to match the key (unfortunately you cannot sort on this column, lazy Microsoft !).

    Hope this helps.

  4. Thanks Christian,

    My boss wants me to be damn sure that I don’t create more problems by fixing this one. Is there any chance that you could post the URL’s to the articles you’ve read about the issue, even if they don’t specifically discuss security?

    Thanks for your help!!

  5. Hi Jacob,

    although my answer has some delay, it’s an interesting question you have. I’m not sure whether it creates a security hole, but to be sure you can always choose NOT to grant rights to Remote Launch and Remote Activation.
    I’ve read several articles and topics about this issue, but no-one ever argued about possible security issues.

  6. Thanks for the post! Very clear and helpful. Before I implement the fix, I was wondering if this will in any way create a security hole on our network. ???

    Thanks for your time!

  7. I had the same error and was able to complete all the steps. Step 6 is misleading. Looking for the friendly name is difficult. In Regedit the name of the app for the CLSID was Network Connect Manager Class. The reason for opening the APPID box is it gives another number that is easier to match in the DCOM config details pane (Netman).

    Waiting to see if the error returns…

Leave a Reply

Your email address will not be published.