The following error may be logged from time to time in the EV Import log file:

2014-04-16 12:45:10Z|ERROR|P:7788|T:25|ItemImport|Error ingesting item into EV
EXCEPTION: System.Runtime.InteropServices.COMException (0x80040308): Archive, Archive Folder, Archive Type, Vault Store or Retention Category does not exist
at KVS.EnterpriseVault.Interop.IItem.Insert()
at ArchiveShuttle.Module.EVImportModule.ItemImport.ImportItemImpl(EVImportItemContainer evImportItemContainer)

A DTRACE may show the following.

1036172 10:56:48.110 [4740] (StorageOnlineOpns) <23872> EV:H {CSimpleStore::LocateTargetVaultIdForCurrentFolder:#5886} _com_error exception: [Error reading ArchiveFolder Entry from Vault Directory %1 (0xc00418e7)]

After investigation with Veritas this was determined to be a bug in the Enterprise Vault API which is used for ingesting items into Enterprise Vault. The issue is that the API treats a folder name/path as an ID, which is then not found in the Directory Database, and causes an error.
There are two solutions to this issue:
1/ Identify the number of items affected, and the number of archives affected. If this is a relatively small number, then manually process that container in some way (for example it may be that just copying the files from the staging area is sufficient, or, that the source container should be exported to PST and ingested into the target from that PST)
2/ The solution for this issue is to upgrade the target environment to Enterprise Vault 11.0 Cumulative Hotfix 5, or later. Following the upgrade the errors will no longer be present, and the containers will migrate normally.

Print Friendly, PDF & Email