Full-Text Search broken for newly created Objects

Question

Suddenly I cannot search for newly created Object, so I guess Indexing doesn't work anymore and I think there are two Indexes missing. 
 Rebuilding doesn't work.. 
 
 Advanced Vault Settings:

Indexes on Drive: 
 
 How could this happen and how can I fix it? 
 
 Thank you very much!

Timo Lahti · Answer

Hi there, 
 As a first option, please run Verify & Repair (thorough) for the whole document vault to see if the vault structure is intact, or if this is just an indexing issue. 
 if no files from the document vault are missing, then re-index the document vault. 
 If files are missing, please check your antivirus software if it has quarantined something. 
 Also it's a good practice to exclude document vault location, as well the software installation folder from the antivirus scans.

Wesley Weir · Answer

Whenever you rebuild the indexes ( Rebuilding the dtSearch Full-Text Search Index.pdf ) that recreates the indexes. M-Files keeps track of which files it has indexed and which it has not in the database, so if you just deleted the index files it would recreate the files but not know that it needs to go back and re-index the files it already did. 
 That's why we recommend you use the rebuild option in the Admin tool as that will delete the files, restart the index count, and recreate the files. 
 I would recommend you remove the new/extra indexers unless they are needed for anything specific, and just have the default indexers for now. 
 Check what processes are running in the background on the server. You should have multiple index processes running (MFIndexer.exe). Usually you should have at least two running but you might have more if you have more than one vault or external connections. 
 When you rebuild the indexer give it time to complete. It will run in the background and go back over all the objects in the vault and depending on resources and the number of objects this can complete in minute or days. 
 While it's running you still should be able to use advanced searches and views to find objects as those ignore the index. If you can't find the object(s) using those options then it's possible it's not an indexing issue. 
 When it's likely caught up if you still aren't getting all results in your searching then that is when you want to do the Verify and Repair (Thorough) option again. One reason that the indexer might not be getting everything is if it has hit an object(s) it can't index. This can cause the indexer to fail, retry, and fail again and to keep looping. Usually when that happens a verify and repair can help find which files are the cause as the V&R will, among other things, try to do similar checks as the indexer. If it finds files that are inaccessible or corrupted at the end it should give you a list of all the objects that were problematic. 
 Sometimes you can take that list and it's easy to identify the problem files. Other times it's not. If you can locate the problem object(s), delete/destroy them from the vault and see if that resolves the issue. 
 That's one of the reasons we highly recommend support in these cases. If the indexer is failing on objects it might take a deeper dive into the database to locate and remove the problem object(s) which is something that would likely require a call with someone from the support staff.

Full-Text Search broken for newly created Objects

Top Replies