In the Application Event Log:
Source: Application Error
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords: Classic
Description:
Faulting application name: EVIndexVolumesProcessor.exe, version: 14.2.0.1226, time stamp: 0x61a7e95d
Faulting module name: clr.dll, version: 4.7.3946.0, time stamp: 0x6246bcb6
Exception code: 0xc00000fd
Fault offset: 0x000000000000bda4
Faulting process id: 0x3684
Faulting application start time: 0x01d8f825d46fa22f
Faulting application path: C:\Program Files (x86)\Enterprise Vault\EVIndexVolumesProcessor.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 5fbcac68-0e11-4482-82a6-cdd6bd300a94
Faulting package full name:
Faulting package-relative application ID:?
In the Veritas Enterprise Vault Event Log:
Source: Enterprise Vault
Event ID: 40967
Task Category: Index Admin Service
Level: Warning
Keywords: Classic
Description:
EV Index Volumes Processor - Restarting failed process.
The process has failed abnormally and will be restarted automatically.
For more information, see Help and Support Center at http://telemetry.community.veritas.com/entt?product=ev&language=english&version=12.5.0.0&build=12.5.0.1221&error=V-437-40967
In a Dtrace log of the IndexVolumesProcessor process:
48863 13:16:24.080 [6744] (EVIndexVolumesProcessor)
33843 13:16:23.048 [6744] (EVIndexVolumesProcessor)
When EVIndexVolumeProcessor encounters a message with a large number (90K+) of recipients, that process fails and is restarted by the EVIndexAdminService. Most times this will also crash. This error prevents indexing of any other message in the affected Enterprise Vault server. Any Affected index volumes will need to be set Offline in order to continue indexing other archives.