Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Upgrade enetrprise vault 10 sp1 to sp2

Created: 18 Oct 2012 • Updated: 05 May 2013 | 13 comments
Ronen Tzimbel's picture
This issue has been solved. See solution.

Hello,

after I upgrade enterprise vault  10 sp1 to sp2 , when the archiving task run we get a lot of errors:

and all of the queue from msmq automatically purge.

Event id:

 Log Name:      Symantec Enterprise Vault

Source:        Enterprise Vault

Date:          17/10/2012 16:32:11

Event ID:      8390

Task Category: Storage Online

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      xxxxx

Description:

The EnterpriseVault.DirectoryConnection object reported an error.

The specified archive folder already exists

Log Name:      Symantec Enterprise Vault

Source:        Enterprise Vault

Date:          17/10/2012 16:32:11

Event ID:      6469

Task Category: Storage Online

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      xxxxxx

Description:

An exception has occurred.

 [Internal reference CArchiveAssister/RF/ce]

Log Name:      Symantec Enterprise Vault

Source:        Enterprise Vault

Date:          17/10/2012 16:32:12

Event ID:      13360

Task Category: Directory Service

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      xxxxx

Description:

An error was detected while accessing the Vault Database 'EnterpriseVaultDirectory' (Internal reference: {CADODataAccess::ExecuteSQLCommand} [.\ADODataAccess.cpp, lines {1316,1318,1333,1351}, built Sep 12 21:03:54 2012]):

Description: 

An attempt was made to create a resource lock name with invalid values for ParentFolderVEID[1F063BF399B0AD24DB5E3BF207FE02C4A1110000vltsrv01] and ContainerArchiveVEID[Not Supplied]

SQL Command:

 CreateArchiveFolder

Additional Microsoft supplied information:

Source:       Microsoft OLE DB Provider for SQL Server

Number:       0x80040e14

SQL State:    42000

Native Error: 00050000

HRESULT                              0x80040e14

Log Name:      Symantec Enterprise Vault

Source:        Enterprise Vault

Date:          17/10/2012 16:32:12

Event ID:      8453

Task Category: Directory Service

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      xxxxx

Description:

The EnterpriseVault.DirectoryService object reported an error.

The error code was 0x80040e14

Log Name:      Symantec Enterprise Vault

Source:        Enterprise Vault

Date:          17/10/2012 16:32:12

Event ID:      8390

Task Category: Storage Online

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      xxxxxx

Description:

The EnterpriseVault.DirectoryConnection object reported an error.

0x80040e14

Internal references:

Error [0x80040e14]

{CDirectoryConnectionObject::CreateArchiveFolder} [.\DirectoryConnectionObject.cpp, lines {2874,2891,2893}, built Sep 12 21:03:57 2012]

Log Name:      Symantec Enterprise Vault

Source:        Enterprise Vault

Date:          17/10/2012 16:32:12

Event ID:      6469

Task Category: Storage Online

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      xxxxxx

Description:

An exception has occurred.

 [Internal reference CArchiveAssister/CF/ce] [

Details:

ContainerArchiveVEID: null

ParentFolderVEID: 1F063BF399B0AD24DB5E3BF207FE02C4A1110000vltsrv01

FolderName: Top of Information Store

FolderPath: 

]

Log Name:      Symantec Enterprise Vault

Source:        Enterprise Vault

Date:          17/10/2012 16:32:12

Event ID:      13360

Task Category: Directory Service

Level:         Error

Keywords:      Classic

User:          N/A

Computer:     xxxxx

Description:

An error was detected while accessing the Vault Database 'EnterpriseVaultDirectory' (Internal reference: {CADODataAccess::ExecuteSQLCommand} [.\ADODataAccess.cpp, lines {1316,1318,1333,1351}, built Sep 12 21:03:54 2012]):

Description: 

An attempt was made to create a resource lock name with invalid values for ParentFolderVEID[1F063BF399B0AD24DB5E3BF207FE02C4A1110000vltsrv01] and ContainerArchiveVEID[Not Supplied]

SQL Command:

 CreateArchiveFolder

please advice me

Thanks Ronen

Discussion Filed Under:

Comments 13 CommentsJump to latest comment

JesusWept3's picture

Would suggest getting a dtrace of StorageOnlineOpns and opening a call with symantec.
You may end up just determining the archive thats causing the problem, exporting it, deleting the archive, recreating it and re-importing the PST

MichelZ's picture

Ronen

Have you ever got a solution to this problem? We are having similar issues currently with a customer.

Thanks
Michel

Ronen Tzimbel's picture

Hi

I open a case before 1 month

and we still have a problem

Ronen

Vilian Alexandrov's picture

Hi,

JesusWept3 poited me to this topic, as i seem to have a similar problem. I'm thinking about opening another case in order to give some weight to this, as it seems many people are having such problems... Here's a link to my topic - https://www-secure.symantec.com/connect/forums/many-events-id-8453-6469-and-13360-ev-904. 

Ronen, could you perhaps provide the ID of your case so I can mention it in mine? After I create it, I will put it here so that we know what happens.

Vilian Alexandrov's picture

Hi,

JesusWept3 poited me to this topic, as i seem to have a similar problem. I'm thinking about opening another case in order to give some weight to this, as it seems many people are having such problems...

Ronen, 

perhaps you can provide your case ID so I can mention it in mine, so that Support guys will know that this is a serious problem for lots of folks.

Here is my post - https://www-secure.symantec.com/connect/forums/many-events-id-8453-6469-and-13360-ev-904 - please mention it in your future communication with Symantec.

Ronen Tzimbel's picture

hi

the case number is 02627326

in meantime I rename the null folder in outlook

and now we dont get any errors.

Ronen

Untitled.png
MichelZ's picture

Ronen

Have you got anything useful from support here?

Thanks
Michel

rasobey's picture

I'm also experiencing this issue after an upgrade to 10.0.SP3. How can I identify which archive folder it is talking about so I can remedy it?

Log Name:      Symantec Enterprise Vault
Source:        Enterprise Vault 
Date:          01/03/2013 07:12:55
Event ID:      8453
Task Category: Directory Service
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      icevstore04.cc.ic.ac.uk
Description:
The EnterpriseVault.DirectoryService object reported an error.
 
The error code was 0x80040e14 
 
 
 
Log Name:      Symantec Enterprise Vault
Source:        Enterprise Vault 
Date:          01/03/2013 07:12:55
Event ID:      13360
Task Category: Directory Service
Level:         Error
Keywords:      Classic
User:          N/A
 
Description:
An error was detected while accessing the Vault Database 'EnterpriseVaultDirectory' (Internal reference: {CADODataAccess::ExecuteSQLCommand} [.\ADODataAccess.cpp, lines {1316,1318,1333,1351}, built Dec 11 16:18:55 2012]): 
 
Description:  
 
An attempt was made to create a resource lock name with invalid values for ParentFolderVEID[170B35D658817D446A7A0AA41BB06BC1D1110000icev1] and ContainerArchiveVEID[Not Supplied]
 
 
SQL Command: 
 CreateArchiveFolder
 
 
Additional Microsoft supplied information:
 
Source:       Microsoft OLE DB Provider for SQL Server 
Number:       0x80040e14 
SQL State:    42000 
Native Error: 00050000 
HRESULT 0x80040e14
 
 
 
 
Log Name:      Symantec Enterprise Vault
Source:        Enterprise Vault 
Date:          01/03/2013 07:12:55
Event ID:      6469
Task Category: Storage Online
Level:         Error
Keywords:      Classic
User:          N/A
 
Description:
An exception has occurred.
 [Internal reference CArchiveAssister/RF/ce] 
 
 
 
Log Name:      Symantec Enterprise Vault
Source:        Enterprise Vault 
Date:          01/03/2013 07:12:55
Event ID:      8390
Task Category: Storage Online
Level:         Error
Keywords:      Classic
User:          N/A
Description:
The EnterpriseVault.DirectoryConnection object reported an error.
 
The specified archive folder already exists.
 
EDIT:
 
The following unique 13360 event IDs are also being logged:
 
Log Name:      Symantec Enterprise Vault
Source:        Enterprise Vault 
Date:          25/02/2013 10:45:55
Event ID:      13360
Task Category: Directory Service
Level:         Error
Keywords:      Classic
User:          N/A
Description:
An error was detected while accessing the Vault Database 'EnterpriseVaultDirectory' (Internal reference: {CADODataAccess::ExecuteSQLCommand} [.\ADODataAccess.cpp, lines {1316,1318,1333,1351}, built Dec 11 16:18:55 2012]): 
 
Description:  
 
Cannot insert duplicate key row in object 'dbo.Root' with unique index 'IX_VaultEntryId'. The duplicate key value is (17649949CAE615D4E88E6C703119EF5801110000icev1).
 
 
SQL Command: 
 CreateArchiveFolder
 
 
Additional Microsoft supplied information:
 
Source:       Microsoft OLE DB Provider for SQL Server 
Number:       0x80040e2f 
SQL State:    23000 
Native Error: 00002601 
HRESULT 0x80040e2f
 
 
Log Name:      Symantec Enterprise Vault
Source:        Enterprise Vault 
Date:          25/02/2013 10:45:55
Event ID:      13360
Task Category: Directory Service
Level:         Error
Keywords:      Classic
User:          N/A
Description:
An error was detected while accessing the Vault Database 'EnterpriseVaultDirectory' (Internal reference: {CADODataAccess::ExecuteSQLCommand} [.\ADODataAccess.cpp, lines {1316,1318,1333,1351}, built Dec 11 16:18:55 2012]): 
 
Description:  
 
The statement has been terminated.
 
 
SQL Command: 
 CreateArchiveFolder
 
 
Additional Microsoft supplied information:
 
Source:       Microsoft OLE DB Provider for SQL Server 
Number:       0x80040e2f 
SQL State:    01000 
Native Error: 00003621 
HRESULT 0x80040e2f
 
 
 
rasobey's picture

I've looked through all the 13360 event logs and checked out the archive ID. NONE of them exist in the EnterpriseVaultDirectory database.

I'm not sure what this is telling me. 

rasobey's picture

Not from my camp. My support are recommending that this is because of one user who has null characters in some of their folders, but I can't change anything without the consent of the customer who I cannot get hold of :(

Abraham Lincoln's picture

We struggled with this for the past 6 weeks and looks like we now have it resolved.

In our case, we got thousands of errors at a time which ended up shutting down EV with...

Log Name:      Symantec Enterprise Vault
Source:        Enterprise Vault
Date:          2/23/2013 4:36:23 PM
Event ID:      4183
Task Category: Admin Service
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      XXXXXXXX.logs.com
Description:
There have been more than 10000 Errors in the last 7200 seconds, of which 90% or more are from Enterprise Vault.
Enterprise Vault will now shut down.
 
The "more than 10000 Errors" were...
 
8390 Storage Online
6469 Storage Online
13360 Directory Service
8453 Directory Service
 
I did two things on the day that the problem was finally resolved.  I'm not entirely sure which one fixed it, or if it was a combination.
 
1) I found a folder in the affected user's mailbox that had no name.  It contained one archived item.  I moved the item and deleted the folder.
 
2) Later in the day, I did the following...
 
Disabled the user in EV.
 
SQL Server Management Studio -> Databases -> EVVault -> Tables
 
New Query
 
USE EnterpriseVaultDirectory 
SELECT *
FROM ExchangeMailboxEntry 
Where MBXAlias = '[MAILBOXALIAS]'    (where [MAILBOXALIAS] was the alias of the affected user) 
 
Then ran this...
 
USE EnterpriseVaultDirectory 
DELETE
FROM ExchangeMailboxEntry 
Where MBXAlias = '[MAILBOXALIAS]'
 
Enabled user in EV.
 
Ran provisioning task and confirmed the user was in the correct group by looking at the latest report in C:\Program Files (x86)\Enterprise Vault\Reports\Exchange Provisioning of the EV server.
 
Synchronized the user (with folder hierarchy and permissions)
 
Ran archiving (shortcuts only) on the mailbox and there weren't any errors.
 
Ran archiving (Archive items and shortcuts) on the mailbox and again, no errors.
 
Our Symantec case was 03795672
 
rasobey's picture

My problem was also resolved by renaming a folder which had no name. All's well now.

SOLUTION