Forum Discussion

Sarah_Seftel1's avatar
Sarah_Seftel1
Level 6
13 years ago
Solved

Index upgrade to 64 bit error msg in Journal

Hi all,

I have errors in EV server on upgrade index task for Journal archive.

the error is:

 

Log Name:      Symantec Enterprise Vault
Source:        Enterprise Vault 
Date:          2/28/2013 5:53:31 PM
Event ID:      41352
Task Category: Index Volumes Processor
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server Name
Description:
The processing of the Upgrade Sub task has stopped following errors.
 
Upgrade Sub task ID: 12EB8C465E838D84E88B2A8242AB4B2E11110000evsite_0
Reason: Undefined
Error Type: NonCritical
 
Description: Unable to find the highest index sequence number of the 32 bit volumes for archive id [12EB8C465E838D84E88B2A8242AB4B2E11110000evsite]. 
 
 
attached print screen of index, the weird thins is that it shows 1-Not Set on the 32bit index.
if upgrade was done successfully from 32 to 64 bit indexing, shouldn't the 64bit index start from1? since it starts with 2562665...
 
any advice?
 
Sarah
Enterprise Vault
Error messages
Information Governance
Tip-How to
Windows Server (2003-2008)

8 Replies

  • TonySterling's avatar
    TonySterling
    Moderator
    13 years ago

    Did you try to rebuild or just upgrade?

    If only upgrade, try to rebuild it.  If that fails run a dtrace of the following:

    • EVIndexAdminService.exe
    • EVIndexVolumesProcessor.exe
    • StorageCrawler.exe

    Seems like the 32 bit index was corrupt to begin with.

  • TonySterling's avatar
    TonySterling
    Moderator
    13 years ago

    Yep, but if it completes it will be 64-bit and it was pretty useless the way it was. wink

  • Sarah_Seftel1's avatar
    Sarah_Seftel1
    Level 6
    13 years ago

    well, it did complete, however, it still has in 32bit range '1-Not Set' so... I opened a case at Symantec.

    Will update this thread once we have results.

  • Sarah_Seftel1's avatar
    Sarah_Seftel1
    Level 6
    13 years ago

    Should smiley

    but I checked and the folder of the 32bit exist, and has 1.8 GB of index.

    Plus the fact that 64bit index starts from range 2,078,897... while it should have started from 1...

    My guess is that something went wrong and the 32bit index file are not counted correctly.

     

  • JesusWept3's avatar
    JesusWept3
    Level 6
    13 years ago

    huh, what happens if you perform a synchronize on that index?

  • Sarah_Seftel1's avatar
    Sarah_Seftel1
    Level 6
    13 years ago

    Well, you learn something new every day smiley

    Synchronizing the Journal Index brought back the correct range.

    Now upgrade task is running.

     

    Thanks!

     

    Sarah