Error Message

EV Event Log entries on the DA server:

Log Name:      Veritas Enterprise Vault
Source:        Accelerator Manager 
Event ID:      483
Task Category: None
Level:         Error
Keywords:      Classic
Description:
APP Analytics - AnalyticsIngesterTask.exe with TransactionId X could not create ECM API objects. Please confirm that Enterprise Vault is installed properly and Discovery Accelerator is configured correctly according to Enterprise Vault installed version. Exception: Symantec.Accelerator.Analytics.NoECMObjectsException: Unable to create ECM API Objects. ---> System.Runtime.InteropServices.COMException: An internal failure occurred. Internal Error: 'Invalid class string  (0x800401f3)'.
   at KVS.EnterpriseVault.Interop.IArchiveMetaData.get_IndexData()
   at Symantec.Accelerator.Analytics.AnalyticsIngester.CanCreateECMAPIObjects(Exception& ex)
   --- End of inner exception stack trace ---
   at Symantec.Accelerator.Analytics.AnalyticsIngester.StartIngestion()
   at Symantec.Accelerator.Analytics.AnalyticsIngesterApp.StartIngestionProcess(Int64 transactionId, String dbServerName, String dbName, Int32 caseId)

V-437-483

Log Name:      Veritas Enterprise Vault
Source:        Accelerator Manager 
Event ID:      486
Task Category: None
Level:         Error
Keywords:      Classic
Description:
APP Analytics - AnalyticsIngesterTask.exe with TransactionId 2545 failed to start processing, terminating.

V-437-486

Similar entries may be seen in a DTrace of the AnalyticsIngesterTask process whilst attempting to enable Analytics:

[1234]    (AnalyticsIngesterTask)    <567>    EV-M    {-} {AcceleratorEvent} {CX} Event logging initialised for 'Accelerator Manager'. Event log name - Veritas Enterprise Vault
[1234]    (AnalyticsIngesterTask)    <567>    EV-H    {-} Exception: Error Ingestion_Could_Not_Create_ECM_Objects_Error 
Info:{AcceleratorEvent} {CX} AnalyticsIngesterTask.exe with TransactionId X could not create ECM API objects. Please confirm that Enterprise Vault is installed properly and Discovery Accelerator is configured correctly according to Enterprise Vault installed version. 
Exception: Symantec.Accelerator.Analytics.NoECMObjectsException: Unable to create ECM API Objects. 
---> System.Runtime.InteropServices.COMException: An internal failure occurred. Internal Error: 'Invalid class string  (0x800401f3)'.
|   at KVS.EnterpriseVault.Interop.IArchiveMetaData.get_IndexData()
|   at Symantec.Accelerator.Analytics.AnalyticsIngester.CanCreateECMAPIObjects(Exception& ex)
|   --- End of inner exception stack trace ---
|   at Symantec.Accelerator.Analytics.AnalyticsIngester.StartIngestion()
|   at Symantec.Accelerator.Analytics.AnalyticsIngesterApp.StartIngestionProcess(Int64 transactionId, String dbServerName, String dbName, Int32 caseId) 
Diag: 
Type:System.Exception 
ST: Inner:None
[1234]    (AnalyticsIngesterTask)    <567>    EV-H    {-} Exception: Error Ingestion_Failed_To_Start_Error Info:{AcceleratorEvent} {CX} AnalyticsIngesterTask.exe with TransactionId 2545 failed to start processing, terminating. 
Diag: 
Type:System.Exception 
ST: Inner:None

The error code 0x800401F3 is a COM error referencing CO_E_CLASSSTRING and indicates a DLL used in the Analytics process was not correctly registered with Microsoft.NET during the installation or upgrade of the EV binaries. This may also occur if the Use the ECM API for item retrieval Configuration Setting has been disabled - see Related Articles below.

To resolve this issue:

1. Log onto the DA server as the Vault Service Account (VSA) and stop the Enterprise Vault Accelerator Manager Service (EVAMS) in the Services management console.

2. Open an administrative/elevated command prompt on the DA server and navigate to the Enterprise Vault installation directory (default path is C:\Program Files (x86)\Enterprise Vault). To open an administrative/elevated command prompt, click Start, right-click Command Prompt, and then click Run as administrator.

3. Confirm the file KVS.EnterpriseVault.Common.dll exists in the folder (if the file does not exist, search for the file and change to the drive\directory in which it resides).

4. Execute the following commands and verify they complete successfully:

4.1. Register the KVS.EnterpriseVault.Common.dll file with the 32-bit .NET Framework by executing the following command using the correct path for the DLL file:

"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe" /tlb /codebase /verbose "C:\Program Files (x86)\Enterprise Vault\KVS.EnterpriseVault.Common.dll"

4.2. Register the KVS.EnterpriseVault.Common.dll file with the 64-bit .NET Framework by executing the following command using the correct path for the DLL file:

"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe" /tlb /codebase /verbose "C:\Program Files (x86)\Enterprise Vault\KVS.EnterpriseVault.Common.dll"

5. Start the EVAMS and attempt to enable Analytics.

Note - If attempting to enable Analytics fails with error referencing File '\SQLData\AnalyticsCaseFile_Case_X.ndf' cannot be reused until after the next BACKUP LOG operation, see the Related Articles below for the solution.