02-25-2011 02:03 PM
Getting these errors everytime we file system archiving. In the file system archiving reports it shows ARCHIVE *** Error *** - Exception from HRESULT: 0x800A0CC1, after every file that it tries to archive.
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Date: 2/25/2011 2:38:47 PM
Event ID: 13345
Task Category: File System Archiving Task
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
An error was detected while accessing the Vault Database 'Provider=SQLOLEDB;Server=Evaultsql2;Database=EVVSGEVVSG01_1_1;Integrated Security=SSPI' (Internal reference: CADODataAccess::AddInputParameter @Type_0 .\ADODataAccess.cpp [lines {2148,2165}], built Nov 24 00:04:01 2010), error code <0x800a0cc1>.
SQL Command:
N/A
Date: 2/25/2011 2:38:05 PM
Event ID: 13360
Task Category: File System Archiving Task
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
An error was detected while accessing the Vault Database 'Provider=SQLOLEDB;Server=Evaultsql2;Database=EVVSGEVVSG01_1_1;Integrated Security=SSPI' (Internal reference: CADODataAccess::AddParameter @Type_0 .\ADODataAccess.cpp [lines {2213,2226}], built Nov 24 00:04:01 2010):
Description:
Item cannot be found in the collection corresponding to the requested name or ordinal.
SQL Command:
N/A
Additional Microsoft supplied information:
Source: ADODB.Parameters
Number: 0x800a0cc1
SQL State:
Native Error: -2146825023
HRESULT 0x800a0cc1
Solved! Go to Solution.
02-28-2011 02:52 PM
Looking at the technote it shows that it hasn't been fixed and is currently under investigation, it will be fixed by way of hotfix or next service pack or next major release but theres no ETA, most people should subscribe to the technote and when a fix is released or when they show what resolves the issue, the technote will be updated.
However if it's something majorly important then a case should be created and be asked to reference the ETrack that exists for it
02-25-2011 02:20 PM
Looks like the issue is being researched. I recommend opening a case and cite this technote:
Article URL http://www.symantec.com/docs/TECH136146
EDITED==> I found this in the EV 9 sp1 Updates.htm, you might just need to upgrade.
In certain circumstances, the number of file types associated with archived items exceeded the maximum number of entries in the file specification table in the Enterprise Vault directory database. When this happened, archiving failed and Event ID 13345 and 13360 error messages were reported in the event log during an archiving run.
This issue occurred in the following situations:
File extension management has been enhanced. Enterprise Vault now normalizes file extensions where possible, to reduce the number of additional entries created in the file specification table.
02-28-2011 02:25 PM
We have a ticket opened with Symantec. Sent dtrace and event logs last Friday. No word yet.
We are currently on 9.01. The errors just started occuring last week. It appears maybe they didn't fix this "Archiving failed when maximum number of file types was exceeded" in this version. What do you think?
02-28-2011 02:52 PM
Looking at the technote it shows that it hasn't been fixed and is currently under investigation, it will be fixed by way of hotfix or next service pack or next major release but theres no ETA, most people should subscribe to the technote and when a fix is released or when they show what resolves the issue, the technote will be updated.
However if it's something majorly important then a case should be created and be asked to reference the ETrack that exists for it