In dtrace log, get error:
467109 18:28:36.305 [4872] (EVIndexAdminService) <11716> EV-L {VelocityIndexingEngineErrors.EnumErrors} Skipping report as an identical report has been processed recently. ID=SERVICE_RECEIVE_TIMEOUT, Message=After executing [C:\Program Files (x86)\Enterprise Vault\EVIndexing\bin\indexer-service], the child process connected to its parent, but then failed to negotiate the startup. The parent subsequently timed out. Last system error: [The operation completed successfully.|].
467110 18:28:36.305 [4872] (EVIndexAdminService) <11716> EV-H {VelocityIndexingEngineErrors.EnumErrors} Indexing engine error - 11/3/2020 6:26:21 PM, COLLECTION_SERVICE_SERVICE_TERMINATED, ERROR, ERRORS_HIGH, The [live] [crawler] for collection [11D67A618DE378E40BD10A051BB48B2AD_5] terminated unexpectedly: [Attempting to start the indexer service failed more than 5 times. [Tue Nov 03 18:26:20 2020|]].
and in system-reporting log:
X63nIgAARCMw||Could not start the [live] [indexer] ([C:\Program Files (x86)\Enterprise Vault\EVIndexing\bin\indexer-service]) in [E:\EV_INDEX1\index1\106452A9E59BB2A4ABE7A5FB81133D5D4_14\live] for collection [106452A9E59BB2A4ABE7A5FB81133D5D4_14]:
X63nIgAARSMw||The [live] [crawler] for collection [106452A9E59BB2A4ABE7A5FB81133D5D4_14] terminated unexpectedly: [Unknown reason].
Cause
Sometimes Indexing engine fails to start within the default timeout value due to an unknown reason which causes the issue. The indexing engine works fine with a higher timeout value.
Solution
Increase the indexing engine startup timeout by the follow steps:
1.Create the following registry key on the EV index server:
Key: "VseIndexOptionStartupTimeout"
Location: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KVS\Enterprise Vault\Indexing]
Type: dword
Value: 30-1800 [In Seconds]
2.Change the registry VseIndexOptionStartupTimeout value to 300
3.Set IVSyncNeeded = 1 in [IndexingServiceEntry] table in [EnterpriseVaultDirectory] database for all entries in IndexingServiceEntry table
4.Restart the indexing service
If need to update the startup-timeout value again for collections, please change the registry VseIndexOptionStartupTimeout value and repeat step 3 to 4.
Note:This registry settings only take effect from EV14.1.1 or EV14.2 version.
