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\svcspdev SID (S-1-5-21-3914637029-2275272621-3670275343-1145) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
To rectify this error, first you need to do this on the SharePoint server - Windows Server 2008 R2. You must first take ownership of the corresponding registry key and grant Administrators permissions to update the configuration. If you do not take the ownership and try to add the user, pop-up window will appear and will say “ACCESS IS DENIED”
To grand permission to the configuration of the IIS WAMREG Admin Service to be changed using the Component Services console:
Now you have granted the Administrators group to sufficient permissions, now how to change the IIS WAMREG Admin Service. If you don’t do the previous step and go directly to the component service, all the fields are disabled.
Next step is referred in the KB article KB920783 from Microsoft as follows:
1) Click Start, click Run, type dcomcnfg in the Open box, and then click OK. 2) Expand Component Services, expand Computers, expand My Computer, and then click DCOM Config. 3) Right-click IIS WAMREG admin Service, and then click Properties. 4) Click the Security tab. 5) Under Launch and Activation Permissions, click Edit. 6) In the Launch Permission dialog box, click Add. 7) In the Select Users, Computers, or Groups dialog box, change the location to the local server. Then, type the local security group WSS_WPG, click Check Names, and then click OK. 8) In the Permissions for UserName list, click to select the Allow check box that is next to Local Activation, and then click OK two times.
Richard Mueller edited Revision 7. Comment: Removed (en-US) from title, added tags
Craig Lussier edited Revision 5. Comment: added en-US to tags and title
Great resolution walk through. Thanks for putting this together!
Great, it's always helpfull for the community !!
Beware that this is the instance of a general problem type, all under the same EventId. However, the CLSID /APPIDs vary and so do the measures to be taken to make the DCOM entry writeable. More on the pattern:
halfloaded.com/.../sbs-2011-distributedcom-eventid-10016-fixed
The instance / CLSID&APPD not mentioned above, but my flavor of the problem: http://bit.ly/1dUysjB