Troubleshooting index volume error codes

Error code

Error description

Possible Cause

Suggestions

0

General error

Unexpected errors

Check that the index volume exists on disk in the correct location and that it is accessible (i.e. no network connectivity issues).

Try using Verify to check the general health of the index.
Instead of rebuilding the volume, consider restoring from backup then using Verify and Synchronize.

1

The index volume folder cannot be found

Connectivity issues.

Index files accidentally deleted from disk

Check that the index volume exists on disk in the correct location and that it is accessible (i.e. no network connectivity issues).
Instead of rebuilding the volume, consider restoring from backup and using Synchronize

2

There are too many consecutive items that have failed

Indexing service cannot access Storage service.

Storage service cannot access archived data.

Check the Windows event log on the computer running the Storage service, which may be remote from the server running Indexing. Check connectivity between Indexing and Storage if environment is distributed.
Also check availability of the vault store database and the vault store partition. Ensure both are online and responsive.

3

There is a sequence number mismatch between the index and storage

Vault store database restored from backup but EVSVR has not been run.

This may indicate a DR operation not completing successfully. Consider running EVSVR

4

The index volume has been partially deleted

An error occurred whilst deleting index files from disk.

An error occurred while deleting an index volume from disk. Enterprise Vault should automatically retry deletion later. In the meantime, check connectivity between the Indexing server and the volume’s index location.

5

The dataset file is missing (32-bit only)

Index files accidentally deleted from disk

Connectivity issues

Check the index volume’s updates.log and avtrace.log files. Instead of rebuilding the index volume, consider restoring from backup then using Verify and Synchronize

6

The dataset file is empty (32-bit only)

Index files accidentally deleted from disk

Connectivity issues

Check the index volume’s updates.log and avtrace.log files. Instead of rebuilding the index volume, consider restoring from backup then using Verify and Synchronize

7

The dataset file is invalid (32-bit only)

Index files accidentally deleted from disk

Connectivity issues

Check the index volume’s updates.log and avtrace.log files. Instead of rebuilding the index volume, consider restoring from backup then using Verify and Synchronize

8

Unable to open the index

Intermittent connectivity issues.

Index file corruption

Check connectivity between the Indexing server and index locations. Once the connectivity issue has been resolved, use Synchronize.
If the index files are on disk but are corrupted, then consider using Rebuild. If the environment is under load and a Rebuild is necessary, consider rebuilding just the volumes affected by corruption. Note that when a 32-bit index volume is rebuilt, the data will be ingested into a 64-bit volume. Upon successful completion of the rebuild, the 32-bit volume will be deleted

9

The checksum file is invalid (32-bit only)

Index files corrupted

If the contents of the index are known to be valid, consider deleting the checksum file then using Synchronize.

10

An error occurred while saving indexing data to disk (32-bit only)

Connectivity issues.

Index files corrupted

Check connectivity between the Indexing server and physical index locations.

Check the index volume’s updates.log and avtrace.log files.

If the error persists, consider rebuilding the index volume

11

An error occurred while saving dynamic attribute indexing data to disk (32-bit only)

Connectivity issues.

Index files corrupted

Check connectivity between the Indexing server and physical index locations.

Check the index volume’s updates.log and avtrace.log files.

If the error persists, consider rebuilding the index volume

12

The index compaction has failed (32-bit only)

 

Check connectivity between the Indexing server and physical index locations.

Check the index volume’s updates.log and avtrace.log files.

If the error persists, consider rebuilding the index volume

13

There has been an indexing engine error

System is overloaded.

Connectivity issues

Check the Windows event log on the Indexing server for possible clues. If the error is repeated for different volumes, check connectivity between the Indexing service and index locations.

Check if the system is running low on memory.

Use Verify and Synchronize to attempt to bring the volume back to life.

14

Failed to audit items

Cannot access Database server

Check the database server that hosts the vault store database(s). Fix any problems there, then run Verify and Synchronize.

15

There are duplicate items in the index

Data corruption

Run Verify. If the problem persists, consider rebuilding the volume.

16

The state file is missing from the index

Index files accidentally deleted from disk

If a backup of the index exists, consider restoring it and running Synchronize. Note that if the state file is missing in the backup too, Synchronize will trigger the re-indexing of all the items already in the volume

17

There was error accessing or updating the index engine metadata

Connectivity issues.

Directory service errors

Check the index metadata location and ensure it is accessible. Restart the Indexing service. Check connectivity between the Indexing service and the Directory service. Check access to database server hosting the Directory database.

18

There are items with incorrect information in the index

Data corruption

Run Verify and Synchronize. If the problem persists, consider rebuilding the index volume.