Please enter search query.
Search <product_name> all support & community content...
Article: 100039343
Last Published: 2021-06-16
Ratings: 0 1
Product(s): Enterprise Vault
Description
Event log messages and their meaning on startup on indexing service:
Index service on startup normally performs the following operations:
i. Indexing service initialization routines
ii. Starts the indexing engine
iii. Synchronize index metadata between 64-bit indexing engine's repository and directory database if required.
iv. Start
IndexBroker.exe process to manage 32-bit index volumes
v. Start
EVIndexVolumesProcessor and
EVIndexQueryServer to manage operations on 64-bit index volumes.
vi. Check for any the pending work from storage
Indexing service on startup will log appropriate event log messages based on the above-mentioned operations.
Indexing admin service will start 64-bit indexing engine and synchronize index metadata.
If index metadata is required to be updated then this process might take a long time as per following scenarios:
i. Directory database and index metadata are in sync (normal scenario)
ii. Startup of indexing service when index metadata is missing OR failover scenario in a building blocks environment
Directory database and index metadata are in sync
In normal circumstances, the indexing service will log following messages at this stage:
1. In cases where the Indexing Service manages 32 bit index volumes (normally present on upgraded index servers) then IndexBroker.exe process will be launched by Indexing Admin Service. Please note that Indexing Admin Service will only launch this process if 32-bit index volumes are managed by Indexing Service.
An event log message will reflect the launch on IndexBroker.exe process:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 7345
Task Category: Index Broker
Level: Information
Keywords: Classic
User: N/A
Computer: testindex3.testindex.local
Description:
IndexBroker has started on this server to manage old 32 bit index volumes.
2. Once all initialization routines are completed, the indexing service will log the following event log message:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41302
Task Category: Index Admin Service
Level: Information
Keywords: Classic
Computer: testindex3.testindex.local
Description:
The Indexing Service has completed its initialization. The service is now functioning fully.
3. "Indexing service has started" message will be subsequently logged.
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41297
Task Category: Index Admin Service
Level: Information
Keywords: Classic
Computer: testindex3.testindex.local
Description:
The Indexing Service has started (10.0.0.1316).
4. After indexing service becomes functional, it then runs a check to find any pending work from storage and once this process is completed, then an event log message is logged, stating how many index volumes have any pending work.
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41365
Task Category: Index Admin Service
Level: Information
Keywords: Classic
Computer: testindex3.testindex.local
Description:
Summary of the current index volume check:
Volumes synchronized: 0
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.
Startup of indexing service when index metadata is missing OR failover scenario in a building blocks environment
In case index metadata is missing from repository OR index metadata for existing index volumes on failed over index server is recreated on backup index server. This process can take a long time depending on the number of existing 64-bit index volumes on failed-over index server.
1. In this scenario, synchronization of index volume metadata between the indexing engine repository and directory database will be started and a message will be logged in event log.
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41372
Task Category: Index Admin Service
Level: Information
Keywords: Classic
Computer: testindex3.testindex.local
Description:
Indexing Service has started the synchronization of index volume metadata between the indexing engine repository and the Directory database.
2. This message will be logged after every 20 seconds until indexing service initialization routines are completed:
Log Name: Veritas Enterprise Vault
Source: Enterprise Vault
Event ID: 41299
Task Category: Index Admin Service
Level: Information
Keywords: Classic
Computer: testindex3.testindex.local
Description:
The Indexing Service is pending initialization.
Requesting additional time for initialization routines....
3. Following message will be logged once initialization routines are completed:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41297
Task Category: Index Admin Service
Level: Information
Keywords: Classic
Computer: testindex3.testindex.local
Description:
The Indexing Service has started (10.0.0.1316).
4. A subsequent message will be logged that indexing service has started but must complete additional work before responds to external work.
This means that synchronization of index volumes metadata between indexing engine repository and directory database is still running and indexing service will only accept new request once this process has completed.
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41303
Task Category: Index Admin Service
Level: Information
Keywords: Classic
Computer: testindex3.testindex.local
Description:
The Indexing Service has been started, but must complete additional work before it can respond to external requests.
5. Indexing service will log a progress summary every 10 minutes in case index volumes metadata and directory database synchronization takes a long time:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41376
Task Category: Index Admin Service
Level: Information
Keywords: Classic
Computer: testindex3.testindex.local
Description:
Indexing Service is synchronizing index volume metadata between the indexing engine repository and the Directory database.
Progress summary:
Created metadata for 1392 index volume(s) in indexing engine.
Updated location for 0 index volume(s) in indexing engine.
6. Once indexing service has completed synchronization of index volume metadata between the 64-bit indexing engine repository and the directory database then following message is logged:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41377
Task Category: Index Admin Service
Level: Information
Keywords: Classic
Computer: testindex3.testindex.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: 3406
Total index volume(s) whose location was updated: 0
7. In case any index volumes metadata is deleted during synchronization of index volumes metadata and directory database then following event log message is logged:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41375
Task Category: Index Admin Service
Level: Information
Keywords: Classic
Computer: TESTINDEX9.testindex.local
Description:
Indexing service has removed redundant metadata for 3 index volume(s) from the indexing engine repository.
8. If indexing service manages 32 bit index volumes (normally present on upgraded index servers) then IndexBroker.exe process will be launched by indexing admin service.
Please note that indexing admin service will only launch this process if 32-bit index volumes are managed by indexing service. An event log message will reflect the launch on IndexBroker.exe process at this stage:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 7345
Task Category: Index Broker
Level: Information
Keywords: Classic
Computer: testindex3.testindex.local
Description:
IndexBroker has started on this server to manage old 32 bit index volumes.
9. Once all sub processes of indexing server are successfully launched then an event log message will be logged that indexing service is now fully functional:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41302
Task Category: Index Admin Service
Level: Information
Keywords: Classic
Computer: testindex3.testindex.local
Description:
The Indexing Service has completed its initialization. The service is now functioning fully.
10. After indexing service becomes fully functional it then runs a check to find any pending work from storage and once this process is completed then an event log message is logged, stating how many index volumes have any pending work. This process can also be time consuming.
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41365
Task Category: Index Admin Service
Level: Information
Keywords: Classic
Computer: testindex3.testindex.local
Description:
Summary of the current index volume check:
Volumes synchronized: 0
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.
Event log messages when indexing service is stopped:
1. Once a shutdown process of indexing service is initiated, if index server manages 32-bit index volumes then IndexBroker.exe process is stopped first and following message will be logged in event log:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 7346
Task Category: Index Broker
Level: Information
Keywords: Classic
Computer: testindex3.testindex.local
Description:
IndexBroker has stopped.
2. Once all 64-bit index volume related processes are successfully stopped then following event log message is logged:
Log Name: Enterprise Vault
Source: Enterprise Vault
Event ID: 41298
Task Category: Index Admin Service
Level: Information
Keywords: Classic
Computer: testindex3.testindex.local
Description:
The Indexing Service has stopped
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.