Index Rebuild fails with event ID 41352.

Problem

During a rebuild or synchronization of an Enterprise Vault (EV) 10.x 64 bit index the rebuild will fail with event ID 41352. A subsequent attempt to retry the rebuild task will result with the rebuild job progressing until it fails again with event ID 41352. Eventually the entire index will successfully rebuild.

Error Message

Log Name:      Symantec Enterprise Vault
Source:            Enterprise Vault
Event ID:          41352
Task Category: Index Volumes Processor
Level:               Error
Computer:       EV01.EV.com

Description:
The processing of the Rebuild Sub task has stopped following errors.

Rebuild Sub task ID: 1E5C010B9E769184591E34B5B5CC61D501110000EVServer_5019
Reason: Undefined
Error Type: NonCritical

Description: Timed out waiting for [Agent Thread for
19EFBD73E879B4FC697191FA7DBE83F341013b00EVServer_1B80E1C89D9C00F439404AC9BDC654D
1C1013a00EVServer_1E5C010B9E769184591E34B5B5CC61D501110000EVServer_5019] to
start after [1800] seconds.

Rebuild Sub task ID: 1E5C010B9E769184591E34B5B5CC61D501110000EVServer_5019
Reason: Undefined
Error Type: NonCritical

Description: Timed out waiting for [Agent Thread for
19EFBD73E879B4FC697191FA7DBE83F341013b00EVServer_1B80E1C89D9C00F439404AC9BDC654D
1C1013a00EVServer_1E5C010B9E769184591E34B5B5CC61D501110000EVServer_5019] to
start after [1800] seconds.</Data>
  </EventData>
</Event>

v-437-41352 

Cause

This issue can occur if the vse_docs table in the indexer.sqlt database in the affected volume is corrupt or inaccessible. 

The indexer.sqlt database is located in the following location:  (i.e.  C:\EVStorage\Index\index7\1420AE29C9113074683732379200994A6_58\live\indexer.sqlt).

Examining the vse_docs table may show corruption or may be inaccessible.

Solution

In the event that it is determined that a table in the affected indexer.sqlt file is corrupt or inaccessible there are two possible resolutions:

• Restore the entire index volume from a point in time when the vse_docs table in the indexer.sqlt file is not corrupt or inaccessible.  Then perform a synchronization from that point.

OR

• Rename the entire index volume to old and rebuild the index volume. In the event the rebuild does not process it may be due to a corrupt repository.xml file. To determine if the repository.xml file is corrupt refer to article 100039337.  If it is determined that the repository.xml file is corrupt follow resolution steps in 100039337. Once the repository.xml has been recreated proceed with the rebuild of the problematic index volume.

Note: Ensure that all antivirus exclusions are in place on the EV server per the link in the Related articles section.