SPFoxhole Blog

I have recently started porting my SharePoint labs over to R2 and found something that may help someone out there when struggling with DCOM errors in your event log.  So you are all used to the following error that pops up in your System Event log

And most of you know that the issue is generally pointing to IIS WAMREG Admin Service Component but like all good and thorough SharePointers you will still grab the CLID {blah –1932-blah-1111} and then search your registry for the named key.  Better safe then sorry right?

Recently I have started to notice that once you find that key, and you already know the offending service as its shown in the above screenshot, you will do a dcomcnfg then scroll down to the service in question, right click on it, choose security, and add the account in question giving it Local Launch and Local Activation rights and poof your done.

Little change here.  You may now find if you go in to do this that the area is grayed out.  No joy to be found.  Here is what you need to do to get this working again.  There is new TrustedInstaller account that basically has taken over control and you will need to override that permission to make changes to the WAMREG component.

1. Go back into your registry
2. Find the WAMReg key  'HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{CLSID}
3. Right Click and choose Permissions
4. Choose Advanced and take ownership
5. Close registry and either stop DCOM Service or Restart Server
1. I always do the latter after making any changes in the registry

You should now be able to add your accounts into Dcom.

Hope this helps