cancel
Showing results for 
Search instead for 
Did you mean: 

index service does not start

vaultlearner
Level 4
Partner Accredited

Hello,

I have this EV on my lab enviroment. Today I saw index service in not starting. Event log is :

The Index Volume Processor could not complete all the required startup routines: Microsoft.Practices.Unity.ResolutionFailedException: Resolution of the dependency failed, type = "Symantec.EnterpriseVault.Indexing.IndexVolumesProcessor.IndexVolumesManager", name = "(none)".

Exception occurred while: Calling constructor Symantec.EnterpriseVault.Common.AuthManager.AuthManager().

Exception is: FileNotFoundException - Retrieving the COM class factory for component with CLSID {F4D2BC89-B8D5-4130-BFA2-3F8B6472A2AA} failed due to the following error: 8007007e The specified module could not be found. (Exception from HRESULT: 0x8007007E).

-----------------------------------------------

At the time of the exception, the container was:

 

  Resolving Symantec.EnterpriseVault.Indexing.IndexVolumesProcessor.IndexVolumesManager,(none)

  Resolving parameter "IndexingEngine" of constructor Symantec.EnterpriseVault.Indexing.IndexVolumesProcessor.IndexVolumesManager(Symantec.EnterpriseVault.Runtime.Queuing.ProcessingQueue synchroniseProcessingQueue, Symantec.EnterpriseVault.Runtime.Queuing.ProcessingQueue subTaskProcessingQueue, Symantec.EnterpriseVault.Indexing.IndexVolumesProcessor.WorkItemsQueue workItemQueue, Symantec.EnterpriseVault.Runtime.Queuing.ProcessingQueue deleteIndexVolumeProcessingQueue, Symantec.EnterpriseVault.Runtime.Queuing.SimpleThreadSafeQueue`1[[Symantec.EnterpriseVault.Indexing.IndexVolumesProcessor.TaskDescriptor, EVIndexVolumesProcessor, Version=12.2.0.0, Culture=neutral, PublicKeyToken=26c5e2ccf2b9267c]] taskList, Symantec.EnterpriseVault.Indexing.IndexVolumesProcessor.ActiveIndexVolumeAgentList activeIndexVolumeAgentList, Symantec.EnterpriseVault.Indexing.IndexVolumesProcessor.Common.IIndexVolumesProcessorServerConfig configuration, Symantec.EnterpriseVault.Indexing.IndexVolumesProcessor.Diagnostics.IIVPPerformanceCounters PerformanceCounters, Symantec.EnterpriseVault.Indexing.IndexingEngine.IIndexingEngine IndexingEngine, Symantec.EnterpriseVault.Indexing.ContentSource.IContentSourceAccessor ContentSourceAccessor, Symantec.EnterpriseVault.Indexing.IndexVolumesProcessor.QueueLockObject queueLockObject, Symantec.EnterpriseVault.Indexing.IndexVolumesProcessor.IndexVolumesManagerObjectFactory ObjectFactory)

    Resolving Symantec.EnterpriseVault.Indexing.IndexingEngine.Index EngineIndexingEngine,(none) (mapped from Symantec.EnterpriseVault.Indexing.IndexingEngine.IIndexingEngine, (none))

    Resolving parameter "contentSourceAccessor" of constructor Symantec.EnterpriseVault.Indexing.IndexingEngine.Index EngineIndexingEngine(Symantec.EnterpriseVault.Indexing.IndexingEngine.Index EngineProxy Index EngineProxy, Symantec.EnterpriseVault.Indexing.IndexingEngine.Index VolumeTemplateSelector Index VolumeTemplateSelector, Symantec.EnterpriseVault.Indexing.ContentSource.IContentSourceAccessor contentSourceAccessor)

      Resolving Symantec.EnterpriseVault.Indexing.ContentSource.EVContentSourceAccessor,(none) (mapped from Symantec.EnterpriseVault.Indexing.ContentSource.IContentSourceAccessor, (none))

      Resolving parameter "authManager" of constructor Symantec.EnterpriseVault.Indexing.ContentSource.EVContentSourceAccessor(Symantec.EnterpriseVault.Indexing.ContentSource.EVObjectFactory objectFactory, Symantec.EnterpriseVault.Indexing.ContentSource.AuditStatusListManager auditStatusListManager, Symantec.EnterpriseVault.Indexing.ContentSource.EVStoreDatabaseCommand storeDatabaseAccess, Symantec.EnterpriseVault.Indexing.ContentSource.EVAdminServiceAccessor adminServiceAccessor, Symantec.EnterpriseVault.Common.AuthManager.AuthManager authManager)

        Resolving Symantec.EnterpriseVault.Common.AuthManager.AuthManager,(none)

        Calling constructor Symantec.EnterpriseVault.Common.AuthManager.AuthManager()

 ---> System.IO.FileNotFoundException: Retrieving the COM class factory for component with CLSID {F4D2BC89-B8D5-4130-BFA2-3F8B6472A2AA} failed due to the following error: 8007007e The specified module could not be found. (Exception from HRESULT: 0x8007007E).

   at Symant

 

For more information, see Help and Support Center at http://telemetry.community.veritas.com/entt?product=ev&language=english&version=12.2.0.0&build=12.2....

 Version 12.2.0, Event id 41312

Count not find any information about this issue

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions

VirgilDobos
Level 6
Partner    VIP    Accredited Certified

Hi there,

I would suggest to run the Deployment Scanner and confirm all IIS/OS prereqs are in place, then run a repair of the EV binaries and check again.

--Virgil

View solution in original post

2 REPLIES 2

VirgilDobos
Level 6
Partner    VIP    Accredited Certified

Hi there,

I would suggest to run the Deployment Scanner and confirm all IIS/OS prereqs are in place, then run a repair of the EV binaries and check again.

--Virgil

View solution in original post

vaultlearner
Level 4
Partner Accredited

Hi,

 

Thank you reinstalling Ev Binaries works for me. I followed this article https://www.veritas.com/support/en_US/article.100025472 but as in the article 6. is not valid anymore I selected repair instead of that.

Thanks

Vaultleaner.