How to read the contents of the IndexMissing.log file
Article ID: 100002019
Updated On:
Resolution
Here is an example of an IndexMissing.log file:
The file consists of a header line and one or more data lines. The breakdown of the header line, using the example above is:
Archive ID: 187938EFF4AB230468C40C1130E4E0F1E1110000ev8alias
187938EFF4AB230468C40C1130E4E0F1E1110000ev8alias/Volume:3 695010,201004020246464~201001212344150000~Z~E129CCEDDEA7D66713C63676F395D731,-1 The file consists of a header line and one or more data lines. The breakdown of the header line, using the example above is:
Archive ID: 187938EFF4AB230468C40C1130E4E0F1E1110000ev8alias
Every index volume is associated with an archive via this Archive ID.
Index Volume: 3
Every archive has at least one index volume. Each index volume is identified by a volume number that is an EV internal reference.
The breakdown of the missing item entry fields, from the example above are as follows:
Index Sequence number: 695010
This number identifies the item within this specific index (not the index volume). These usually begin at 1 (for the index as a whole) and increment by 1 for each item indexed. For example, the second index volume might span items 576,231 - 899,073. In the example above, item 695,010 was not indexed, even though it is archived - so its contents can't be searched.
Saveset ID: 201004020246464~201001212344150000~Z~E129CCEDDEA7D66713C63676F395D731
This ID is used within EV to uniquely identify an item archived by Enterprise Vault. The Saveset ID is discussed elsewhere (see document TECH35581 in the Related Documents section below):
Index failure code: -1
This number is the code used to identify the cause of the index failure. There can be several failures for any given item. Each of these failures will be listed on one line with the codes listed separated by semicolons.
For more information about repairing an index volume when it has items missing, or to resolve issues where the IndexMissing.log file appears to be corrupted - see article 000007449.
Note: The use of the IndexMissing.log file can be disabled using the LogMissingItems registry key.
Please see Related Documents section below for more information on this registry setting.
Issue/Introduction
The IndexMissing.log file is a file that resides within an index volume folder when there is at least one archived item that has failed to be indexed. The Enterprise Vault (EV) Indexing service uses the IndexMissing.log to document the details of non-consecutive items missing from the index volume.
Was this article helpful?
Yes
No
Powered by
