Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

Event 13360,6796,6842 related to collections

Created: 19 Jun 2014 • Updated: 22 Jun 2014 | 4 comments
GertjanA's picture
This issue has been solved. See solution.

Hello all,

EV10SP4CHF2. One one site I manage I have the below events when SFW kicks off with event 6854 - Partitions Collector run has started.. This is followed immediately by the following 3 alerts:

First Event - 13360 - An error was detected while accessing the Vault Database 'EVAMRNAVaultStore1' (Internal reference: {CADODataAccess::ExecuteSQLCommand} [.\ADODataAccess.cpp, lines {1317,1319,1335,1358}, built Jul 10 17:51:36 2013]):

Description:

[Microsoft][ODBC SQL Server Driver][SQL Server]The query processor could not start the necessary thread resources for parallel query execution.
 
 
SQL Command:
 EVManageCollections

Seconf Event - 6796 - A COM exception has been raised.
<0x80040e14>
Internal reference
{CVaultStoreDB::EnumSparseCollections} [.\VaultStoreDB.cpp, lines {5138,5148,5151,5152,5153,5154,5155,5156,5157,5160}, built Jan  7 10:48:36 2014]
 
An exception is raised when a process encounters an unexpected fault.

Third Event - 6842 - A Collector encountered an error.

Reason: <0x80040e14>
PartitionEntryID: 1772058216651B344A1F905A90D8833091q10000AMRNAMAILARCHIVE
Method: CCollector::DeleteEmptyCollections

 

Whilst looking at the eventlog, it looks like event 6842 shows the affected partitions. Could this be indicating a corruption on the partition? In database?

Anyone has an idea what to check further?

Thanks.

Gertjan

Operating Systems:

Comments 4 CommentsJump to latest comment

AndrewB's picture

i wonder if something is going on with the sql server. do you have a dba that can help troubleshoot from that end? maybe parallelism on the sql server?

Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com

GertjanA's picture

Hello Andrew,

My thought also. I asked DBA's to investigate. what I did notice is that the time the event occurred is the same time when a backup of the databases is being made. I'm checking to see if that can be adjusted.

Thank you, Gertjan, MCSE, MCITP,MCTS, SCS, STS
Company: www.t2.nl

www.quadrotech-it.com

www.symantec.com/vision

AndrewB's picture

sounds like that might be your issue.

remember, first rule of EV club, dont overlap schedules. ie: backup, collections, archiving, expiry, etc.

p.s. if you're backing up databases and EV isnt in backup mode... well, you know.

Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com

SOLUTION
GertjanA's picture

Changing the collection process to be run from 1600 to 1800 has removed the error.

Thank you, Gertjan, MCSE, MCITP,MCTS, SCS, STS
Company: www.t2.nl

www.quadrotech-it.com

www.symantec.com/vision