WORKAROUND
To identify the correct indexing GUID so that the incorrect indexes may be deleted, run the index_support_tool2.exe attached to this Knowledge Article:
- Extract the tool to the InTrust server.
- Stop all InTrust services on the server running index.
- Backup IndexingRoot$ folder of the problem repository (optional)
- Run the tool(attached) using the following command:
index_support_tool2.exe -d -r "rep_path" ("UNC path for repository")
The output will show the working index GUID (like this: index identifier - {9E8FE494-581C-4ACA-B5A4-8BE8FBCD7ED3} )
This is correct index, other indexes in this repository IndexingRoot$ folder should be deleted.
Repeat these steps for each impacted repository.
Once the tool output is available, check the ... IndexingRoot$\storages.2 and storages.3 folders. There should be not be any other GUIDs in them except for the one in the output. If there are any - delete them.
- After having identified and removed the incorrect indexes, restart the InTrust services.
STATUS
Waiting fix in a future release of InTrust.