cancel
Showing results for 
Search instead for 
Did you mean: 

The DELETE statement conflicted with the SAME TABLE REFERENCE constraint "FK_ArchiveFolder_ArchiveFolder". The conflict occurred in database "EnterpriseVaultDirectory", table "dbo.ArchiveFolder", column 'ParentFolderRootIdentity'.

WiVM
Level 3

Hi,

 

I get this error in the StorageDelete trace on eVault 9:

42554342 11:21:39.287  [7232] (StorageDelete) <7952> EV:M CBaseDirectoryServiceWrapper::CreateDirectoryService() - Entry [m_nNumTries = 40]
42554343 11:21:39.303  [7232] (StorageDelete) <7952> EV:L CBaseDirectoryServiceWrapper::CreateDirectoryService() - Successfully communicated with an EV Directory Service on the local machine
42554344 11:21:40.287  [5128] (DirectoryService) <7804> EV~E Event ID: 13360 An error was detected while accessing the Vault Database 'EnterpriseVaultDirectory' (Internal reference: .\ADODataAccess.cpp (CADODataAccess::ExecuteSQLCommand) [lines {1393,1395,1410,1428}] built Aug  6 19:31:21 2010): |Description:  |The DELETE statement conflicted with the SAME TABLE REFERENCE constraint "FK_ArchiveFolder_ArchiveFolder". The conflict occurred in database "EnterpriseVaultDirectory", table "dbo.ArchiveFolder", column 'ParentFolderRootIdentity'.| | |SQL Command: | DeleteArchiveFolders| | |Additional Microsoft supplied information:| |Source:       Microsoft OLE DB Provider for SQL Server |Number:       0x80040e2f |SQL State:    23000 |Native Error: 00000547 |HRESULT|0x80040e2f| |
42554345 11:21:40.287  [5128] (DirectoryService) <7804> EV~E Event ID: 13360 An error was detected while accessing the Vault Database 'EnterpriseVaultDirectory' (Internal reference: .\ADODataAccess.cpp (CADODataAccess::ExecuteSQLCommand) [lines {1393,1395,1410,1428}] built Aug  6 19:31:21 2010): |Description:  |The statement has been terminated.| | |SQL Command: | DeleteArchiveFolders| | |Additional Microsoft supplied information:| |Source:       Microsoft OLE DB Provider for SQL Server |Number:       0x80040e2f |SQL State:    01000 |Native Error: 00003621 |HRESULT|0x80040e2f| |
42554346 11:21:40.287  [5128] (DirectoryService) <7804> EV~E Event ID: 8453 The EnterpriseVault.DirectoryService object reported an error.| |The error code was 0x80040e2f |
42554349 11:21:40.303  [7232] (StorageDelete) <7952> EV~E Event ID: 6651 Storage Deletion Server has failed |Reason:  <0x80040e2f> |
42554350 11:21:40.303  [7232] (StorageDelete) <7952> EV:L EVCommon::EVThreading::CThreadPool::ServiceRequests Information: Executed one more request(cookie = [16]). Total active requests now left = [0]
42554351 11:21:40.303  [7232] (StorageDelete) <7952> EV:M EVCommon::EVThreading::CThreadPool::GetNextRequest (Entry)

I found another post on this forum which suggest to run this query to see that it returns any results: http://www.symantec.com/connect/forums/ev-901-events-8453-13360

It does return one entry, but what now?

Thank you

 

1 ACCEPTED SOLUTION

Accepted Solutions

Rob_Wilcox1
Level 6
Partner

I would suggest discussing it with SYMC, or take a look here:

https://www-secure.symantec.com/connect/forums/ev9sp2-13360-deletearchivefolders-issue

 

Working for cloudficient.com

View solution in original post

3 REPLIES 3

Rob_Wilcox1
Level 6
Partner

I would suggest discussing it with SYMC, or take a look here:

https://www-secure.symantec.com/connect/forums/ev9sp2-13360-deletearchivefolders-issue

 

Working for cloudficient.com

EV_Ajay
Level 6
Employee Accredited

The DeleteArchiveFolders Stored Procedure attempts to delete folders from the ArchiveFolder table in the EnterpriseVaultDirectory Database that cannot be deleted.  During the delete process, an attempt is made to delete a parent folder which is marked for deletion, but NOT all of its associated child folder(s) are also marked for deletion.   Deleting the parent folder will be prevented to avoid having orphan child folder(s).

This is controlled by the Foreign Key constraint FK_ArchiveFolder_ArchiveFolder

Reason : The issue is because the deleted folders are not cleared in ArchiveFolder.dbo.

 

 

EV_Ajay
Level 6
Employee Accredited

Hi,

I would recommend to open case with Symantec to work on this issue. To resolve this issue it is require some manual changes into the SQL database.