Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Evault Indexing service starts but stops automatically.

Created: 08 Sep 2013 • Updated: 23 Oct 2013 | 6 comments
This issue has been solved. See solution.

Hi All,

I need your help on the issue with my Evault server indexing. The service will start but outmatically stop. I am receiving error messages below. I have also included the Dtrace result below.

Operating system : Windows 2008 R2 Standard SP1

Evault version : 10.0.1.1171

Event 1 :

Log Name:      Symantec Enterprise Vault
Source:        Enterprise Vault
Date:          9/09/2013 1:30:48 PM
Event ID:      41312
Task Category: Index Admin Service
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      auultdwnwsp001.downergroup.internal
Description:
The Indexing Service could not complete all the required startup routines: Starting Index Engine failed. Service will be stopped.

For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp?EvtID=41312
 

Event 2 :

Log Name:      Symantec Enterprise Vault
Source:        Enterprise Vault
Date:          9/09/2013 1:30:48 PM
Event ID:      41335
Task Category: Index Admin Service
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      auultdwnwsp001.downergroup.internal
Description:
An error occured while trying to start indexing engine.
Further error details include: 'Indexing engine failed to wake up : There has been a problem:ExpatError: no element found: line 1, column 0 (ID: CLI_GENERIC_ERROR)'.

For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp?EvtID=41335
 

Dtrace result:

**************************************************************

1453 13:02:20.378  [11560] (EVIndexAdminService) <8608> EV-L {IndexAdminService.OnPerformStartup} Start indexing engine and perform index volume synchronization started
1454 13:02:20.378  [11560] (EVIndexAdminService) <8608> EV-L {IndexingEngineMonitor.WakeUpIndexEngine} Waking up indexing engine
1455 13:02:20.519  [11560] (EVIndexAdminService) <8608> EV-H {VelocityStartStopIndexingEngine.Start} Indexing engine failed to wake up : There has been a problem:ExpatError: no element found: line 1, column 0 (ID: CLI_GENERIC_ERROR)
1456 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV~E |Event ID: 41335 An error occured while trying to start indexing engine.|Further error details include: 'Indexing engine failed to wake up : There has been a problem:ExpatError: no element found: line 1, column 0 (ID: CLI_GENERIC_ERROR)'.
1457 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV-H {VelocityStartStopIndexingEngine.Start} Some of the processes did not start, shutdown indexing engine
1458 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV-L {IndexingEngineMonitor.WakeUpIndexEngine} WakeUpIndexEngine completed
1459 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV-H {IndexAdminService.OnPerformStartup} The Indexing Service could not complete all the required startup routine: Starting Index Engine failed.. Service will be stopped.
1460 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV~E |Event ID: 41312 The Indexing Service could not complete all the required startup routines: Starting Index Engine failed. Service will be stopped.
1461 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV-H {ServiceBaseEx.Run} Exception of type 'KVS.EnterpriseVault.Common.ServiceBaseExException' was thrown.
1462 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV-L {ServiceBaseEx.Run} Executing OnPerformShutdown()
1463 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV-L {IndexAdminService.OnPerformShutdown} Starting Index Admin Service shutdown routines in a background thread
1464 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV-L {IndexAdminService.OnPerformShutdown} Miscellaneous indexing service shutdown tasks started
1465 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV-H {EVIndexAdminUtils.InvokeHelper} Calling Void <OnPerformShutdown>b__16(). Reference: Stopping StorageRevisionDiscovery
1466 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV-H {StoragePendingWorkDiscovery.Stop} StoragePendingWorkDiscovery stopping
1467 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV-L {IndexAdminService.OnPerformShutdown} Miscellaneous indexing service shutdown tasks completed (0 ms)
1468 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV-L {IndexAdminService.OnPerformShutdown} Stop child processes and unregister indexing service endpoints started
1469 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV-L {StateManager.UnregisterForDCOMClient} Inside UnregisterForDCOMClient
1470 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV-L {StateManager.StopChildProcesses} Stopping child processes of Index Admin Service.
1471 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV-L {StateManager.StopChildProcesses} Stopping child processes: {EVIndexVolumesProcessor,EVIndexQueryServer}
1472 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV-L {ChildProcessManager.StopChildProcesses} Stopping child processes of Indexing Service [Max shutdown time: 900000 ms].
1473 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV-L {ChildProcessManager.StopChildProcesses} Stopping child process 'EVIndexVolumesProcessor'
1474 13:02:20.534  [11560] (EVIndexAdminService) <8608> EV-L {ChildProcessManager.StopChildProcesses} Stopping child process 'EVIndexQueryServer'
 

Operating Systems:

Comments 6 CommentsJump to latest comment

JesusWept3's picture

Check this Technote, suggests performing a reinstall of the indexing engine

http://www.symantec.com/business/support/index?pag...

Pradeep_Papnai's picture

Please check the tech note below. 

64 bit Indexing Engine fails to start up with error "Indexing engine failed to wake up" http://www.symantec.com/docs/TECH202130

SOLUTION
RyanKim's picture

Hi Guys,

 

Thanks for your comments. Will there be no issue with the current archives once Indexing engine was re-installed?

 

Regards,

Advisor's picture

Hello RyanKim,

Resetting Indexing engine does not actually delete/modify archived data, hence there is no impact on current archives. After resetting the engine, it will initialize and update/sync the indexes metedata.

Pradeep_Papnai's picture

AS mentioned the cause in TN "This problem is the result of the core data files used by the 64 bit Indexing Engine becoming corrupted"

If you reset indexing engine, it just update indexing files and Your archive can still be search. Or in other words, resetting index engine does not have any impact on archives.
 

RyanKim's picture

Hi All,

 

Thanks for the feedback. The issue was resolve after reinstalling index service.