Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Error 13360 and 6796

Created: 10 Oct 2012 • Updated: 15 Oct 2012 | 7 comments
Rob dos Ramos's picture
This issue has been solved. See solution.

Hi All,

 

Have another situation. Have a clinet who is receiving loads of 13360 and 6796 errors (non stop)

 

 

Event Type: Error
Event Source: Enterprise Vault 
Event Category: Storage Online 
Event ID: 6796
Date: 10/10/2012
Time: 13:50:54
User: N/A
Computer: ServerX
Description:
A COM exception has been raised. 
<0x80040e21> 
Internal reference 
{{CVaultStoreDB::GetFoldersWithUserDeletedItemsForArchive:#16078} } [.\VaultStoreDB.cpp, lines {16078,16087,16089,16090}, built Aug  9 10:01:17 2012] 
 
An exception is raised when a process encounters an unexpected fault. 
 
 
Event Type: Error
Event Source: Enterprise Vault 
Event Category: Storage Online 
Event ID: 13360
Date: 10/10/2012
Time: 13:50:54
User: N/A
Computer: ServerX
Description:
An error was detected while accessing the Vault Database 'EVMailboxVaultStore' (Internal reference: {CADODataAccess::ExecuteSQLCommand} [.\ADODataAccess.cpp, lines (13){...,1409,1424,1472,1473,1476,1480,1481,1485,1489,1491,1492,1494}, built Nov 11 21:02:49 2011]): 
 
Description:  
 
Could not find stored procedure 'GetFoldersWithUserDeletedItemsForArchive'.
 
 
SQL Command: 
 GetFoldersWithUserDeletedItemsForArchive
 
 
Additional Microsoft supplied information:
 
Source:       Microsoft OLE DB Provider for SQL Server 
Number:       0x00040eda 
SQL State:    42000 
Native Error: 00002812 
HRESULT 0x80040e21
 
Been looking on the Net but non of the 13360 error have the same issues. 
 
Any advise would be great.
 
Rob

Comments 7 CommentsJump to latest comment

Jeff Shotton's picture

I think the first thing to try is validate if dbo.GetFoldersWithUserDeletedItemsForArchive actually exists (in any vault store).

Rob, I cant find this in either the install scripts, EV9 or EV10. This makes me think it was something brought in with a patch to correct a specific issue. And maybe you are running the binaries, but the SQL was not applied.

Which version are you running, which service pack, and what hotfixes have been installed.

If you aren't sure, just post the EVfileversions.txt file from a deployment scanner output.

Regards,

Jeff

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here

Jeff Shotton's picture

I figured it out.

You have EV9 sp3 and you applied the following hotfix: http://www.symantec.com/docs/TECH196642

However, the SQL script in that patch has not been run against the vault store database.

Regards,

Jeff

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here

SOLUTION
Rob dos Ramos's picture

I will try it out

Regards,

Rob

 

Rob dos Ramos's picture

Hi Jeff,

 

Ran the script against one of the databases and got the following error

 

Msg 207, Level 16, State 1, Procedure GetFoldersWithUserDeletedItemsForArchive, Line 14 Invalid column name 'DeletionReason'.

Regards,

Rob

 

Jeff Shotton's picture

Hmm. Well, that column should exist in an EV9 sp3 vault store database, so i wonder if you are running a mashup of dlls from a couple of versions.

Can you post the full list of file versions by doing a dtrace of any process for a couple of seconds and then terminating it, and also run the following query:

use EnterpriseVaultDirectory

select DatabaseDSN, SchemaVersion from VaultStoreEntry

Your schema version should be 9.13.9.24

 

while you are at it, run

 

use EnterpriseVaultDirectory

select SchemaVersion from DirectoryEntry

your DirectoryDB schema should be 9.36.1.45

 

Regards,

Jeff

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here

Rob dos Ramos's picture

 

EVJournalVaultStore 9.13.9.24
EVMailboxVaultStore 9.13.9.24
Directory 9.36.1.45

Regards,

Rob

 

Jeff Shotton's picture

Then something looks wrong with the schema. I wont be able to correct this via the forums...unless it turns out that it is something that doesn't actually need correcting:

I was just thinking...is it possible you have some orphaned databases (i.e test restores from an older version). i.e the two databases above - are they the only ones you ran the script against, and which one failed?

 

For each vault store database, run the following

 

select * from journaldelete where 0=1

 

this will pipe out the column headers without actually touching the data. Post the list of columns back here.

Regards,

Jeff

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here