Skip to main content

Thinking out aloud - Dave Hunter's SharePoint Blog

Go Search
Home
Blog
  

Locations of visitors to this page


 Useful Links

  Microsoft UK events
  SharePoint 2007 on CodePlex
  SharePoint Community Portal
  SharePoint User Group
  SharePoint Community Portal
  SharePoint Pedia
  SharePoint MSDN Forums
  SharePoint University
Home > Thinking out aloud - Dave Hunter's SharePoint Blog > Posts > DCOM and COM class factory error messages in the event log
My thoughts and findings on Microsoft Information worker technologies, including MCMS and SharePoint 2007 (MOSS).
DCOM and COM class factory error messages in the event log
After giving my SharePoint server a reboot I started to receive DCOM errors in the system event log and Office SharePoint Server and Windows SharePoint Services 3 errors in the application event log.
 
The error details were as follows:
  • DCOM errors
----------------
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date:  18/12/2007
Time:  17:01:50
User:  MOSS\MOSSSvc
Computer: WIN2K3BASE001
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 MOSS\MOSSSvc SID (S-1-5-21-2583425652-4040595884-2567147219-1010).  This security permission can be modified using the Component Services administrative tool.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
  • MOSS errors
---------------
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server General
Event ID: 7888
Date:  18/12/2007
Time:  16:39:01
User:  N/A
Computer: WIN2K3BASE001
Description:
A runtime exception was detected. Details follow.
Message: Retrieving the COM class factory for component with CLSID {3D42CCB1-4665-4620-92A3-478F47389230} failed due to the following error: 80070005.
Techinal Details:
System.UnauthorizedAccessException: Retrieving the COM class factory for component with CLSID {3D42CCB1-4665-4620-92A3-478F47389230} failed due to the following error: 80070005.
   at Microsoft.Office.Server.Search.Administration.SearchApi.RunOnServer[T](CodeToRun`1 remoteCode, CodeToRun`1 localCode, Boolean useCurrentSecurityContext, Int32 versionIn)
   at Microsoft.Office.Server.Search.Administration.SearchApi..ctor(WellKnownSearchCatalogs catalog, SearchSharedApplication application)
   at Microsoft.Office.Server.Search.Administration.SearchSharedApplication.get_SearchApi()
   at Microsoft.Office.Server.UserProfiles.SRPSite.IsImportInProgress(String contentSourceName)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
  • WSS errors
--------------
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Timer
Event ID: 6398
Date:  18/12/2007
Time:  16:38:48
User:  N/A
Computer: WIN2K3BASE001
Description:
The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID d0c66122-171a-4705-b4ff-521f671776fb) threw an exception. More information is included below.
Retrieving the COM class factory for component with CLSID {3D42CCB1-4665-4620-92A3-478F47389230} failed due to the following error: 80070005.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
After some research and investgiation I resolved these issues using the following procedure:
 
  1. Copy the CLSID from the error message.  For example: {61738644-F196-11D0-9953-00C04FD919C1}.
  2. Open regedit, perform a find for the GUID you copied.  This will return back the name of the COM+ component.  In this case IIS WAMREG admin service.  
  3. Open Component Services and drill down to DCOM Config.
  4. Locate the component, right click and select properties.
  5. Select the secuirty tab.
  6. Click edit on the "lauch and activation permissions".
  7. Add the MOSS service account or the account in the event log message.
  8. Grant Local Launch and Local Activation, and click OK.
  9. Perform an IISRESET.
Please Note: You may find Microsoft Office SharePoint Search.  This appears as OSearch in Component Services
 
No more new error messages .... Hope this helps.
  Copyright
This work is licenced under a Creative Commons Attribution-Noncommercial-No Derivative Works 2.0 UK: England & Wales License
  Site Map

Comments

Thanks I have solved error

for more details other link also helpful to me
http://www.sharepointlions.blogspot.com
at 15/05/2008 06:12

GREAT!!!

Thank you Sir!

The service has starter without IISRESET and without errors.
This procedure could be useful also for other problems .

Kind Regards!!

Carlo
at 24/02/2009 12:16

 Dave Hunter

I'm currently a Senior Consultant at Netstore 2e2. I specialise in Microsoft Information Worker technologies (especially MOSS, MCMS and .NET), with over 8 years of experience within this area of specialism. 

I have gained two certifications for MOSS and WSS and look to complete the full certification track soon.

View Dave Hunter's profile on LinkedIn

  Subscribe in a reader


 Latest Posts

I’m attending the first ever SharePoint Saturday in the UK31/08/2010 19:43
I’ve re-joined CIBER UK31/08/2010 19:26
I’ve been Awarded a MVP for SharePoint01/04/2010 19:49
SharePoint 2010 Training on Microsoft E-Learning15/03/2010 17:56
SharePoint UK User Group - Thursday 27th August London Meeting25/08/2009 17:56
CAML Query that filters on the current user23/07/2009 17:50
Microsoft Ramp Up Free SharePoint Developer Training22/07/2009 20:59
How To: Change a SharePoint Application Pool Programmatically07/07/2009 18:08
SharePoint Forums Topping 100 Answers06/07/2009 12:29
Find out the SharePoint Internal Name for a Column or Site Column28/05/2009 09:56
1 - 10 Next