Enterprise Vault StorageCrawler fails to retrieve an item with event 6727 & 28998

Article: 100044949
Last Published: 2025-12-02
Ratings: 1 1
Product(s): Enterprise Vault

Problem

Enterprise Vault StorageCrawler fails to retrieve items with event 6727 & 28998. In certain circumstances CPU consumption by StorageCrawler may increase which further can impact the indexing. 

 

Error Message

The event logs will show the following events. 

Type :        Error
Event :        6727
Source :        Enterprise Vault 
Category :    Storage Crawler
Computer :    evserver1.ev.local
Description:
Abnormal error occurred 
 
Error:     The requested lookup key was not found in any active activation context.  (0x800736b7) 
Reference: GIM/gim 
Info:      163CE32264BDC6E44AFC43BE9129E79A21110000evserver1 (User1) 
           202009170327203~202009170718210000~Z~414068A45CD7921641B79F16300705D1 
            

For more information, see Help and Support Center at http://telemetry.community.veritas.com/entt?product=ev&language=english&version=12.3.0.0&build=12.3.0.1365&error=V-437-6727

 

Type :        Error
Event :        28998
Source :        Enterprise Vault 
Category :    Storage Crawler
Computer :    evserver1.ev.local
Description:
Retrieval of a saveset failed. 
 
Reason: Abnormal error occurred      Error:        Reference:    Info:                                        (0xc0041a47) 
Saveset Id: 202009170327203~202009170718210000~Z~414068A45CD7921641B79F16300705D1 
Vault Id: 1A6690C2FE3F9704998AC1C111B751B421110000evserver1 
Index Sequence Number: 202254973 
Internal Reference: Fetching Saveset for indexing 

For more information, see Help and Support Center at http://telemetry.community.veritas.com/entt?product=ev&language=english&version=12.3.0.0&build=12.3.0.1365&error=V-437-28998

 

You may also see the following variation of event ID 6727.

Event ID: 6727 Abnormal error occurred 
Error:  Unspecified error (0x80004005) 
Reference: GIM/gim |Info: 1D785EF442D31DF45BD1E68B5990ED7071110000evserver1 (User1)           201810179724673~201810162115410000~Z~E0484FA3BAE44612FC8DFA4566419B31 

Cause

The problem may occur if there are high number of calls to CDOSYS. 

 

Solution

Please contact Veritas Technical Support for further investigation.

Was this content helpful?