Clearwell Enterprise Vault Collection fails with "[#422293] Unexpected error - Index: 0, Size: 0"

  • Modified Date:
  • Article ID:000087154


Clearwell Enterprise Vault (EV) Collection fails with "[#422293] Unexpected error - Index: 0, Size: 0"  during the collection of items from EV Journal archives.


Error Message

Failed: com.teneo.esa.icp.collection.ev.EVContentRetrieverSpec@abcdef01: [#422293] Unexpected error - Index: 0, Size: 0



When number of results returned by the Searcher is exactly equal to the content batch size defined internally by the application (defaults to 2000 messages), the collector could go into a loop waiting for more content.



Resolved in version 7.1.2 FIX 2  (ESA-28597)

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.

Symantec Corporation currently plans to address this issue by way of a patch or hotfix to the current version of the software. Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here. A link to the patch or hotfix download will be added to this document when it becomes available. 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.




A. Add/Modify the ESA property

Provide a value of either 2000 or 2500 

(System | Support Features | Property Browser)

  1. Name of property to change: esa.icp.collection.ev.content


  2. BatchSizeNew value (leave blank to remove): 2000


  3. Confirm change. Are you sure?*:  check


  4. Submit



B. Retry the Collection Task.


Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)