Here's the detailed error description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
to the user SERVERNAME\xxxuser (S-1-5-20). This security permission can be modified using the Component Services administrative tool.
To me, this error is related to an IIS misconfiguration more than to a SharePoint error.
61738644-F196-11D0-9953-00C04FD919C1 is in fact the key for the service “IIS WAMREG Admin Service”. You can check this looking in HKCR.
A simple solution under Windows 2003 and Windows 2008 is to run dcomcnfg and give the service account (which is indicated in the event log error) rights to Launch and Activate IIS WAMREG Admin Service.
To do so:
- Click Start
- Click Run
- Type "dcomcnfg" and click ok
- Expand Component Services / Computers / My Computer / DCOM Config
- Scroll down and find IIS WAMREG admin Service.
- Right click on it
- Click the Security tab
- Click Edit under Launch and Activation Permissions
- Click the Add... button.
- Enter the name of the Service Account for your Configuration Service
- Click OK
- In the Permission for your username, check these boxes: allow Local Launch and allow Local Activation rights.
- Click OK
- Click OK once again
Unfortunately, if you are working (as I was) in a Windows 2008 R2 environment, the solution is a bit harder, because, as I could discover, I had first to unlock the Launch and Activation Permission windows, which was greyed out due to lack of permissions.
Under Windows 2008 R2 the permission for this service for the Administrator accout is limitied to "Read". So:
- Start Regedit (Click on Start/Run/Regedit)
- Type F3
- Search for the string 61738644-F196-11D0-9953-00C04FD919C1
- Then right click on the key
- Click Advanced in the Permissions dialog of this key
- Select the Owner tab.
- Change the owner of the key to the administrators group for example
- Set full control to the administrators group. (Remember not to make ANY modification to the permissions for the TrustedInstaller!!)
You should no longer see the annoying DCOM 1006 errors in your System Event log!