The Upgrade of 32bit Indexes to 64 bit Indexes Causes EVIndexVolumesProcessor.exe to Crash

Article:TECH182219  |  Created: 2012-02-24  |  Updated: 2012-04-05  |  Article URL http://www.symantec.com/docs/TECH182219
Article Type
Technical Solution


Issue



EVIndexVolumesProcessor.exe may crash repeatedly when attempting to upgrade 32 bit (pre-EV10) indexes to 64 bit EV10 indexes.


Error



Type :        Warning
Date :        2/16/2012
Time :        10:22:23 AM
Event :        40967
Source :        Enterprise Vault
Category :    Index Move Task
User :        N/A
Computer :    evserver1.testdomain.local
Description:
EV Index Volumes Processor - Restarting failed process.

The process has failed abnormally and will be restarted automatically.


Type :        Error
Date :        2/16/2012
Time :        10:26:36 AM
Event :        1000
Source :        Application Error
Category :    Application Crashing Events
User :        N/A
Computer :    evserver1.testdomain.local
Description:
Faulting application name: EVIndexVolumesProcessor.exe, version: 10.0.0.1316, time stamp: 0x4e1374cc
Faulting module name: mscorwks.dll, version: 2.0.50727.4963, time stamp: 0x4e15067f
Exception code: 0xc00000fd
Fault offset: 0x00000000002c746a
Faulting process id: 0x(null)
Faulting application start time: 0x(null)
Faulting application path: (null)
Faulting module path: (null)
Report Id: (null)

 


Cause



In some instances a large number of deleted items within the affected archive, which are awaiting the expiry of the deleted item retention setting period before being permanently deleted, may cause EVIndexVolumesProcessor.exe to crash repeatedly when this process is called to perform an upgrade of a pre-EV10 index to an EV10 index.


Solution



This issue has been addressed in the following release:

 

Enterprise Vault 10.0.1

http://www.symantec.com/docs/TECH147787


Supplemental Materials

SourceETrack
Value2694347
Description

EVIndexVolumesProcessor.exe crashes multiple times when attempting the upgrade of 32 bit indexes to 64 bit



Article URL http://www.symantec.com/docs/TECH182219


Terms of use for this information are found in Legal Notices