In case data were archived with an old Enterprise Vault release (pre-EV 8.0) an index rebuild could generate numerous Storage Crawler errors with Event ID 6882.
The same error could also be logged if users try to retrieve the same archived items.
Source: Enterprise Vault
Category: Trace (Index Query Server)
The processing of the Rebuild Sub task has stopped following errors.
Error Type: FrenzyErrorDetected
Error 1: Error encountered whilst trying to fetch item Sequence Number '1' Item Identifier '201006040000000~200808291228240000~Z~525D56FDF5A04E89A119C12F5B6DFC60'
Error Code: 60
Description:Too many failed consecutive items
Error encountered whilst trying to fetch item Sequence Number '1' Item Identifier '201006040000000~200808291228240000~Z~525D56FDF5A04E89A119C12F5B6DFC60'
Error encountered whilst trying to fetch item Sequence Number '25' Item Identifier '201006040000000~200808280742350000~Z~EFA521DAE7F94EA19D0B9D0137B49A90'
This is caused by an invalid check in Enterprise Vault 10.0.1 retrieving TransactionIDs created with a pre-EV 8.0 release.
TransactionIDs created with a pre-EV 8.0 are composed by 31 characters (such as 525D56FDF5A04E89A119C12F5B6DFC6), while from Enterprise Vault 8.0 (when the Optimized Single Instance Storage was introduced) the TransactionIDs are composed by 32 characters (such as EFA521DAE7F94EA19D0B9D0137B49A90), an additional check introduced by EV 10.0.1 has actually broken the retrieving mechanism causing the errors during retrieve, index rebuild and also with EVSVR dump operations.
This issue has been addressed in the following releases:
Enterprise Vault 9.0.4 Cumulative Hotfix 5 Release
Enterprise Vault 10.0.3 - Release Details
Enterprise Vault 10.0.1
Enterprise Vault 10.0.2