Error Message

Event ID 6727 containing the following: 

Event ID:       6727
Task Category:  Storage Crawler
Level:          Error
Description:    Abnormal error occurred
Error:          <0x8004010e>

Dtrace of StorageCrawler shows:

*Below lines shows that MAPIInitialize returned an error

16566 09:15:54.644 [38884] (StorageCrawler) <6692>  EV:H {CSingleObjectComApartment::Apartment:#220} MAPIInitialize returned [0x8004010e]
16567 09:15:54.644 [38884] (StorageCrawler) <6692>  EV:H {CSingleObjectComApartment::Apartment:#387} ATL exception in apartment thread (hr=<0x8004010e>)
16568 09:15:54.644 [38884] (StorageCrawler) <50624> EV:H {CSingleObjectComApartment::Apartment:#220} MAPIInitialize returned [0x8004010e]
16569 09:15:54.644 [38884] (StorageCrawler) <50624> EV:H {CSingleObjectComApartment::Apartment:#387} ATL exception in apartment thread (hr=<0x8004010e>)
16570 09:15:54.925 [38884] (StorageCrawler) <30188> EV~E Event ID: 6727 Abnormal error occurred | |Error:     <0x8004010e> |Reference: TR/mi |Info:

*We see event id 6727 logged for each and thread and then shutdown is initiated as show in below line. All StorageCrawler threads are stopped causing EV Indexing to halt

16961 09:16:55.159 [38884] (StorageCrawler) <68212> EV:H CStorageCrawlerModule::Shutdown: Initiated server shutdown. (hr=Success  (0))
16962 09:16:55.159 [38884] (StorageCrawler) <68212> EV:M CStorageCrawlerModule::PostMessageLoopImpl: Shutdown returned 0x00000000
16963 09:16:55.159 [38884] (StorageCrawler) <68212> EV:M CStorageCrawlerModule::PostMessageLoopImpl: Shutting down FetchAheadThreads
16964 09:16:55.159 [38884] (StorageCrawler) <68212> EV:M CFetchAheadThread::Shutdown [20] threads

When some or all of the StorageCrawler worked threads receive a failure HRESULT code from the MAPIInitialize() call, this error code is treated as a major failure, causing the underlying thread to terminate and invariably resulting in shutdown of the StorageCrawler process. Further to it no indexing occurs during this period of time until the Storage & Indexing Services on the affected servers are re-started.

This issue has been addressed in the following release.

Enterprise Vault 12.3.2 Release

https://www.veritas.com/support/en_US/article.100043310