Fixing those pesky DCOM event log error 10016 in a SharePoint farm environment

I’m responsible for a couple of SharePoint 2007 (MOSS) farms where all SharePoint servers showed the following error in the system event log:


Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date: 1/17/2007
Time: 4:31:48 AM
User: <DOMAIN>\sa_adm
Computer: <SERVER>
Description:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{61738644-F196-11D0-9953-00C04FD919C1}

to the user <DOMAIN>\sa_adm SID (S-1-5-21-162740987-2502514208-3469184634-1119). This security permission can be modified using the Component Services administrative tool.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The error would show up at regular intervals in clusters (4-12 at roughly the same time) and there would be a few more with other usernames and other class id’s. I had two fully functional farms with 3 SharePoint servers each and a number of standalone development machines. They all exhibited similar behavior.

The error listed above is that the user running the Central Administration web application doesn’t have access to activate (instantiate) the IIS WAMREG admin Service object (search the registry for the CLSID).

Strangely enough I didn’t observe any functional errors in the farms as a result of these errors – nothing seemed amiss (plenty of stuff didn’t work but none directly related to this).

An important note here is that the service users used in the farm are all standard domain accounts and only given additional local rights by the SharePoint installer and Central Administration (The one exception is that “aspnet_regiis -ga IIS_WPG” was executed after SharePoint install and initial configuration).

The following procedure removes the errors from the event log without compromising the entire security setup (yes, assign administrative rights for the service users would do the trick too) and has been verified by Microsoft consulting services.

On each SharePoint server do the following:

  1. Click Start, Click Run, type “dcomcnfg” and click ok
  2. Expand Component Services / Computers / My Computer / DCOM Config

  3. Right click IIS WAMREG admin Service and choose Properties
  4. Click the Security tag
  5. Click Edit under Launch and Activation Permissions

  6. Click Add
  7. In the Select Users, Computers or Groups type computername\WSS_WPG and
    computername\WSS_ADMIN_WPG

  8. Click ok
  9. In the Permissions for UserName list, click to select the Allow check box

  10. Click Ok twice.
  11. Go back to the main Component Services window, right click the “netman” node and select Properties
  12. Click the security tab
  13. Click Edit under Activation Permissions
  14. Click Add on the Launch Permissons Dialog
  15. Enter “NETWORK SERVICE” in the edit box
  16. Click Ok
  17. Enable all the checkboxes for the NETWORK SERVICE

  18. Click Ok twice
  19. Finally, run “IISReset”

That should be it!

A little less event log errors to worry about – there are plenty left on a reasonable complex SharePoint farm…

As a side note: The above error also shows up in other applications as well – I’ve heard about it for exchange servers as well and more applications are probably affected. In that case you’ll need to search the registry for the actual DCOM application and assign the rights to another local group (or username as a last resort).

Advertisements

About Søren Nielsen
Long time SharePoint Consultant.

46 Responses to Fixing those pesky DCOM event log error 10016 in a SharePoint farm environment

  1. Alpesh Nakar says:

    You are a rockstar. We have this error. Will try on Monday and see if it fixes the proble, 🙂

    Cheers!
    Alpesh

  2. Happy to help 🙂

  3. Spence you are right, it’s pretty much the same.

    It appears that harbar was actually first.. Oh well.

    We even used almost the same title. LOL.

  4. Krishna says:

    I was experiencing this error and I tried all different procedures to stop this error messages.

    Thanx for the detailed presentation.

    – Krishna

  5. Pingback: En finir avec les erreurs DCOM 10016 - SharePoint of View

  6. Pingback: Nerfed Tech » Blog Archive

  7. Rob says:

    Thsi worked for me thanks alot

  8. oliver says:

    This process makes sense until you get to step 11. What does it mean to “Go back to the main Component Services window, right click the “netman” node and select Properties”? What is the “main Component Services window”? What is “netman”?

    Thanks,

    oliver

  9. Great tip – thanks for posting!

    Kenneth

  10. Frank says:

    Good stuff.

    Thanks

  11. Frank says:

    Components Services window is the dcomconfig where you found the IIS WAMREG Admin.

    Good Luck

    Frank

  12. Rob T says:

    This worked great. Don’t know how or why these settings get hosed, but site is back up now.

    Thanks!

  13. Steve Self says:

    GREAT INSTRUCTIONS U DA MAN!!!

  14. Jack says:

    Excellent. Thanks

  15. Søren Nielsen says:

    Manish: I see nothing new in your article. The difference is?

  16. Pingback: roadburn’s sharepoint 2007 blog » Blog Archive » Event ID 10016: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

  17. Pingback: Eliminating DCOM errors « BDBits Bytes

  18. bibin says:

    Thank u so much
    i solvel my problem

  19. doze says:

    Thank You!

    Works like a charm!

    Greets Manuel

  20. Pingback: Malcolm Gin’s SharePoint and .NET Tips » Blog Archive » DCOM 10016 errors

  21. George says:

    Nice guide. Thanks

  22. cwxwwwxwwxwx says:

    well, hi admin adn people nice forum indeed. how’s life? hope it’s introduce branch 😉

  23. Pingback: My Error In Sharepoint Server , - Rudy Yulianto

  24. Pingback: links for 2009-02-09 | benway.net

  25. Pingback: links for 2009-02-09 | Savage Nomads

  26. Pingback: SBS 2008 -> SBS BPA 2008 Warnung - MCSEboard.de MCSE Forum

  27. Bob Cummings says:

    Another satisfied customer! Thanks

  28. Mike says:

    I tried everything mentioned on numerous forums and nothing worked. Then I read something about Windows firewall and decided to check it since I use Kaspersky Internet Security. Under Windows Firewall, Advanced tab I cleared the check marks for all 1394 and Local Area Connections, rebooted my machine and no more DCOM errors. I’m running Windows XP Home, SP3. I hope this helps someone else. It was driving me crazy. Good luck, Mike

  29. Alastair says:

    many thanks, this simple walk through has saved lots fo frustrating afternoons trying to resolve our DCOM errors!!

  30. Marlon says:

    Great article Soeren, this solution was a help for many, apparently. I still have the error in the eventviewer with a specific AD user/serviceaccount. I have given this account Local Activation and Local Lauch permissions. Any suggestions on getting rid of this pesky error message??

    • Hi Marlon

      I would double check the object and account in question. To find what component the guid in the event log refers to, just search for it in the registry. That will usually yield a class/object name in hkey_classes_root. You might have to do two searches one for the guid from the registry and another for the guid that the first one “points to”. One is the interface the other the object.

      Once objected is locatedgo to the dcomcnfg and check it’s set as you expect it to. Adjust a bit, and possibly increase the privileges.

      Are you in a farm? then you might try to adjust the remote launch permissions as well. Cannot remember if the dcom error occurs on the source or dest server though.

  31. Pingback: 2K8 - SharePoint unter SBS2008 aufrufen + Fehler - MCSEboard.de MCSE Forum

  32. Edwin says:

    Thanks for the good explanation.

  33. Pingback: Editing IIS WAMREG Properties in Windows Server 2008 R2 « SharePoint Nick

  34. Matt says:

    On windows server 2008R2 I was not able to make the changes to the dcom settings because they were all grayed out… I had to go into the registry and give myself permissions to do it… I followed this post:
    http://blogs.msdn.com/b/emeadaxsupport/archive/2010/01/26/unable-to-edit-the-dcom-settings-for-iis-wamreg-admin-service-on-a-windows-server-2008-r2-when-trying-to-configure-kerberos-authentication-for-role-centers.aspx

    *Make sure to change the owner/permissions back… I don’t know what might break if you don’t, but I don’t want to find out either. 🙂

  35. Pingback: SharePoint 2010 and TFS 2010 Integration Checklist | headcrash industries | blog

  36. Pingback: Adventures upgrading to SharePoint 2010 | SoftArtisans, Blogged Adventures upgrading to SharePoint 2010 | The Cathedral and the Bizarre

  37. d2iguy says:

    Right on! This one has been bugging our server for a long time. Thanks for the detailed info!

  38. Pingback: Event 10016 | Monserratedesi

  39. jd says:

    Worked for me, thanks a lot !

  40. Angelo says:

    Thanks for sharing such a good thought, post is nice, thats why i
    have read it completely

  41. Pingback: How To Fix Dcom 10016 Errors - Windows Vista, Windows 7 & 8

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: