When performing a Compliance Accelerator (CA) or Discovery Accelerator (DA) search, the Info column entry "Some items could not be searched" occurs.

Article:TECH127715  |  Created: 2008-01-30  |  Updated: 2014-08-08  |  Article URL http://www.symantec.com/docs/TECH127715
Article Type
Technical Solution



When performing a search in Enterprise Vault (EV) Compliance Accelerator (CA) or Discovery Accelerator (DA), the Info column entry "Some items could not be searched" occurs.



Some items could not be searched. 

Items or content missing.



When an item cannot be indexed, an entry is entered into the database for the item and a file named 'IndexMissing.log' is created or updated in the physical folder for Enterprise Vault (EV) 32-bit index volume containing that item.  When the failed item is successfully indexed, the database is updated as well as the 'IndexMissing.log' file. When the last failed item has been fully indexed, the 'IndexMissing.log' file is supposed to be deleted by the repair processing.

When a Compliance Accelerator (CA) or Discovery Accelerator (DA) search is run against an index volume that has items that failed to be indexed, or has the 'IndexMissing.log' file present, the Info column for the index volume in the search will contain the message "Items or content missing", or "Some items could not be searched".  These messages are not errors, but informational notices that the index volume could have contained additional items to match the search criteria, but the search  could not confirm that due to the failed item(s).  The search would have returned all hits that match the search criteria in the index volume, if any exist.

These informational notices prevent the automatic acceptence of the search results into the review set of the CA Department or DA Case, but the search can be accepted manually.



These informational notices can be ignored once the failed to index item has been investigated and determined to not be related to the search criteria.  If the investigation into these notices uncovers that there is no failed to index item left in the Index Volume, the following actions can be executed to prevent these notices to occur again.
Rename the 'IndexMissing.log' file in the physical folder for the index volume that is referencing this error.
Note: This should only be done after an index repair has been successfully completed or the failed to index archived item(s) is/are no longer available from the Vault Store location.
1. From Discovery Accelerator's Case Administration, click on the case.
2. Under Options, select "Searches".
3. Select the search that reported this error.
4. On the upper right corner, click on "Search Details +".
5. Identify and note the Archive(s) that corresponding to the error reported.
6. Open Vault Administration Console and go to Archives.
7. Click on the appropriate archive such as Exchange Journal or Exchange Mailbox to populate journal archive(s) or Exchange archive(s), respectively.
8. Right click on the archive in question and select Properties.
9. Go to Advanced tab.
10. Under "Archive ID", note the ArchiveID.
11. Identify the Indexes location (End of document: How to Identify Index Location).
12. Using Windows Explorer, go to the Index Location found above and search the "Archive ID" found previously.
13. In this folder, search for the IndexMissing.log.
14. Examine its content for the SaveSetID's.
15. Confirm that the SaveSetID's is/are not in the Vault Store location.
Note: Vault Store location can be identified by going to the properties of the Vault Store's partition in the Vault Administration Console.
16. Rename the IndexMissing.log.
17. Restart Enterprise Vault Accelerator Manager service.
Now Discovery Accelerator search should run successfully.
How to identify index location:
This can be done from Enterprise Vault Administration Console->Enterprise Vault->Directory on [EV_Server]->Evsite->Enterprise Vault Servers->[EV_Server]->Services->Enterprise Vault Indexing Service->Index Locations.
NOTE:  In EV 10 and above, check the ItemAdditionStatusLog table in the Vault Store Database to determine the reason the items failed in the index, since the IndexMissing.log file does not exist.


Legacy ID


Article URL http://www.symantec.com/docs/TECH127715

Terms of use for this information are found in Legal Notices