After upgrade of Enterprise Vault there could be Events with IDs 29014, 6654, 28998, 6727, 41329, 7344

Article: 100010653
Last Published: 2020-12-07
Ratings: 0 0
Product(s): Enterprise Vault

Problem

After upgrading Enterprise Vault to a newer version there could be Remote Procedure Call (RPC) and Distributed Component Object Model (DCOM) errors. 
In environments with Enterprise Vault for Domino there might be also some Notes System Diagnostic (NSD) files created in the Notes IBM_TECHNICAL_SUPPORT directory.

 

Error Message

The error below are displayed in the Enterprise Vault Event Viewer:

Event ID:      29014
Task Category: Lotus Domino Mailbox Archiving Task
Level:         Error
Keywords:      Classic
Description:
Storage DCOM error.
Reason: No such interface supported  (0x80004002)
Reference: [Get storage object]
V-437-29014


Event ID:      6654
Task Category: Storage Server
Level:         Warning
Keywords:      Classic
Description:
Storage Online Process (1)  -  Restarting failed process
PID: 12280
Exit Code: ONE
The process has failed abnormally and will be restarted automatically
V-437-6654


Event ID:      28998
Task Category: Storage Crawler
Level:         Error
Keywords:      Classic
Description:
Retrieval of a saveset failed.

 
Reason:  Abnormal error occurred   Error:   Reference:   Info:  (0xc0041a47)
Saveset Id: 201309128984092~201306140854290000~Z~7098E6710E55AD226D2B8526535F8AC1
Vault Id: 1ABF45A777CDF63428A7017335A5501A41110000EVAPPJL01
Index Sequence Number: 59470
Internal Reference: Fetching Saveset for indexing
V-437-28998


Event ID:      6727
Task Category: Storage Crawler
Level:         Error
Keywords:      Classic
Description:
Abnormal error occurred  
Error:     Catastrophic failure  (0x8000ffff)
Reference: GIM/gim
Info:      19B94250A7FD0394CBD8CFE8AB6B22BA81110000EVAPPJL01 (username/domain)
           201308217101996~200701090133270000~Z~A13FE49DE5E5E112E09E32111DE77151
V-437-6727

 

Event ID:      41329
Task Category: Index Volumes Processor
Level:         Error
Keywords:      Classic
Description:
Index volume is marked as failed.

Archive Name: Archive0001
Index Volume ID: 1D96643F07157B64C817085BF82440AA91110000EV
Reason: None
Error Type: FrenzyErrorDetected

Description:
Error 1: Error encountered whilst trying to fetch item Sequence Number '210926' Item Identifier '201309048287786~201201100115080000~Z~60AC8BB606D33A148A5A933D3DE16E81'
Error 2: Error encountered whilst trying to fetch item Sequence Number '210927' Item Identifier '201309048287786~201201110851380000~Z~60AC8A6C5C0192E82645DE5839693EF1'
V-437-41329

 

Event ID:      7344
Task Category: Lotus Domino Mailbox Archiving Task
Level:         Error
Keywords:      Classic
Description:
Could not contact the Indexing Service
Please check the Indexing Service has been started on EVSERVER
Internal reference:
CCIAO/cc : No such interface supported  (0x80004002)
V-437-7344


In Vault Administration Console/Monitor Indexing Tasks, when you try to delete a failed index job from a rebuild or synchronization you may see the following:

The subtask for archive 'XXXX' could not be deleted.  Reason: Indexing Service: Class not registered

 

Cause

Some EV libraries were not registered during the upgrade thereby causing symptoms like mutant mutex objects, CLSID errors from Vault Administration Console, Notes System Diagnostic (NSD) failures, numerous events in the event logs in relation to RPC, DCOM, and failed processes.

 

Solution

Correct the content within the FileReRegister.bat script file and re-run the batch file.
 
  1. Make sure the <EnterpriseVaultDirectory>FileReRegister.bat script file had all the necessary lines and then ran that to make sure all libraries and executables were registered properly. In the original case reported the RegAsm lines near the bottom of the FileReRegister.bat script were missing and therefore running the script did not resolve the issue.
  2. To resolve the issue, it required copying the lines from a good file, modify the paths as necessary, and then run the bat file.  
  3. Important: Before modifying your FileReRegister.bat script file make a backup copy of it.

Note:  Attached is a copy of a good FileReRegister.bat file that can be used as a reference. It is labeled FileReRegister.log to prevent accidental execution.
 

 

Was this content helpful?