Event Id 41312 "Could not obtain the service entry identifier for this service. Service will be stopped." Enterprise Vault Indexing service cannot start

book

Article ID: 100027725

calendar_today

Updated On:

Description

Error Message

Event ID's logged: 

Type :  Error
Date :  01/01/2012
Time :  00:00:01
Event :  41312
Source :  Enterprise Vault
Category : Index Admin Service
User :  N/A
Computer : EVServer.domain.ext
Description:
The Indexing Service could not complete all the required startup routines: Could not obtain the service entry identifier for this service. Service will be stopped.

The service is then stopped: 

V-437-41312

Type :  Information
Date :  01/01/2012
Time :  00:00:02
Event :  41298
Source :  Enterprise Vault
Category : Index Admin Service
User :  N/A
Computer : EVServer.domain.ext
Description:
The Indexing Service has stopped

V-437-41298

 

The dtrace of the EVIndexAdminService contains: 

43 15:09:43.584  [7116] (EVIndexAdminService) <8008> EV-H {EVINDEXADMINUTILS.EN_US} Exception: Retrieving the COM class factory for component with CLSID {4EC6FF78-C97A-11D1-90E0-0000F879BE6A} failed due to the following error: 8007007e. Info: Diag: Type:System.IO.FileNotFoundException ST:   at KVS.EnterpriseVault.Common.Computer.ReadComputerInformation()|   at Symantec.EnterpriseVault.Indexing.Admin.EVIndexAdminUtils.GetServiceEntryIdFromComputerName() Inner:None
44 15:09:43.584  [7116] (EVIndexAdminService) <8008> EV-H {INDEXADMINSERVICE.EN_US} The Indexing Service could not complete all the required startup routines: Could not obtain the service entry identifier for this service. Service will be stopped.
45 15:09:43.600  [7116] (EVIndexAdminService) <8008> EV~E |Event ID: 41312 The Indexing Service could not complete all the required startup routines: Could not obtain the service entry identifier for this service. Service will be stopped.
46 15:09:43.600  [7116] (EVIndexAdminService) <8008> EV-H {EXECUTIONCONTEXT.EN_US} Exception of type 'KVS.EnterpriseVault.Common.ServiceBaseExException' was thrown.

 

Cause

Corruption in the Enterprise Vault Indexing data files.

Resolution

In order to fix the problem it is needed to reset the EV index engine:

  1. Stop the Enterprise Vault Indexing Service on the affected Enterprise Vault Server.
     
  2. Stop the World Wide Web Publishing Service on the affected Enterprise Vault Server.
     
  3. Launch IIS Manager and delete the EVIndexing virtual Directory.
     
  4. Following the deletion of the Indexing virtual directory, delete the EVIndexingPool application pool.

    Note: Do not delete any other virtual directories or application pools as doing so will damage the Enterprise Vault installation.
     
  5. Using windows explorer, navigate to the Enterprise Vault installation Directory and delete the EVIndexing subdirectory

    Note: If Enterprise Vault is clustered the IndexMetaData folder (which is usually found under the EVIndexing subdirectory) may be held in a different location and will need to be deleted separately in addition to deletinig the EVIndexing folder in Step 5. To locate this folder run the below SQL query:

        USE EnterpriseVaultDirectory
        SELECT CE.ComputerName, ISE.MetaDataLocation
        FROM ComputerEntry CE, IndexingServiceEntry ISE
        WHERE CE.ComputerEntryID = ISE.ComputerEntryID

     
  6. Reinstall the Indexing Engine, using the “Veritas Enterprise Vault Indexing Redistributable.msi”. The redistributable file is located on the Enterprise Vault Installation Media, in the following location: "Server/EVTmp"


     Note:  If any indexing hotfix has been applied to the affected Indexing Server, this must be uninstalled before re-installing the Indexing Redistributable. This is done by completing the following steps:
               1. Locate the installation msi used to install the hotfix
               2. Right-click on the msi and select uninstall
               3. The hotfix will be removed and the Indexing Redistributable can now be run
               4. Following the re-installation of the Indexing Server, please ensure to reapply any hotfixes that were previously removed.
 
  1. Restart the Enterprise Vault Indexing Service

Note:  It may take a while for the Indexing service to become fully operational following the reinstallation of the Indexing Engine, as a full Synchronization between Enterprise Vault and the Indexing Engine will be automatically triggered. The commencement and completion of this process will be marked by the following entries in the Enterprise Vault Event Log:

Issue/Introduction

The Enterprise Vault Indexing service cannot be started logging the Event ID 41312 due to possible corrupt EV Indexing Engine.