Forum Discussion

Jakob's avatar
Jakob
Level 5
10 years ago

Indexing is using to much ressources - EV Services shut down

Hi together,   we´re using one single EV Server 10.0.0.4 CH3 for Exchange Mailbox Archiving for ca. 2500 Mailboxes. We´re also migrate Contents from another EV site into the new Archives on the...
Enterprise Vault
Information Governance
Troubleshooting
Windows Server (2003-2008)
  • Jakob's avatar
    Jakob
    10 years ago

    Hi,

    our Vendor leaded me to the solution of this issue. There have been single corrupted indexes.

    In the Reporting Files (..\indexmetadata\reporting\system-reporting\...) they found many errors like this one:

    Could not start the [live] [indexer] ([...)\Enterprise Vault\EVIndexing\bin\indexer-service]) in [...\index7\119DD0076B5A49D48997FCEE29D820AF1_1542\live] for collection [119DD0076B5A49D48997FCEE29D820AF1_1542]:  <log ><log ><error time="193130" date="1415746863" id="SERVICE_STARTUP_RECEIVE" >Failed to receive startup confirmation from the service <string name="command" >...\Enterprise Vault\EVIndexing\bin\indexer-service</string> in directory <string name="path" >...\index7\119DD0076B5A49D48997FCEE29D820AF1_1542\live</string>: <string name="error" >An existing connection was forcibly closed by the remote host.

    We´ve renamed the mentioned index folders and the repository.xml and rebuilded the affected user archiv indexes. After this i´ve re-adjusted the values for "Maximum concurrent indexing capacity"and "Indexing memory throttling threshold" to the default values.

    So - a similar error to http://www.symantec.com/business/support/index?page=content&id=TECH213907 but with other effects.

     

Jakob's avatar
Jakob
Level 5
10 years ago

Hi,

our Vendor leaded me to the solution of this issue. There have been single corrupted indexes.

In the Reporting Files (..\indexmetadata\reporting\system-reporting\...) they found many errors like this one:

Could not start the [live] [indexer] ([...)\Enterprise Vault\EVIndexing\bin\indexer-service]) in [...\index7\119DD0076B5A49D48997FCEE29D820AF1_1542\live] for collection [119DD0076B5A49D48997FCEE29D820AF1_1542]:  <log ><log ><error time="193130" date="1415746863" id="SERVICE_STARTUP_RECEIVE" >Failed to receive startup confirmation from the service <string name="command" >...\Enterprise Vault\EVIndexing\bin\indexer-service</string> in directory <string name="path" >...\index7\119DD0076B5A49D48997FCEE29D820AF1_1542\live</string>: <string name="error" >An existing connection was forcibly closed by the remote host.

We´ve renamed the mentioned index folders and the repository.xml and rebuilded the affected user archiv indexes. After this i´ve re-adjusted the values for "Maximum concurrent indexing capacity"and "Indexing memory throttling threshold" to the default values.

So - a similar error to http://www.symantec.com/business/support/index?page=content&id=TECH213907 but with other effects.