Monday, 31 October 2011

DCOM errors in MOSS

Event log error messages 10016 and 10017


DCOM errors in the System log are associated with application pool accounts. 
Add these accounts to the IISWAMREG admin service. 
Make sure the accounts have local launch, remote launch, local activation, and remote activation

DCOM errors after upgrading MOSS 

These are caused by the updates clearing the activation permissions for the OSearch service (Microsoft Office Server Search) service.

Errors in the Application event log:

Event ID 6398
The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID b94e8106-b5f9-4c2d-ad98-2871bcc4c669) 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.


Event ID 6482
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (7d8b475a-6dda-47e8-8ab7-dbd171926b39).
Reason: Retrieving the COM class factory for component with CLSID {3D42CCB1-4665-4620-92A3-478F47389230} failed due to the following error: 8007000e.

You need to grant the service account that is used by “Office SharePoint Server Search” with Local Activation rights.

Open Component Services->DCOM Config->OSearch->Properties->Security, I added Network Service (may not need) and the account to run “Office SharePoint Server Search” service and gave them “Local Activation” rights (in “Launch and Activation Permissions” group).

In order to re-apply these settings use the start menu to go to:

·         Administrative Tools --> Component Services

In the left tab select:
·         Console Root

           Component Service --> Computers --> My Computer --> DCOM Config --> OSearch


Right Click on OSearch and go to properties
Click the Security Tab

Click “Edit” under Launch and Activation Permissions
·         Add the local group WSS_ADMIN_WPG
·         Add the local group WSS_WGP

·         e.g. INDEX01/WSS_ADMIN_WPG and INDEX01/WSS_WPG

·         Edit these groups to have local launch and local activation permissions

Click “Edit” under Access Permissions
·         Add the local group WSS_ADMIN_WGP and the local group WSS_WGP to have local access permissions

Click “Edit” under Configuration Permissions
·         Add the local group WSS_ADMIN_WGP and the local group WSS_WGP to have Full Control and Read permissions.

Repeat this process on all MOSS servers in the farm


Scripted:


·         This runs dcomperm.exe to fix DCOM errors that may appear post install

·         Sets local activation permission on mssearch.exe for svcmossprimary, svcmossssp, svcmossappid

·         First need to download dcomperm.exe to location _SOURCE

cmd.exe /c “_SOURCE\dcom\dcomperm.exe" –al 3D42CCB1-4665-4620-92A3-478F47389230}
set domain\farmaccount permit level:la
                                                               
This script sets DCOM Permission Level for the SSP service account

cmd.exe /c  “_SOURCE\dcom\dcomperm.exe” –al {3D42CCB1-4665-4620-92A3-478F47389230} set domain\svcmossssp permit level:la

This script sets DCOM Permission Level for a web application – application pool ID

cmd.exe /c  “_SOURCE\dcom\dcomperm.exe” –al {3D42CCB1-4665-4620-92A3-478F47389230} set domain\apppoolID permit level:la



















No comments:

Post a Comment