How to fix corrupted TRIM indexes?

Recently we started receiving following types of emails from the TRIM Event Processor.

TRIM Event Processor running on server reported the following message:
Error : Database: - User An error occurred updating Content Index for Record(xxxxxxx). The primary content index in folder C:\.. has a pending transaction file (C:\TRIMIndexFolder\TRIMpending.bin). This indicates that a previous call to update the index using these transactions has failed. All content indexing will cease for this database until the problem has been rectified.
This E-mail Message has been automatically generated by TRIM Context (server).

This became a very big issue because it was filling up our TRIM notification inbox. It wasn’t effecting day to day TRIM operations except for document content searches.

This is how we fixed it.

Solution 1 – Failed

These were the steps involved based on HP documentation:

1. Stop the TRIM Event Server service on your Event Server.
2. Locate the TRIMPending.bin file. This should be located in the Document Content Index folder, the location being administered by each site.
3. Rename the file ‘TRIMPending.bin’ to ‘TRIMtrans.bin’.
4. Start the Event Server service.

Solution 2 - Successful

We tried the above few times and every attempt failed. We were running out of time and finally we decided to delete the current index and recreate it. Worked like a magic. No more issues and no more automated email notifications.

These were the steps involved:

1. Stop all TRIM services (Low priority to high priority).
2. Go to Event Server and stop Document Content Indexing (DCI).
3. Remove the content index from the dataset.
4. Go to the DCI folder and delete the folder which is represented by the 2 character database identifier.
5. Go back to TRIM enterprise Manage and create the new index.
6. Reindex the newly created Content Index.
7. Check for the logs and fix any issues.
8. Go to properties of the Workgroup Server and update the Content Search Settings path.
9. Turn on Document Content Indexing(DCI) on the Event Server (Check the path).
10. Create a new DCI chain and mark the existing chain as read-only.
11. Start all TRIM Services (High priority to low priority).
12. Using Monitor Activity ensure Event Queue is back to normal.