cloud.net Where the unpredictable sky meets the logical nature of .net programming.

Sunday, April 27, 2008

{61738644-F196-11D0-9953-00C04FD919C1} Local Activation SharePoint

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date: 27/04/2008
Time: 9:35:28 AM
User: VMDomain\SPConfigAcct
Computer: VMDEV
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 VMDomain\SPConfigAcct SID (S-1-5-21-2183741768-1351022156-4028051374-1111). This security permission can be modified using the Component Services administrative tool.

The event kind of tells you how to fix it: "This security permission can be modified using the Component Services administrative tool". But first we need to figure out what 61738644-F196-11D0-9953-00C04FD919C1 is; Win + R > regedit > search = IIS WAMREG admin Service
  1. Win + R C:\WINDOWS\system32\Com\comexp.msc
  2. Expand Component Services > Computers > My Comp > DCOM Config
  3. Right Click IIS WAMREG admin Service
  4. Select Properties > Security
  5. Launch and Activation Permissions "Customize" > Edit
  6. You need to grant the "user" rights.
  7. My user is a SharePoint Config account and as such belongs to the IIS_WPG group, but is also the sole member of WSS_RESTRICTED_WPG group so using the safest security I'm going to use WSS_RESTRICTED_WPG until more errors appear.
    Because it's not going to need to lauch or activate remotely I just need to enable "Local".

3 comments:

Anonymous said...

So in my case, I have a default install of Small Business Server 2008 (that has SharePoint). I don't have anyone modifying any SharePoint site. I am getting these errors (61738644-F196-11D0-9953-00C04FD919C1) and don't want to assign a permission; since I have no specific person needing this.

Ray Proffitt said...

When you install SP it doesn't set the DCOM permissions up properly for the SP Config account... has nothing to do with people modifying an SP site.

David said...

Thanks for posting this - helped me get rid of that annoying error.