Description
This document aims to highlight the key event messages that are seen when starting the Indexing Service.
The server Cache location has not been set
A Cache location must be specified on every Indexing Server prior to starting the Indexing Service. During Indexing Service startup, the service checks that the server Cache location has been configured correctly. If it has not been set, then the Indexing Service will stop.
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41312
Task Category: Index Admin Service
Level: Error
Computer: IndexServer1.server.local
Description:
The Indexing Service could not complete all the required startup routines: Enterprise Vault Server Cache is not configured for this computer. Service will be stopped.
See the Enterprise Vault Administration Console help for details on setting the Cache location.
Paths to index locations that contain non-ASCII characters
When the Indexing Service starts, it checks for index locations that have invalid characters in their path names. If any of the path names contain non-ASCII characters, then the Indexing Service will close these locations and then the Indexing Service will stop. An event is displayed in the event viewer to prompt the user that this has occurred:
Event ID: 41312
Task Category: Index Admin Service
Level: Error
Description:
The Indexing Service could not complete all the required startup routines:
Some of the open index locations contained invalid characters.
These index locations have been closed. Service will be stopped.
The Indexing Service can now be manually restarted.
The Indexing Service checks and reports index locations that are closed or in backup mode
Any index locations that are closed or in backup mode are reported in the event viewer:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41307
Task Category: Index Admin Service
Level: Information
Computer: IndexServer1.server.local
Description:
The following index locations are closed and/or in backup mode:
\\indexserver1\c$\Remote Location\index1
\\indexserver1\c$\Remote Location\index2
\\indexserver1\c$\Remote Location\index3
\\indexserver1\c$\Remote Location\index4
\\indexserver1\c$\Remote Location\index5
\\indexserver1\c$\Remote Location\index6
\\indexserver1\c$\Remote Location\index7
\\indexserver1\c$\Remote Location\index8
\\indexserver1\e$\RemoteIndex1\index1
\\indexserver1\e$\RemoteIndex1\index2
\\indexserver1\e$\RemoteIndex1\index3
\\indexserver1\e$\RemoteIndex1\index4
\\indexserver1\e$\RemoteIndex1\index5
\\indexserver1\e$\RemoteIndex1\index6
\\indexserver1\e$\RemoteIndex1\index7
\\indexserver1\e$\RemoteIndex1\index8
If all available index locations are closed or in backup mode, then no data will be indexed until at least one index location is open and not in backup mode. This is also reported in the event viewer:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41316
Task Category: Index Admin Service
Level: Warning
Computer: IndexServer1.server.local
Description:
All the index locations on this server are closed and/or in backup mode. No indexing can take place until at least one location is open and taken out of backup mode.
Indexing Service initialization
When the Indexing Service is initialized, it is reported in the event viewer:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41299
Task Category: Index Admin Service
Level: Information
Computer: IndexServer1.server.local
Description:
The Indexing Service is pending initialization.
Requesting additional time for initialization routines....
The Index Volume Metadata on disk is compared with the Directory Database
A consistency check between the Index Volume Metadata on disk and the Directory Database is performed as the service starts, which is reported in the event viewer:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41372
Task Category: Index Admin Service
Level: Information
Computer: IndexServer1.server.local
Description:
Indexing Service has started the synchronization of index volume metadata between the indexing engine repository and the Directory database.
If there is a mismatch between the Index Volume Metadata on disk and the Directory Database, then this can cause the Indexing Service to take a long time to start up, as this work must be completed prior to the Indexing Services being available.
The Indexing Service has started
When the Indexing Service has started, this is reported in the event viewer:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41297
Task Category: Index Admin Service
Level: Information
Keywords: Classic
User: N/A
Computer: IndexServer1.server.local
Description:
The Indexing Service has started (10.0.0.1299).
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41303
Task Category: Index Admin Service
Level: Information
Computer: IndexServer1.server.local
Description:
The Indexing Service has been started, but must complete additional work before it can respond to external requests.
Indexing Engine Metadata synchronization completion
When synchronization between the Indexing Engine Metadata on disk and the Directory Database is complete, but did not change anything, this is reported in the event viewer:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41373
Task Category: Index Admin Service
Level: Information
Computer: IndexServer1.server.local
Description:
Indexing Service has completed the synchronization of index volume metadata between the indexing engine repository and the Directory database.
When synchronization between the Index Volume Metadata on disk and the Directory Database is complete and metadata was created or the location has been updated, this is reported in the event viewer:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41377
Task Category: Index Admin Service
Level: Information
Computer: IndexServer1.server.local
Description:
Indexing Service has completed the synchronization of index volume metadata between the indexing engine repository and the Directory database.
Total index volume(s) whose metadata was created: 1
Total index volume(s) whose location was updated: 0
If there are 32 bit index volumes in the environment
Additional Indexing service components are started if there are 32bit index volumes in the environment, which are reported in the event viewer. If it is a fresh installation of V10 or all pre-V10 index volumes have been upgraded, then the Index Broker will not start and it will not be reported in the event viewer:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 7345
Task Category: Index Broker
Level: Information
Computer: IndexServer1.server.local
Description:
IndexBroker has started on this server to manage old 32 bit index volumes.
The Indexing Service checks for pending work after startup
The number of index volumes found with pending work is reported in the event viewer:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41365
Task Category: Index Admin Service
Level: Information
Computer: IndexServer1.server.local
Description:
Summary of the current index volume check:
Volumes synchronized: 1
Failed volumes synchronized: 0
The next synchronization checks will take place as follows:
Volumes having pending work in 0 hours and 59 minutes
Failed volumes in 5 hours and 59 minutes
All volumes in 9 hours and 59 minutes.
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.