Monday, March 17, 2008

What to do if you get MOSS 2007 COM/W3SVC-WP 80070005 Errors

I recently installed a MOSS 2007 server and applied several service packs, including WSS SP1 and MOSS 2007 SP1. This resulted in COM+ application security settings being reset to their default settings, specifically the COM+ application, OSearch.

The event viewer revealed the following error, for me:

The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID 86e55a13-e654-4458-aa3c-87f910d6ec9e) 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.

Other associated errors produced by this problemare shown below and can be resolved by the following steps:

Starting up database 'SharedServices1_Search_DB_GUID'.

The worker process failed to initialize the http.sys communication or the w3svc communication layer and therefore could not be started. The data field contains the error number.

Unable to reach Excel Calculation Services http://HOSTNAME:PORT/SharedServicesProvider/ExcelCalculationServer/ExcelService.asmx.

Ensure that all Relevant COM+ Applications are Accessible by the ASPNET, WSS & Service Accounts

To fix this problem, follow these steps on the computer hosting MOSS 2007:

  1. Click on the Windows' Start button.
  2. Click on Run.
  3. Type "%WINDIR%\system32\Com\comexp.msc" (without quotes), then press the Enter key.
  4. Navigate to the Component Services, Computers, My Computer, DCOM Config folder.
  5. Right-click on the OSearch application, then click on Properties.
  6. Click on the Security tab.
  7. In the Launch and Activation section, click on Edit.
  8. Ensure that any and all WSS* accounts are listed. If they are not, add them.
  9. Grant these accounts all of the permissions available.
  10. Click on OK.
  11. In the Access Permissions section, click on Edit.
  12. Ensure that all of the the ASPNET, WSS*, and SP service accounts are listed. If they are not, add them.
  13. Grant these accounts all of the permissions available.
  14. Click on OK twice.
  15. Repeat steps 5 through 14 above for the following other SP COM applications: SharedAccess, SPSearch.
  16. Restart IIS by running "iisreset" (without quotes) from a command prompt.

Ensure that the Identity Account is the Same Across All WSS/MOSS Shared Services (ONLY) Web Application Pools

  1. Login to SharePoint Central Administration.
  2. Under Central Administration, click on Operations.
  3. Under Security Configuration, click on Service accounts.
  4. Select Web application pool.
  5. Select the Web Service pool.
  6. Select the affected Web service.
  7. In the list of Application pools, for each Shared Service Pool, configure the account to be the same and that that account has been granted access to the COM+ applications in the preceding section.
  8. Click on OK once done.
  9. Restart IIS6 by executing "iisreset" from the Windows' Run dialog box.


DotNetGuts said...

Good Work. Its Helpful.


Web Design Quote said...


First time in have visited your blog i think its really helpful,because you give us the information different software the operating process.