cancel
Showing results for 
Search instead for 
Did you mean: 

EV Saveset Error

Matthew_Kimler
Level 5

In an older Discovery Accelerator case, it was brought to my attention that an error existed on an item that was under review. When I went to the DA event log, I saw the following error:

APP AS - Customer ID: 24 - An Error has occured when retrieving Item
SaveSetID: 200902050000000~200902051348510000~Z~D15AE24533E403A1C6536B2C220836B1
VaultID: 1901E41648F2E4F4EBC8D7CA8EC9EF3E01110000evsite
Format: XML
sAttachmentID: 0.
System.Runtime.InteropServices.COMException (0x80040307): Item not found.
at KVS.EnterpriseVault.Interop.IItem.Get(Int32 DetailLevel)
at KVS.Common.VaultItem.Item.CallEcmAPI(String sSaveSetID, String sVaultID, String sAttachmentID, String sFormat) 

 

If I use EVSVR in interactive mode, I get the following:

EVSVR Command>dumpsaveset 1901E41648F2E4F4EBC8D7CA8EC9EF3E01110000evsite 200902050000000~20090205134
8510000~Z~D15AE24533E403A1C6536B2C220836B1 -o d:\logs
2011-09-26 13:52:05  Log file 'd:\logs\EVSVR_DumpSaveset_20110926135205\EVSVR_DumpSaveset_2011092613
5205.Log' created/opened
2011-09-26 13:52:05
2011-09-26 13:52:05  EVSVR Version (9.0.2.1061)
2011-09-26 13:52:05
2011-09-26 13:52:05  Initialising operation
2011-09-26 13:52:05  Arguments: 1901E41648F2E4F4EBC8D7CA8EC9EF3E01110000evsite 200902050000000~20090
2051348510000~Z~D15AE24533E403A1C6536B2C220836B1 -o d:\logs
2011-09-26 13:52:05  Output folder: d:\logs\EVSVR_DumpSaveset_20110926135205\
2011-09-26 13:52:05  Log file path: d:\logs\EVSVR_DumpSaveset_20110926135205\EVSVR_DumpSaveset_20110
926135205.Log
2011-09-26 13:52:05  Found an archive: Parameter 1901E41648F2E4F4EBC8D7CA8EC9EF3E01110000evsite is t
he entry id for archive 'evsystemFCXJRNL02' that is in vault store 'Journaling'.
2011-09-26 13:52:06  Log file closed
2011-09-26 13:52:06
DumpSaveset Initialisation failed: ERROR: The second parameter 200902050000000~200902051348510000~Z~
D15AE24533E403A1C6536B2C220836B1 is not a valid saveset or transaction id. Error: The specified Save
set does not exist.      (0xc0041aac). Error: 0xc0041aac

 

What I hope is good news, is that if I go to the storage location, I see collection files and one of them with the following two DVS files:

D15AE24533E403A1C6536B2C220836B1.DVS
D15AE24533E403A1C6536B2C220836B1~50~4DB423EB~00~1.DVSSP

 

Is there a way to fix this? Running some other EVSVR verify commands I found some errors shown below, but could not find that particular saveset mentioned. It should be noted though that I was trying to limit the data range and it's possible it was archived a later date or something. I have about 1000 of these errors in a 1 week period of my EVSVR verify run:

2011-09-23 03:14:51            SavesetId: 201002105830723~201002101931590000~Z~D022E94ADE210F311DD7E811F4B21F01, Archived Date: 2010-02-10 19:38:00Z
2011-09-23 03:14:51              ArchiveEntryId: 1901E41648F2E4F4EBC8D7CA8EC9EF3E01110000evsite
2011-09-23 03:14:51              Collection Identity: 211579, DVS RelativeFileName: 2010\02-10\D\Collection211579.CAB
2011-09-23 03:14:51              Fingerprint validation failed [0x80041b9f]

 

Any help would be helpful. Thanks.

1 ACCEPTED SOLUTION

Accepted Solutions

Matthew_Kimler
Level 5

Symantec support was unable to repair it. It seems that in 2009 when the item went to be put on hold, it failed to do so. It reported an error but no one checks the errors. It just expired and went away.

Thanks for all of the help. My advice is to remind peopole to check the error reports.

View solution in original post

6 REPLIES 6

John_Chisari
Level 6
Partner Accredited

As you can probably tell, the database reference for that saveset does not exist anymore - maybe it was expired?

Anyway, to add it back in, runn EVSVR as you have with the Repair/Database References Option - this will recreate the database entries for the saveset files.

 

The fingerprint validation error you were getting - you may want to try a dumpset on it.  It "could" be related to this technote - http://www.symantec.com/docs/TECH166430 - which is still being worked on.

Matthew_Kimler
Level 5

I'm going to work on the EVSVR option and see if that fixes it. It will be at least a week before I can update you on this since the process is quite intensive.

Thanks for the assistance.

Matthew_Kimler
Level 5

The repair is still running. Will let you know.

JesusWept3
Level 6
Partner Accredited Certified
Make sure that you tell DA to put items on hold automatically, because if you don't, export and user deletes can still be performed, which is most likely (as Chisari noted) what happened here Also when running EVSVR you should try and narrow the one frame as much as possible and to the specific vault store partition, in this case running for Feb 20th 2010 should have been enough. Also make sure you set it so that it does not require an index entry, because if it's an expiration or deleted item, the index entry wont exist, and by default EVSVR requires the item have an index entry. The downside to this is you may end up reinserting items that users have deleted or expired and don't want back in their vault (for items that have expired, you could actually breaking compliance by reintroducing items that should have expired back in to the environment, but regular expiry should pick it up again on the next run) And last but not least IF the item did in fact expire, next storage expiry run will delete it again
https://www.linkedin.com/in/alex-allen-turl-07370146

Matthew_Kimler
Level 5

Symantec support was unable to repair it. It seems that in 2009 when the item went to be put on hold, it failed to do so. It reported an error but no one checks the errors. It just expired and went away.

Thanks for all of the help. My advice is to remind peopole to check the error reports.

JesusWept3
Level 6
Partner Accredited Certified
Wait You found the DVS though and they couldn't insert it back in? That's weird
https://www.linkedin.com/in/alex-allen-turl-07370146