We recently migrated an EV 11.0.1 CHF5 installation from 2008 R2 to Windows server 2012 R2. The process was successfull and every service started. Prior to updating to EV 12.1 we wanted to make sure that everything is still working and so we tested the search, archiving and retrieval - Which was fine. Only the indexing of new items seemed to not work even though the indexing service started. The application eventlog gave us a hint with application error id 1000 on start (velocity-startup.exe) and stop (velocity-shutdown.exe) of the indexing service:
Faulting application name: velocity-startup.exe, version: 8.1.1006.1002, time stamp: 0x4917df95
Faulting module name: MSVCR71.dll, version: 6.3.9600.18696, time stamp: 0x5915ecd6
Exception code: 0xc0000135
Fault offset: 0x0009d4c2
Faulting process id: 0x2734
Faulting application start time: 0x01d2f6778e0559f0
Faulting application path: C:\Program Files (x86)\Enterprise Vault\EVIndexing\bin\velocity-startup.exe
Faulting module path: MSVCR71.dll
Report Id: d04ef21b-626a-11e7-80d9-005056a54517
Faulting package full name:
Faulting package-relative application ID:
Dtrace did not give us more details and the system reporting sqlite database only stated: The [live] [indexer] for collection [1551A4BE2A54C2A49A4A9DA89575E85B3_991] terminated unexpectedly: [Unknown reason].
Tried to rename repository.xml and reinstalled the indexing engine without success. Error persisted and no new items got indexed. We then tried to execute the query Velocity-Startup -y mentioned in https://www.veritas.com/support/en_US/article.000115831 which gave us the statement that it could not be started because MSVCR71.dll is missing on the system! Well why is this one missing on a freshly installed Windows server 2012 R2? verified the locations that are named in combination with that dll file (C:\Windows\system32) and did not find it - We did not find it on a working EV server 2012 R2 in that location but under C:\Windows\SysWOW64. Copied this to the problematic system into the same location and restarted the Indexing service - Which is now starting without an error. Velocity-Startup -y now states: Velocity is ready. A few minues late the items in question were indexed successfully.
Missing MSVCR71.dll under C:\Windows\SysWOW64 prevent the indexing service from starting correctly. Copying the file from a working system to that location solved it.
Maybe this helps someone in the future!