Archive Shuttle 7.8 EV Export module may log error below during item extraction from Enterprise Vault journal archive if:
a\ Envelope reconstruction is done by AS. Archive Shuttle does the envelope reconstruction for EV journal archives coming from EV 10.0.3 and older.
b\ EV Export module system setting ‘EV Export Storage’ is set to ‘FileSystem’
2016-09-08 14:18:18Z|4956| 4|ERROR| Process|Error occured. ArchiveID: [1739C279888AEDA4DA0A5C64646025E7D1110000ev10-site] | ItemID: [51547e49-7ab7-7c2e-5a2c-a622787ee981] Void ProcessAsFile(ArchiveShuttle.Common.Resources.Staging.StagingArea, ArchiveShuttle.Common.Resources.EnterpriseVault.Results.EVExportResult, System.String) Processing as File is not allowed for ExportTypeEnum.JournalEnvelopeReconstruction at ArchiveShuttle.Module.EVExportModule.ItemContentRetrievers.ContentRetrieverBase.ProcessAsFile(StagingArea stagingArea, EVExportResult item, String fileName) at ArchiveShuttle.Module.EVExportModule.ItemContentRetrievers.ContentRetrieverBase.Process(EVArchive archive, Int32 commandId, Int32 mappingId, EVExportResult item, StagingArea stagingArea)
Archive Shuttle 7.8 and higher cannot export to file (‘EV Export Storage’ is set to ‘FileSystem’) from Enterprise Vault journal archive when you use Azure Storage (HOTS) or journal envelope reconstruction is done by AS. It is by design.
If you would like export to the file first the process is consuming resource and would look like below:
1. Export to file (write)
2. Load file to memory (read)
3. Reconstruct message in memory
4. Remove old file
5. Save reconstructed message from memory to file (write)
With memory first, it’s just:
1. Export to memory
2. Reconstruct message in memory
3. Save reconstructed message from memory to file (write)
Saving to file does not provide any benefits, it’s just more IO work for the module and is therefore not supported.
The solution is then to set EV Export module system setting ‘EV Export Storage’ to Memory or MemoryFallbackWithFileSystem.