Error Message

The following two errors in the Enterprise Vault (EV) Event Viewer log will occur during an archive run of the affected SharePoint sites: 

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault 
Event ID:      13360
Task Category: Directory Service
Level:         Error
Computer:      EV01.ev.local
Description:
An error was detected while accessing the Vault Database 'EnterpriseVaultDirectory' (Internal reference: {CADODataAccess::ExecuteSQLCommand} [d:\builds\14_\ev\v-prod-s\sources\source\common\adointerface\adodataaccess.cpp, lines {1326,1328,1347,1365}, built Mar 16 12:23:30 2021]): 

Description:  

An attempt was made to create an ArchiveFolder entry with a duplicate CustomId and CustomQual
 
SQL Command: 
 CreateArchiveFolder
 
Additional Microsoft supplied information:
 
Source:       Microsoft OLE DB Driver for SQL Server 
Number:       0x80040e14 
SQL State:    42000 
Native Error: 00050000 
HRESULT        0x80040e14

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault 
Event ID:      6469
Task Category: SharePoint Task
Level:         Error
Computer:      EV01.ev.local
Description:
An exception has occurred.
 [Internal reference CArchiveAssister/CF/ce]
[
Details:
ContainerArchiveVEID: 1B59B9EABB35B34409D468573E7D49B001110000evserver01
ParentFolderVEID: null
FolderName: TestFolder
FolderPath: http://sp01.ev.local/years/2013
] 
 

V-437-13360
V-437-6469

Each SP site has a set of metadata identifiers that uniquely identify each folder.  EV stores these values in the EnterpriseVaultDirectory database within the ArchiveFolder table in two fields named CustomId/CustomQual.  If an attempt is made during archiving to add a new folder with the same CustomId/CustomQual the error will be returned.   

There are multiple causes of why the same SP site would try to be archived in EV with a same CustomId/CustomQual:

1. The SP target is removed and re-created.
2. The SP site collection/site/document library being archived from two different servers, such as a test and production SP server. 
3. The SP site path is renamed.
4. The SP site is migrated to a new server keeping the same metadata values.

If one of the causes above can be reversed on the SP server then that will fix the issue as the data will match what EV has in the database.  However, if that is not possible then SQL manipulation maybe required.  Open a case with Support to resolve the issue.  

Please refer to the Related articles section for information on migrating SP sites when using EV.