Index failed, rebuilding failed
if you have any other event log enteries would be helpful and also do a DTrace of the indexbroker service and the storagebroker service in verbose mode when you attempt the repair and attach the output file so we can see the result
There is a way to set a poison pill setting in the registry to bypass the default number of failures to allow your index to rebuild but you will be missing items in the index after it completes
Here is how to make the setting
HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\Indexing\PoisonPillCount
DWORD
Default: 1
This will set the number of attempts to process an item before it is deemed to be a poison pill. The action taken depends upon what's being processed...
e.g.
After PoisonPillCount consecutive failed attempts to open an index volume it is deemed to be corrupt and is marked as 'failed'
After PoisonPillCount failed attempts to add an item to the index the addition is abandoned and the index update steps onto the next item.If you do not have the following then please create it, if you do then change the value to '100000' :-
HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\Indexing\MaxConsecutivePoisonPillItems
DWORD
Default: 100
The maximum number of consecutive poison pill items before an index update is deemed to be a poison pill and abandoned. The index update will be restarted on indexing service restart or the hourly check for pending updates.Remember please backup your registry before making any changes and this setting is to be removed after you rebuild the indexa
