Enterprise Vault for Exchange 10.0.1, Index rebuild or retrieve of archived items fail logging the error with Event ID 6882 for the Storage Crawler about 'Unable to complete retrieval request, Reason: The parameter is incorrect (0x80070057)'
| Article:TECH196901 | | | Created: 2012-09-19 | | | Updated: 2012-10-02 | | | Article URL http://www.symantec.com/docs/TECH196901 |
Problem
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.
Error
Date: 01/09/2012
Time: 01:00:01
Event: 41352
Source: Enterprise Vault
Category: Trace (Index Query Server)
User: N/A
Computer: EVSERVER.domain.local
The processing of the Rebuild Sub task has stopped following errors.
Reason: TooManyErrors
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'
Environment
Enterprise Vault 10.0.1
Enterprise Vault 10.0.2
Cause
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.
Solution
This issue will be fixed in Enterprise Vault 10.0.3 **not yet released**
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
There are no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. However, the issue is currently scheduled to be addressed in the next major revision of the product. Please be sure to refer back to this document periodically as any changes to the status of the defect will be reflected here. Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests. Symantec’s plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.
|
|
| Source | UMI |
| Value | V-437-6882 |
| Description | Unable to complete retrieval request
Reason: The parameter is incorrect. (0x80070057) |
| Source | Event ID |
| Value | 6882 |
| Description | Unable to complete retrieval request
Reason: The parameter is incorrect. (0x80070057) |
| Source | UMI |
| Value | V-437-41352 |
| Description | The processing of the Rebuild Sub task has stopped following errors. Rebuild Sub task ID: 14A7308D7C8DA24439F76A1A168DAB5AC1110000vault1_14273 Reason: TooManyErrors Error Type: FrenzyErrorDetected |
| Source | Event ID |
| Value | 41352 |
| Description | The processing of the Rebuild Sub task has stopped following errors. Rebuild Sub task ID: 14A7308D7C8DA24439F76A1A168DAB5AC1110000vault1_14273 Reason: TooManyErrors Error Type: FrenzyErrorDetected |
| Source | ETrack |
| Value | 2926397 |
| Description | 'Unable to complete retrieval request, Reason: The parameter is incorrect (0x80070057)' |
Article URL http://www.symantec.com/docs/TECH196901
Terms of use for this information are found in Legal Notices
Thank you.