Comments on: Fixing those pesky DCOM event log error 10016 in a SharePoint farm environment http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/ The life of yet another consultant Fri, 09 Oct 2009 20:49:32 +0000 http://wordpress.com/ hourly 1 By: Søren Nielsen http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-596 Søren Nielsen Fri, 09 Oct 2009 20:49:32 +0000 http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-596 Hi Marlon I would double check the object and account in question. To find what component the guid in the event log refers to, just search for it in the registry. That will usually yield a class/object name in hkey_classes_root. You might have to do two searches one for the guid from the registry and another for the guid that the first one "points to". One is the interface the other the object. Once objected is locatedgo to the dcomcnfg and check it's set as you expect it to. Adjust a bit, and possibly increase the privileges. Are you in a farm? then you might try to adjust the remote launch permissions as well. Cannot remember if the dcom error occurs on the source or dest server though. Hi Marlon

I would double check the object and account in question. To find what component the guid in the event log refers to, just search for it in the registry. That will usually yield a class/object name in hkey_classes_root. You might have to do two searches one for the guid from the registry and another for the guid that the first one “points to”. One is the interface the other the object.

Once objected is locatedgo to the dcomcnfg and check it’s set as you expect it to. Adjust a bit, and possibly increase the privileges.

Are you in a farm? then you might try to adjust the remote launch permissions as well. Cannot remember if the dcom error occurs on the source or dest server though.

]]> By: Marlon http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-595 Marlon Thu, 08 Oct 2009 09:43:35 +0000 http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-595 Great article Soeren, this solution was a help for many, apparently. I still have the error in the eventviewer with a specific AD user/serviceaccount. I have given this account Local Activation and Local Lauch permissions. Any suggestions on getting rid of this pesky error message?? Great article Soeren, this solution was a help for many, apparently. I still have the error in the eventviewer with a specific AD user/serviceaccount. I have given this account Local Activation and Local Lauch permissions. Any suggestions on getting rid of this pesky error message??

]]> By: Alastair http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-580 Alastair Mon, 17 Aug 2009 10:37:09 +0000 http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-580 many thanks, this simple walk through has saved lots fo frustrating afternoons trying to resolve our DCOM errors!! many thanks, this simple walk through has saved lots fo frustrating afternoons trying to resolve our DCOM errors!!

]]> By: Mike http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-439 Mike Sun, 29 Mar 2009 01:54:52 +0000 http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-439 I tried everything mentioned on numerous forums and nothing worked. Then I read something about Windows firewall and decided to check it since I use Kaspersky Internet Security. Under Windows Firewall, Advanced tab I cleared the check marks for all 1394 and Local Area Connections, rebooted my machine and no more DCOM errors. I'm running Windows XP Home, SP3. I hope this helps someone else. It was driving me crazy. Good luck, Mike I tried everything mentioned on numerous forums and nothing worked. Then I read something about Windows firewall and decided to check it since I use Kaspersky Internet Security. Under Windows Firewall, Advanced tab I cleared the check marks for all 1394 and Local Area Connections, rebooted my machine and no more DCOM errors. I’m running Windows XP Home, SP3. I hope this helps someone else. It was driving me crazy. Good luck, Mike

]]> By: Bob Cummings http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-402 Bob Cummings Wed, 11 Feb 2009 08:40:09 +0000 http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-402 Another satisfied customer! Thanks Another satisfied customer! Thanks

]]> By: SBS 2008 -> SBS BPA 2008 Warnung - MCSEboard.de MCSE Forum http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-401 SBS 2008 -> SBS BPA 2008 Warnung - MCSEboard.de MCSE Forum Tue, 10 Feb 2009 16:14:18 +0000 http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-401 [...] [...] [...] [...]

]]> By: links for 2009-02-09 | Savage Nomads http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-400 links for 2009-02-09 | Savage Nomads Mon, 09 Feb 2009 11:03:19 +0000 http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-400 [...] Fixing those pesky DCOM event log error 10016 in a SharePoint farm environment « Thoughts on comput... ut it for exchange servers (tags: sharepoint dcom moss) [...] [...] Fixing those pesky DCOM event log error 10016 in a SharePoint farm environment « Thoughts on comput… ut it for exchange servers (tags: sharepoint dcom moss) [...]

]]> By: links for 2009-02-09 | benway.net http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-399 links for 2009-02-09 | benway.net Mon, 09 Feb 2009 10:01:37 +0000 http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-399 [...] Fixing those pesky DCOM event log error 10016 in a SharePoint farm environment « Thoughts on comput... ut it for exchange servers (tags: sharepoint dcom moss) [...] [...] Fixing those pesky DCOM event log error 10016 in a SharePoint farm environment « Thoughts on comput… ut it for exchange servers (tags: sharepoint dcom moss) [...]

]]> By: My Error In Sharepoint Server , - Rudy Yulianto http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-391 My Error In Sharepoint Server , - Rudy Yulianto Wed, 07 Jan 2009 05:17:34 +0000 http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-391 [...] http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sha... [...] [...] http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sha... [...]

]]> By: cwxwwwxwwxwx http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-390 cwxwwwxwwxwx Tue, 23 Dec 2008 18:47:19 +0000 http://soerennielsen.wordpress.com/2007/04/16/fixing-those-pesky-dcom-event-log-error-10016-in-a-sharepoint-farm-environment/#comment-390 well, hi admin adn people nice forum indeed. how's life? hope it's introduce branch ;) well, hi admin adn people nice forum indeed. how’s life? hope it’s introduce branch ;)

]]>