SBS 2011: DistrubutedCOM Error 10016

Pay no atten­tion to the DCOM behind the cur­tain!
On your SBS 2011 serv­er, do you find a lot of DCOM errors in your Sys­tem Event Log? These are rel­a­tive­ly com­mon on SBS box­es. Microsoft’s guid­ance is that these can be safe­ly ignored. How­ev­er, when an error is report­ed, I expect it to be some­thing that should be inves­ti­gat­ed. If it can be ignored, it shouldn’t be report­ing it as an error. For­tu­nate­ly, there is a fix for these.

Each event list­ed below is has the same alert lev­el of “Error” and the same Event ID “10016”. The fix­es are all most­ly the same with a few dif­fer­ences. Below, I out­line each spe­cif­ic error I saw on a spe­cif­ic SBS 2011 box and high­light the dif­fer­ences in fix­ing each dif­fer­ent error. The key dif­fer­ences are the dif­fer­ent user account account miss­ing the rights and the dif­fer­ent CLSID and APPID. If you find oth­er DCOM errors that this fix works on, let me know and I’ll add it to the list.
Event Infor­ma­tion:

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Event ID: 10016
Level: Error
User: NETWORK SERVICE

CLSID 90DCAB7F-347C-4BFC-B543-540326305FBE

Description: The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {90DCAB7F-347C-4BFC-B543-540326305FBE} and APPID {FA3FC5CF-0304-4CAC-99F0-032AC2B15D1E} to the user NT AUTHORITYNETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

To Fix This Error:

  1. Open reged­it and select “HKEY_CLASSES_ROOT
  2. Go the Edit menu and select “Find…” (Ctrl+F)
  3. Enter the APPID in the search dia­log and press find: FA3FC5CF-0304-4CAC-99F0-032AC2B15D1E
  4. Right click on the key and select per­mis­sions
  5. Click the Advanced But­ton and select the Own­er tab
  6. Take own­er­ship of the object, check the “Replace Own­er on Sub­con­tain­ers” and Objects check-box, and press OK
  7. Grant “Admin­is­tra­tors” Full Con­trol and press OK
  8. Note the default val­ue of the found reg­istry key. Should be: “File Serv­er Resource Man­age­ment Ser­vice”. Close the reg­istry edi­tor.
  9. Launch the Com­po­nent Ser­vices MMC: Start → Run → comexp.msc (make sure to run as admin­is­tra­tor if using UAC)
  10. Expand: Com­po­nent Ser­vices → Com­put­ers → My Com­put­er → DCOM Con­fig
  11. Find “File Serv­er Resource Man­age­ment Ser­vice”, right click it and select prop­er­ties
  12. Select the Secu­ri­ty Tab and press the “Edit…” but­ton in the “Launch and Acti­va­tion Per­mis­sions” group box
  13. Select the “Net­work Ser­vice” account, check the “Local Acti­va­tion” right and press OK.
  14. Click OK and close the Win­dows. The DCOM error should be resolved.

CLSID 61738644-F196-11D0-9953-00C04FD919C1


Description: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1} and APPID {61738644-F196-11D0-9953-00C04FD919C1} to the user DOMAINNAMEspfarm SID (S-1-5-21-123456789-123456789-123456789-1157) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

To Fix This Error:
Fol­low the same steps as shown above except:

  • Step 3: 61738644-F196-11D0-9953-00C04FD919C1
  • Step 8 and 11: IIS WAMREG admin Ser­vice
  • Step 13: Share­Point Farm Account

CLSID 000C101C-0000-0000-C000-000000000046


Description: The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {000C101C-0000-0000-C000-000000000046} and APPID {000C101C-0000-0000-C000-000000000046} to the user DOMAINNAMEspfarm SID (S-1-5-21-123456789-123456789-123456789-1157) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

To Fix This Error:
Fol­low the same steps as shown above except:

  • Step 3: 000C101C-0000-0000-C000-000000000046
  • Step 4: Instead of search­ing, nav­i­gate to: HKEY_CLASSES_ROOTWow6432NodeAppID{000C101C-0000-0000-C000-000000000046}
  • Step 8: (Val­ue Not Set)
  • Step 11: The DCOM Appli­ca­tion ID will be named by its CLSID/APPID instead of short name: {000C101C-0000-0000-C000-000000000046}
  • Step 13: If “Share­Point Farm Account” is not list­ed, add DOMAIN­NAME­sp­farm and then add the rights.

14 comments

  1. Killer info! I got as far as mod­i­fy­ing a DCOM com­po­nent only to find all the set­tings greyed out. By chang­ing the Reg Key I was able to edit and fix the DCOM errors. You Rock!

  2. Thanks for this info. Very help­ful as I’m get­ting about 60 of these errors a day and it real­ly clogs up the event view­er when I fil­ter for errors and warn­ings.

  3. Thanks for the info, been dri­ving me around the bend try­ing to work out why, now it seems to have fixed my issues.
    Hope­ful­ly I can get on with some oth­er work now.

  4. You know what this looks like? Tak­ing the IIS WAMREG app for exam­ple, the default own­er­ship and per­mis­sions on the key are for administrator@domain.local. Of course when set­ting up a serv­er, nobody calls the admin­is­tra­tor account “admin­is­tra­tor”!

    So it looks like a throw­back to the old days when there was always an account called “admin­is­tra­tor”, but seems nobody has told the M$ teams respon­si­ble for these apps!!

  5. At {000C101C-0000-0000-C000-000000000046}

    Step 13:
    Yes > “Share­Point Farm Account” is not list­ed

    I do not under­stand this last step: add DOMAIN­NAME­sp­farm and then add the rights.

  6. Thank you very much for this instruc­tion. unbe­liev­able that SBS has so many DCom errors, nev­er ends!

  7. Fol­lowed all the steps for the {000C101C-0000-0000-C000-000000000046} error up to step #12. All the set­tings are grayed out as post­ed by Kel­ly on Jan. 12th, how­ev­er I don’t under­stand Kelly’s fix, “chang­ing the reg key”. What reg key, and chang­ing it how? I found and fol­lowed this arti­cle http://www.experts-exchange.com/Security/Misc/Q_26770843.html but still no joy.

    Please help. Thanks.

  8. Hi,

    I have fol­lowed all of the above steps, very detailed. How­ev­er I am still receiv­ing the DCOM errors.

    The machine-default per­mis­sion set­tings do not grant Local Acti­va­tion per­mis­sion for the COM Serv­er appli­ca­tion with CLSID
    {90DCAB7F-347C-4BFC-B543-540326305FBE}
    and APPID
    {FA3FC5CF-0304-4CAC-99F0-032AC2B15D1E}
    to the user NT AUTHORITYNETWORK SERVICE SID (S-1-5-20) from address Local­Host (Using LRPC). This secu­ri­ty per­mis­sion can be mod­i­fied using the Com­po­nent Ser­vices admin­is­tra­tive tool.

    Any advice would be great­ly appre­ci­at­ed.

    Thanks.

  9. If I do have the CLSID {B15C0E47-C391-45B9-95C8-EB596C853F3A}-type of prob­lem, how do I find out about which AppId’s Sec­Set­tings I have to edit in the reg­istry in step 3?

  10. Now you have to restart the dcom­c­n­fg appli­ca­tion and once find the IIS WAMREG appli­ca­tion and then set the Launch and Acti­va­tion set­tings that you need to get rid of the DCOM 10016 error.

Comments are closed.