Forum Discussion

NameTaken's avatar
NameTaken
Level 4
11 years ago

Invalid archive ID

Good afternoon,   We've got quite a few error messages relating to an archive ID which does not seem to exist (at least, not any more).  The event ID 13360 is generated by the Directory Service...
Enterprise Vault
Error messages
Information Governance
Troubleshooting
Windows Server (2003-2008)
  • JesusWept3's avatar
    JesusWept3
    11 years ago

    Probably best off doing an EVSVR in report mode

    1. Go to a command prompt
    2. CD \Program Files (x86)\Enterprise Vault\
    3. Type 'evsvr' and press Enter
    4. Type 'edit' and press Enter
    5. In the drop down box next to Operation - choose "Verify"
    6. In the drop down box next to Option - choose "ArchivesDirectory"
    7. Bump up the threads to like 5 or so, or to match however many processors/cores the machine has
    8. Press OK
    9. Press Start
    10. Wait for the EVSVR to complete 
    11. Review the log file

    If i had to guess it would be either that a transaction rolled back somewhere along the line OR you restored the Directory database recently.

    Like you said, you could DTrace, you could either trigger on the Archive ID and include 10,000 lines which may catch it, you could Filter and use the Archive ID but its probably not going to give you the correct amount of information OR your best bet is to BackTrace using the archiveID

  • AndrewB's avatar
    AndrewB
    11 years ago

    i found this thread which describes a similar error. hope it steers you in the right direction. https://www-secure.symantec.com/connect/forums/upgrade-enetrprise-vault-10-sp1-sp2

JesusWept3's avatar
JesusWept3
Level 6
11 years ago

Probably best off doing an EVSVR in report mode

1. Go to a command prompt
2. CD \Program Files (x86)\Enterprise Vault\
3. Type 'evsvr' and press Enter
4. Type 'edit' and press Enter
5. In the drop down box next to Operation - choose "Verify"
6. In the drop down box next to Option - choose "ArchivesDirectory"
7. Bump up the threads to like 5 or so, or to match however many processors/cores the machine has
8. Press OK
9. Press Start
10. Wait for the EVSVR to complete 
11. Review the log file

If i had to guess it would be either that a transaction rolled back somewhere along the line OR you restored the Directory database recently.

Like you said, you could DTrace, you could either trigger on the Archive ID and include 10,000 lines which may catch it, you could Filter and use the Archive ID but its probably not going to give you the correct amount of information OR your best bet is to BackTrace using the archiveID