Overview

You may experience with an error during the Journal archive from Enterprise Vault extraction.

2019-03-12 10:27:32Z|10032| 51|TRACE|                             ProcessAsMemoryStream|>> Started FetchItem. ArchiveId: [1DECFAD0630A64143A1A4AEB5C7BE1EC01110000EV11, ItemId: [d0ef3c65-4e9f-89a4-b1b8-21555259e041]
2019-03-12 10:27:32Z|10032|177|TRACE|                             ProcessAsMemoryStream|<< Finished FetchItem. ArchiveId: [1DECFAD0630A64143A1A4AEB5C7BE1EC01110000EV11, ItemId: [103cc1c8-311e-34c0-1b19-21554cf4b711] [64 ms]
2019-03-12 10:27:32Z|10032|177|TRACE|                             ProcessAsMemoryStream|<< Finished Getting Item as MemoryStream. ArchiveId: [1DECFAD0630A64143A1A4AEB5C7BE1EC01110000EV11, ItemId: [103cc1c8-311e-34c0-1b19-21554cf4b711] [66 ms]
2019-03-12 10:27:32Z|10032|177|ERROR|                                           Process|Export with Memory EV Export Storage setting fails.  Void FetchItem(KVS.EnterpriseVault.Interop.IItem)
More than one section list is not expected. Aborting.
   at ArchiveShuttle.Module.EVExportModule.ItemContentRetrievers.JournalNativeContentRetriever.FetchItem(IItem item)
   at ArchiveShuttle.Module.EVExportModule.ItemContentRetrievers.ContentRetrieverBase.ProcessAsMemoryStream(StagingArea stagingArea, EVExportResult item, EVArchive archive, ContainerTypeEnum targetMigrationType)
   at ArchiveShuttle.Module.EVExportModule.ItemContentRetrievers.ContentRetrieverBase.Process(EVArchive archive, Int32 commandId, Int32 mappingId, EVExportResult item, ExportArchive command)
   at ArchiveShuttle.Module.EVExportModule.ArchiveExport.<>c__DisplayClass17_2.b__0()
2019-03-12 10:27:32Z|10032|177| WARN|                                           Process|EV Export Storage configuration is set to: Memory. You can try to set it to: MemoryFallbackWithFileSystem and reprocess.
2019-03-12 10:27:32Z|10032|177|TRACE|                                               Get|Going to use JournalReconstructionContentRetriever for JournalArchive.
2019-03-12 10:27:32Z|10032|177|TRACE|                             ProcessAsMemoryStream|>> Started Getting Item as MemoryStream. ArchiveId: [1DECFAD0630A64143A1A4AEB5C7BE1EC01110000EV11, ItemId: [103cc1c8-311e-34c0-1b19-21554cf4b711]
2019-03-12 10:27:32Z|10032|177|TRACE|                        FetchCMAPIInstancefromPool|>> Started Fetch MAPI instance. ArchiveId: [1DECFAD0630A64143A1A4AEB5C7BE1EC01110000EV11, ItemId: [103cc1c8-311e-34c0-1b19-21554cf4b711]
2019-03-12 10:27:32Z|10032|177|TRACE|                        FetchCMAPIInstancefromPool|<< Finished Fetch MAPI instance. ArchiveId: [1DECFAD0630A64143A1A4AEB5C7BE1EC01110000EV11, ItemId: [103cc1c8-311e-34c0-1b19-21554cf4b711] [1 ms]
2019-03-12 10:27:32Z|10032|177|TRACE|                             ProcessAsMemoryStream|>> Started FetchItem. ArchiveId: [1DECFAD0630A64143A1A4AEB5C7BE1EC01110000EV11, ItemId: [103cc1c8-311e-34c0-1b19-21554cf4b711]

As you can see in logs Archive Shuttle tries first to get the message by JournalNativeContentRetriever which means that the module will get reconstructed message from EV server directly. When it fails on exception “More than one section list is not expected. Aborting.” then Archive Shuttle will use JournalReconstructionContentRetriever to try to reconstruct p1 header by the module itself which means that it will work and the message is exported successfully using JournalReconstructionContentRetriever method developed by Quadrotech.

Print Friendly, PDF & Email