Error Message

Event Log error:

Log Name:      Veritas Enterprise Vault
Source:        Accelerator Manager 
Event ID:      529
Task Category: None
Level:         Error
Keywords:      Classic
Description:
APP Analytics - AnalyticsIngesterTask was supplied an invalid command line. 
Usage:
Command line usage:     
To ingest items in Analytics:
AnalyticsIngesterTask Numeric_Transaction_Id Customer_Database_Server_Name Customer_Database_Name Case_Id Customer_Id
To view this message:
AnalyticsIngesterTask /help

V-437-529

DTrace log examples:

[1234]    (AcceleratorService64)        EV-L    {CommonStarterEV} {CX} Items are available for hotword analysis
[1234]    (AcceleratorService64)        EV-L    {CommonStarterEV} {CX} Spawning AnalyticsIngesterTask.exe for hotword analysis
...
[1234]    (AcceleratorService64)        EV-L    {-} {ProcessRunner} {CX} Spawning new process : \AnalyticsIngesterTask.exe
...
[2345]    (AnalyticsIngesterTask)    <234>    EV-M    {-} {AcceleratorEvent} {C} Event logging initialised for 'Accelerator Manager'. Event log name - Veritas Enterprise Vault
[2345]    (AnalyticsIngesterTask)    <234>    EV-H    {-} Exception: Error Ingester_Invalid_Command_Line Info:{AcceleratorEvent} {C} AnalyticsIngesterTask was supplied an invalid command line. |Usage:|Command line usage: |To ingest items in Analytics:|AnalyticsIngesterTask Numeric_Transaction_Id Customer_Database_Server_Name Customer_Database_Name Case_Id Customer_Id|To view this message:|AnalyticsIngesterTask /help Diag: Type:System.Exception ST: Inner:None

The issue is caused by the Customer database name containing spaces or the SQL server name that services the Accelerator databses containing a space. For example, a Customer database name of CA Customer 01 would have the issue, a Customer database name of CACustomer01 should not have the issue. Another example would be adding a space after the comma denoting the port in a SQL server name, such as SQLServer01, 1433.

The SQL server name combined with the database name is used by CA as the DSNConfiguration key value  in various configuration files. A space in this DSNConfiguration is not expected and is, therefore, not correctly parsed, resulting in the error.

The fix is to rename the affected Customer database name and or SQL server references to remove the spaces.

The steps to fix the Customer database include:

- Obtaining the current configuration information for the affected Customer.
- Backing up the databases.
- Renaming the Customer database to remove the spaces. Note this step will need to be performed by the onsite SQL team.
- Editing the Configuration database for the new name.

The steps to fix the SQL server name include:

- Verifying the SQL server name does not actually contain any spaces.
- Reviewing the configuration files and editing as needed.
- Reviewing the SQL server name for each Customer in the EVBAAdmin administration website and editing as needed.

Once these steps have been successfully implemented and the Customer database name and SQL server name no longer contain spaces, Hotword Analysis should function as expected.

Please contact technical support for assistance.