Error Message

Note: The error descriptions may vary, depending on the circumstances as to why the item(s) failed. Below are some examples.

The following errors may be seen in the Enterprise Vault Event Log on the DA server:

Source:        Accelerator Service Processor
Event ID:      234
Task Category: None
Level:         Error
Keywords:      Classic
Description:
APP AT - Customer ID: 1 - !!An error occurs during cleaning the PST object
 

Source:        Accelerator Service Processor
Event ID:      236
Task Category: None
Level:         Error
Keywords:      Classic
Description:
APP AT - Customer ID: 1 - [ExportPST] - Error moving some messages to PST for run 'Export to log Dtrace on missing item (5)' : 0
 

Source:        Accelerator Service Processor
Event ID:      236
Task Category: None
Level:         Error
Keywords:      Classic
Description:
APP AT - Customer ID: 1 - [ExportPST] - Error moving some messages to PST for run 'Export to log Dtrace on missing item (5)' : System.NullReferenceException: Object reference not set to an instance of an object.
   at KVS.Accelerator.Production.ProductionQueue.ProductionRunQueue.HooverUpMsgsToPst(Boolean bLastItem, ConcurrentQueue`1 filesMovesToPST)
   at KVS.Accelerator.Production.ProductionQueue.ProductionRunQueue.StartPSTExport(Boolean isLastItem)

Source:        Accelerator Service Processor
Event ID:      236
Task Category: None
Level:         Error
Keywords:      Classic
Description:
APP AT - Customer ID: 1 - [ExportPST] - Error moving some messages to PST for run 'Export to log Dtrace on missing item (5)' : System.Runtime.InteropServices.InvalidComObjectException: COM object that has been separated from its underlying RCW cannot be used.
   at KVS.Accelerator.Production.ProductionQueue.ProductionRunQueue.ClosePST()
   at KVS.Accelerator.Production.ProductionQueue.ProductionRunQueue.HooverUpMsgsToPst(Boolean bLastItem, ConcurrentQueue`1 filesMovesToPST)
   at KVS.Accelerator.Production.ProductionQueue.ProductionRunQueue.StartPSTExport(Boolean isLastItem)


The following errors may be seen in the Enterprise Vault Event Log on the EV Storage Service server(s):

Source:        Enterprise Vault
Event ID:      6882
Task Category: Storage Online
Level:         Error
Keywords:      Classic
Description:
Unable to complete retrieval request
 
Reason:              The system cannot find the file specified.  (0x80070002)
Vault:              JournalArchive
Vault Id:           1DE5EA73FEBC737458C7F38AFD7D8706B1110000evserver1.EV.LOCAL
Item Id:            201510215450081~201510191648470000~Z~B152C2D9F71DC90BA42B0D1D2CCF3961
Reference:          Vault/RI
Extended Item Info: 1DE5EA73FEBC737458C7F38AFD7D8706B1110000evserver1.EV.LOCAL+201510215450081~201510191648470000~Z~B152C2D9F71DC90BA42B0D1D2CCF3961+0++0+1+42298.74583333333400000+21+469++1+1+469+1+0+0+681
Supplementary Info:

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-6882
 

Source:        Enterprise Vault
Event ID:      6882
Task Category: Storage Online
Level:         Error
Keywords:      Classic
Description:
Unable to complete retrieval request
Reason:   Operation did not complete successfully because the file contains a virus or potentially unwanted software.  (0x800700e1)
Vault:    Inbox
Vault Id: 158E8DE107864DC4B8258D4646A5A82F11110000evlab
Item Id:  201907254049773~201907251013390000~Z~6131194262EF1BE7C45D06F10C7B4821
Reference:   Vault/RI
Extended Item Info: 158E8DE107864DC4B8258D4646A5A82F11110000evsmtp-01+201907254049773~201907251013390000~Z~6131194262EF1BE7C45D06F10C7B4821+0++0+27+43671.42777777777500000+3452+592792++30+17+6712870+1+0+0+681?1+24+706828517+0+6130B4BF4957686059FEB7C571CFB161+0+6+43671.42777777777500000+1+0+++0+0+0+0+1?1+187+2010763217+0+6130B4BF4957686059FEB7C571CFB161+0+6+43671.42777777777500000+2+0+++0+0+0+0+1
Supplementary Info:
2020-02-13T08:06:16-00:00 ID: 7116
Failed to access file '\\EVLab\EVPartition01d3a21add9a1b30$\2019\07-25\6\130\6130B4BF4957686059FEB7C571CFB161~BB~77D9CFD1~00~1.DVSSP'.      Reason: Operation did not complete successfully because the file contains a virus or potentially unwanted software.  (0x800700e1)   Operation: READ   Reference: CNTFSStorageDeviceReader::LoadFile     

The following error may be seen in an EVSVR DumpSaveset Log:

Getting recombined Saveset (DVS) file
ERROR: Failed to get recombined saveset. Error: Unspecified error  (0x80004005)
Event Output: Unable to complete retrieval request     
Reason:   Operation did not complete successfully because the file contains a virus or potentially unwanted software.  (0x800700e1)   Vault:              JournalArchive 24062019 
  Vault Id:  1A6D39081177C964E9C83B05548D460BA1110000evlab
  Item Id:  201907254049773~201907251013390000~Z~6131194262EF1BE7C45D06F10C7B4821
  Reference:  Vault/RI 
  Extended Item Info:  
  Supplementary Info:   2020-02-19T06:31:37-00:00
  ID: 7116 Failed to access file '\\EVLAB\EVPartition01d3a21add9a1b30$\2019\07-25\6\130\6130B4BF4957686059FEB7C571CFB161~BB~77D9CFD1~00~1.DVSSP'.  
  Reason: Operation did not complete successfully because the file contains a virus or potentially unwanted software.  (0x800700e1) 
  Operation: READ  
  Reference: CNTFSStorageDeviceReader::LoadFile      (0xc0041ae2)
         2020-02-19 06:31:37 
  ERROR: GetRecombinedSaveset failed. Error: Unspecified error  (0x80004005)

UMI Codes:

V-437- 234

V-437- 236

V-437- 6882

When an item to be exported by Discovery Accelerator cannot be retrieved from storage, the export processing marks it as failed and proceeds to the next item.  This failure sets the status of the export to Error which prevents the export reports from being created.

Below Steps can be followed to workaround this issue:

1. Note the DiscoveredItemID value for each item marked as failed in the export.

2. In the Review tab, mark all items to be exported with a common Mark, such as Reviewed.

3. For each of the failed items, used their DiscoveredItemID to preview each one and apply a different Mark, such as Unreviewed.

4. Create a new Export using the Mark placed upon all items.  Those items that failed and were marked with a different Mark will not attempt to be exported.

This issue has been resolved in the following release:

Enterprise Vault 12.5.2

https://www.veritas.com/support/en_US/downloads/update.UPD334575