Forum Discussion

Vipul_Desai's avatar
Vipul_Desai
Level 4
11 years ago

Indexing Issue

Dear All,

We are facing issue in one of the Journal Index Volume.

We found From the rebuild report file, 102 and 106 errors and followed the technote

http://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=&id=HOWTO56265

We need to reset the Indexing engine to solve the issue but Our EV server are configured in a Symantec Veritas Cluster.

Please let us know if we need to follow same steps listed in  http://www.symantec.com/docs/HOWTO59060 article or different steps.

Kindly suggest.

Any reply or feedback will be helpful for us.

 
Enterprise Vault
Error messages
Information Governance
Troubleshooting
Windows Server (2003-2008)
  • JesusWept3's avatar
    JesusWept3
    11 years ago

    well are you absolutely sure it needs to have indexing reinstalled?
    I mean how frequest are these errors? are any items getting indexed or are all the items timing out or deemed unable to be added to the index etc?

    For the index reinstallation, you would follow that article, probably best to do it on the passive EV Server first, then after the reinstallation completes, fail-over so its now the active server and try again and see if that resolves your situation, and if it does, you can then follow the same steps on your other EV Server

    But before that I would be interested in seeing if a regular Index Synchronization throws the same errors again or not

  • JesusWept3's avatar
    JesusWept3
    Level 6
    11 years ago

    well are you absolutely sure it needs to have indexing reinstalled?
    I mean how frequest are these errors? are any items getting indexed or are all the items timing out or deemed unable to be added to the index etc?

    For the index reinstallation, you would follow that article, probably best to do it on the passive EV Server first, then after the reinstallation completes, fail-over so its now the active server and try again and see if that resolves your situation, and if it does, you can then follow the same steps on your other EV Server

    But before that I would be interested in seeing if a regular Index Synchronization throws the same errors again or not

  • Ben_Watts's avatar
    Ben_Watts
    Level 6
    11 years ago

    IF you decide you want to reinstall the Indexing Engine you will need to take the Indexing 'Service' offline at some point to rename/delete the IndexMetaData folder as that will be shared between the nodes.

    My suggestion would be:-

    1) Take Indexing,www Offline

    2) Follow technote on Node 1

    3) Follow technote on Node 2

    4) Bring Indexing Online again (This should bring www back online too but check it anyway)

     

    BUT as JW said, are you sure Reinstalling the Indexing Engine will fix that issue.

    It doesnt take a long time to do that but it isn't something that should be undertaken as one of the first steps of 'investigation' to be honest.

  • Vipul_Desai's avatar
    Vipul_Desai
    Level 4
    11 years ago

    Thanks for your reply.

    We reinstalled EV Indexing engine.

    We ran Synchronization against failed volume ( Index Volume Range: 69220860-73023673 ) as per the suggestion from Symantec which failed with below error

     

    Error Code: 62

    Description:Error Accessing to SQL server evsqlserver.lntfinsvcs.com for database EVJournal:

    Index #0

    Message: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

    LineNumber: 0

    Source: .Net SqlClient Data Provider

    Procedure: . Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

     

    Kindly find the logs as below.

     

    Synchronize index volume started at 28/11/2014 05:18:08

        Archive Name: Journal archive
        Archive Id: 1440C39D0AD4C9C43A8F17B0D05336A7E1110000evserver.lntfinsvcs.com
        Index Volume Identity: 23309
        Index Volume Range: 69220860-73023673
        Root Path Id: 14E63461BCB023B44B42C578BBF3FB3391810000evserver.lntfinsvcs.com
        Folder: 1440C39D0AD4C9C43A8F17B0D05336A7E_23309
        Root Path: P:\EV Indexing\Index J\EV Index
        Index Server: evserver.lntfinsvcs.com
        Volume Type: 64-bit

    28/11/2014 05:18:09 Checking index volume for failed state.
    28/11/2014 05:18:09 The failed reason on the index volume may be caused by a temporary problem. Will continue synchronizing the volume.
    Failed volume reason: Unable to open the index

    28/11/2014 05:18:09 Clearing the failed status of the volume.
    28/11/2014 05:18:09 Failed status of the volume cleared.

    28/11/2014 05:18:09 Performing initial verification for the index volume.

    28/11/2014 05:20:14 The synchronize paused as it encountered an error.
    28/11/2014 05:20:19 The synchronize has resumed its processing.

    28/11/2014 05:22:24 The synchronize paused as it encountered an error.
    28/11/2014 05:23:14 The synchronize has resumed its processing.

    28/11/2014 05:25:19 The synchronize subtask has failed. 
    Error Code: 62
    Description:Error Accessing to SQL server evsqlserver.lntfinsvcs.com for database EVJournal:
    Index #0
    Message: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    LineNumber: 0
    Source: .Net SqlClient Data Provider
    Procedure: 

    . Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

    For more information, see the online index troubleshooting technical note at:

        http://www.symantec.com/docs/TECH160420
    28/11/2014 05:26:28 The synchronize has resumed its processing.

    28/11/2014 05:26:28 Performing initial verification for the index volume.

    28/11/2014 05:28:33 The synchronize paused as it encountered an error.
    28/11/2014 05:28:35 The synchronize has resumed its processing.

    28/11/2014 05:30:40 The synchronize paused as it encountered an error.
    28/11/2014 05:30:55 The synchronize has resumed its processing.

    28/11/2014 05:33:01 The synchronize subtask has failed. 
    Error Code: 62
    Description:Error Accessing to SQL server evsqlserver.lntfinsvcs.com for database EVJournal:
    Index #0
    Message: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    LineNumber: 0
    Source: .Net SqlClient Data Provider
    Procedure: 

    . Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

    For more information, see the online index troubleshooting technical note at:

        http://www.symantec.com/docs/TECH160420

     

    Kindly suggest on the same.

  • Ben_Watts's avatar
    Ben_Watts
    Level 6
    11 years ago

    Its basically saying there was a problem contacting the SQL DB to carry out the Sync for one reason or another.

    Is SQL contactable?

    Is the EVJournal DB mounted and Online?

    Do you have the correct permissions assigned to the VSA for that DB/SQL? (Deployment Scanner/SymHelp)

    Do you have archiving on going at the moment to that DB?

    Can you sync any other Indexes that are on that DB?