Overview
In rare occasions, when the index gets corrupted, it might prevent the engine from starting. You can see from content_application.log that there is a problem in some file under the engines content (C:\Single9\IDOLServer\IDOL\content) folder.
In this case, it is likely that you have to use index backups or reindex. To get the engine running you have to remove the index content from the engine.
This document will describe how to remove index content from the engine.
NOTE: These instructions are for IDOL 10.9
Solution
1. Stop MFindexingManager service from M-Files server.
2. Stop malfunctioning IDOL engine service. Make sure that corresponding processes go down.
3. Remove everything else from the of Content folder (usually in C:\Single9\IDOLServer\IDOL\content) than:
- Folder: license
- Folder: uid
- Files: admin.dat, autn_ntres.dll, autnxslt.dll, content.exe, content.lck, licensekey.dat, portinfo.dat, admin.dat
4. Start the engine.
5. Check from application.log and content_application.log that engine starts properly.
6. Start MFindexingManager service from M-Files server.
In the cluster environment, it is a good idea to remove the content from all engines before restore/reindex. To ease up the job you can use following PowerShell script. Copy the below blue text to the power shell window and run it:
if (!([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] "Administrator")) { Start-Process powershell.exe "-NoProfile -ExecutionPolicy Bypass -File `"$PSCommandPath`"" -Verb RunAs; exit }
Remove-Item -path E:\Single9\IDOLServer\IDOL\content\* -recurse -exclude
license,uid,admin.dat,autn_ntres.dll,autnxslt.dll,content.exe,content.lck,licensekey.dat,portinfo.dat
