Error Message

The following snippets can be seen in the trace of the 'StorageCrawler' process:

(StorageCrawler)        <45064>        EV:M        CItemFetcher::Start ArchiveId:1F6CB7D8AE8B84740837A14C5E2ECDE731110000EV01 (Old:(null))

(StorageCrawler)        <51004>        EV:L        CItemFetcher::RequestItem New fetch request NextISN:9220589 ItemISN:0 SSID:(null) (hr=There are no more items.      (0x80041b3b))

(StorageCrawler)        <35164>        EV:L        CADOContext::CreateConnection exit. source:Provider=SQLOLEDB;Server=sqlev.EV.Local;Database=EVVSVS08_9;Trusted_Connection=Yes hr=Success  (0)

(StorageCrawler)        <45064>        EV:L        CItemFetcher::Start ArchiveID:1F6CB7D8AE8B84740837A14C5E2ECDE731110000EV01 (hr=Success  (0))

(StorageCrawler)        <51004>        EV:M        CItemFetcher::RequestItem NextISN:9220589 MaxISN:18446744073709551615 Format:3 MaxMarshallSize:10240 (KB) IIRebuildMode:1 (hr=There are no more items.      (0x80041b3b)) Last indexing retry:no

In some cases, we might see the event below:

Log Name: Veritas Enterprise Vault
Source: Enterprise Vault
Event ID: 41352
Task Category: Index Volumes Processor
Level: Error
Computer: evarch1.ev.local
Description:
The processing of the Index Volume has stopped following errors.

Archive name: Test User1
Task:
Index Volume ID: 13440237A1A0EEF45AA584C107C65DE821110000evserver1_1029
Reason:
Error Type: NonCritical

Description: Unexpected COM exception caught. Archive Id=[13440237A1A0EEF45AA584C107C65DE821110000evserver1] HRESULT=0x80047192

V-437-41352

The code 0x80047192 indicates the following: The item has not yet been written to the partition.  The StorageCrawler process may be stuck in a loop trying to fetch a particular item that may be stuck in the storage queue. This looping may result in high CPU usage on the EV server. As a result, subsequent items that are added to the archive are not indexed. 

Workaround:

Restarting the storage service may allow indexing of the archive to progress. Although indexing may get stuck again later, if items continue to get stuck in the storage queue. 

There may be several reasons why an item gets stuck in a storage queue, so identifying the root cause and preventing this will aid in the indexing issue.