- Event Log entries seen for Search issues:
Log Name: Veritas Enterprise Vault
Source: Accelerator Service Processor
Event ID: 1033
Level: Error
Description:
APP AS - Customer ID: X - An error occurred getting the policy list. System.Exception: Configuration Key [1205] 'GetAllPolicyNames' does not exist - (384 configuration keys).
at KVS.Accelerator.Common.ConfigFileAccess.GetKeyValue(ConfigKeys key)
at KVS.Accelerator.Common.ConfigFileAccess.GetBooleanValue(ConfigKeys key)
at KVS.Accelerator.Application.Policies.GetAllVisiblePolicies(Int32 CaseID, Boolean bShowOnlyPoliciesWithItems)
Inner:None
V-437-1033
Log Name: Veritas Enterprise Vault
Source: Accelerator Service Processor
Event ID: 41933
Level: Error
Description:
APP AS - Customer ID: X - An error occurred getting the policy list. System.Exception: Configuration Key [1205] 'GetAllPolicyNames' does not exist - (384 configuration keys).
at KVS.Accelerator.Common.ConfigFileAccess.GetKeyValue(ConfigKeys key)
at KVS.Accelerator.Common.ConfigFileAccess.GetBooleanValue(ConfigKeys key)
at KVS.Accelerator.Application.Policies.GetAllVisiblePolicies(Int32 CaseID, Boolean bShowOnlyPoliciesWithItems)
Reason: Configuration Key [1205] 'GetAllPolicyNames' does not exist - (384 configuration keys0
STACK: at KVS.Accelerator.Common.ConfigFileAccess.GetKeyValue(ConfigKeys key)
at KVS.Accelerator.Common.ConfigFileAccess.GetBooleanValue(ConfigKeys key)
at KVS.Accelerator.Application.Policies.GetAllVisiblePolicies(Int32 CaseID, Boolean bShowOnlyPoliciesWithItems)
V-437-41933
- Event Log entries seen for Export issues:
Log Name: Veritas Enterprise Vault
Source: Accelerator Service Processor
Event ID: 241
Level: Error
Description:
APP AS - Customer ID: X - An error occurred when saving a Production. System.Data.SqlClient.SqlException (0x80131904): Procedure or function usp_Production_add has too many arguments specified.
at KVS.Accelerator.Production.Productions.UpdateDS(Int32 nCaseID, ProductionDS aDS)
at KVS.Accelerator.Production.ProductionRun.NewProductionRun(ProductionDS aProductionDS)
ClientConnectionId:52ef89c9-f02c-49ab-a383-6d9f9d184628
Error Number:8144,State:2,Class:16
V-437-241
Log Name: Veritas Enterprise Vault
Source: Accelerator Service Processor
Event ID: 245
Level: Error
Description:
APP AS - Customer ID: X - Error updating a Production. System.Data.SqlClient.SqlException (0x80131904): Procedure or function usp_Production_add has too many arguments specified.
at Symantec.EnterpriseVault.DatabaseAccess.EVSqlBase.Do[T](Func`1 action)
at Symantec.EnterpriseVault.DatabaseAccess.EVSqlDataAdapter.Update(DataSet dataSet, String srcTable)
at KVS.Accelerator.Production.Productions.UpdateDS(Int32 nCaseID, ProductionDS aDS)
ClientConnectionId:52ef89c9-f02c-49ab-a383-6d9f9d184628
Error Number:8144,State:2,Class:16
V-437-245
- DTrace entries seen for Export issues:
[1234] (AcceleratorService) <1234> EV-L {EVSqlBase.ShouldExcludeSqlException} Error 'Procedure or function usp_Production_add has too many arguments specified.' is not transient. 'EVSqlDataAdapter:
Select: EVSqlCommand: DB: server=SQLServer;Initial Catalog=CustomerDatabase;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery/Compliance Accelerator - Command: [usp_Productions_sel] |
Update: EVSqlCommand: DB: server=SQLServer;Initial Catalog=CustomerDatabase;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery/Compliance Accelerator - Command: [usp_Production_Upd] |
Delete: EVSqlCommand: DB: server=SQLServer;Initial Catalog=CustomerDatabase;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery/Compliance Accelerator - Command: [usp_Production_del]
Insert: EVSqlCommand: DB: server=SQLServer;Initial Catalog=CustomerDatabase;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery/Compliance Accelerator - Command: [usp_Production_add]' will not be retried
[1234] (AcceleratorService) <1234> EV-L {EVSqlBase.ShouldRetry} Error 'Procedure or function usp_Production_add has too many arguments specified.' is excluded. 'EVSqlDataAdapter:
Select: EVSqlCommand: DB: server=SQLServer;Initial Catalog=CustomerDatabase;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery/Compliance Accelerator - Command: [usp_Productions_sel] |
Update: EVSqlCommand: DB: server=SQLServer;Initial Catalog=CustomerDatabase;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery/Compliance Accelerator - Command: [usp_Production_Upd] |
Delete: EVSqlCommand: DB: server=SQLServer;Initial Catalog=CustomerDatabase;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery/Compliance Accelerator - Command: [usp_Production_del]
Insert: EVSqlCommand: DB: server=SQLServer;Initial Catalog=CustomerDatabase;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery/Compliance Accelerator - Command: [usp_Production_add]' will not be retried
[1234] (AcceleratorService) <1234> EV-H {EVSqlBase.LogFailureAndThrow} Failed to execute 'EVSqlDataAdapter:
Select: EVSqlCommand: DB: server=SQLServer;Initial Catalog=CustomerDatabase;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery/Compliance Accelerator - Command: [usp_Productions_sel] |
Update: EVSqlCommand: DB: server=SQLServer;Initial Catalog=CustomerDatabase;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery/Compliance Accelerator - Command: [usp_Production_Upd] |
Delete: EVSqlCommand: DB: server=SQLServer;Initial Catalog=CustomerDatabase;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery/Compliance Accelerator - Command: [usp_Production_del]
Insert: EVSqlCommand: DB: server=SQLServer;Initial Catalog=CustomerDatabase;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery/Compliance Accelerator - Command: [usp_Production_add]' - This command was not retried - Error Error Code: 8144 / 80131904 - Severity 16 - Procedure or function usp_Production_add has too many arguments specified.
[1234] (AcceleratorService) <1234> EV-H {-} Exception: Error Production_UpdateError Info:{AcceleratorEvent} {CX} Error updating a Production.
System.Data.SqlClient.SqlException (0x80131904): Procedure or function usp_Production_add has too many arguments specified.|
at Symantec.EnterpriseVault.DatabaseAccess.EVSqlBase.Do[T](Func`1 action)|
at Symantec.EnterpriseVault.DatabaseAccess.EVSqlDataAdapter.Update(DataSet dataSet, String srcTable)|
at KVS.Accelerator.Production.Productions.UpdateDS(Int32 nCaseID, ProductionDS aDS)|
ClientConnectionId:. . .|
Error Number:8144,State:2,Class:16 Diag: Type:System.Exception ST: Inner:None
[1234] (AcceleratorService) <1234> EV-H {-} Exception: Error Production_SaveError Info:{AcceleratorEvent} {CX} An error occurred when saving a Production.
System.Data.SqlClient.SqlException (0x80131904): Procedure or function usp_Production_add has too many arguments specified.|
at KVS.Accelerator.Production.Productions.UpdateDS(Int32 nCaseID, ProductionDS aDS)|
at KVS.Accelerator.Production.ProductionRun.NewProductionRun(ProductionDS aProductionDS)|
ClientConnectionId:. . .|
Error Number:8144,State:2,Class:16 Diag: Type:System.Exception ST: Inner:None
[1234] (AcceleratorService) <1234> EV-H {-} Exception: Procedure or function usp_Production_add has too many arguments specified.
Info:{RBO_ExportProduction} {CX} Diag:Num:8144 State:2 Sev:16 Svr:SQLServer Proc:usp_Production_add Line:0 Type:System.Data.SqlClient.SqlException ST:
at KVS.Accelerator.Production.ProductionRun.NewProductionRun(ProductionDS aProductionDS)|
at KVS.Accelerator.RBO.RBO_ExportProduction.Add(ProductionDS NewOne) Inner:None
- Event Log entries seen for Case creation issues:
Log Name: Veritas Enterprise Vault
Source: Accelerator Service Processor
Event ID: 102
Level: Error
Description:
APP AS - Customer ID: X - An error occured updating cases. System.Data.SqlClient.SqlException (0x80131904): @ModifiedByID is not a parameter for procedure usp_Case_Add.
at Symantec.EnterpriseVault.DatabaseAccess.EVSqlBase.Do[T](Func`1 action)
at Symantec.EnterpriseVault.DatabaseAccess.EVSqlDataAdapter.Update(DataTable dataTable)
at KVS.Accelerator.Case.Case.UpdateDS(CaseDS DS)
ClientConnectionId:426f9770-9794-4cd4-9b4c-53b084e6f085
Error Number:8145,State:1,Class:16
V-437-102
- DTrace entries seen for Case creation issues:
[1234] (AcceleratorService) <1234> EV-L {EVSqlBase.ShouldExcludeSqlException} Error '@ModifiedByID is not a parameter for procedure usp_Case_Add.' is not transient. 'EVSqlDataAdapter:
Select: EVSqlCommand: DB: server=EVAULTDB;Initial Catalog=DodgeCountyDA;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery Accelerator - Command: [usp_Case_Sel] |
Update: EVSqlCommand: DB: server=EVAULTDB;Initial Catalog=DodgeCountyDA;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery Accelerator - Command: [usp_Case_Upd] |
Delete: EVSqlCommand: DB: server=EVAULTDB;Initial Catalog=DodgeCountyDA;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery Accelerator - Command: [usp_Case_Del]
Insert: EVSqlCommand: DB: server=EVAULTDB;Initial Catalog=DodgeCountyDA;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery Accelerator - Command: [usp_Case_Add]' will not be retried
[1234] (AcceleratorService) <1234> EV-L {EVSqlBase.ShouldRetry} Error '@ModifiedByID is not a parameter for procedure usp_Case_Add.' is excluded. 'EVSqlDataAdapter:
Select: EVSqlCommand: DB: server=EVAULTDB;Initial Catalog=DodgeCountyDA;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery Accelerator - Command: [usp_Case_Sel] |
Update: EVSqlCommand: DB: server=EVAULTDB;Initial Catalog=DodgeCountyDA;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery Accelerator - Command: [usp_Case_Upd] |
Delete: EVSqlCommand: DB: server=EVAULTDB;Initial Catalog=DodgeCountyDA;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery Accelerator - Command: [usp_Case_Del]
Insert: EVSqlCommand: DB: server=EVAULTDB;Initial Catalog=DodgeCountyDA;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery Accelerator - Command: [usp_Case_Add]' will not be retried
[1234] (AcceleratorService) <1234> EV-H {EVSqlBase.LogFailureAndThrow} Failed to execute 'EVSqlDataAdapter:
Select: EVSqlCommand: DB: server=EVAULTDB;Initial Catalog=DodgeCountyDA;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery Accelerator - Command: [usp_Case_Sel] |
Update: EVSqlCommand: DB: server=EVAULTDB;Initial Catalog=DodgeCountyDA;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery Accelerator - Command: [usp_Case_Upd] |
Delete: EVSqlCommand: DB: server=EVAULTDB;Initial Catalog=DodgeCountyDA;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery Accelerator - Command: [usp_Case_Del]
Insert: EVSqlCommand: DB: server=EVAULTDB;Initial Catalog=DodgeCountyDA;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery Accelerator - Command: [usp_Case_Add]' - This command was not retried - Error Error Code: 8145 / 80131904 - Severity 16 - @ModifiedByID is not a parameter for procedure usp_Case_Add.
[1234] (AcceleratorService) <1234> EV-H {-} Exception: Error Case_Case_Updating Info:{AcceleratorEvent} {C1} An error occured updating cases. System.Data.SqlClient.SqlException (0x80131904): @ModifiedByID is not a parameter for procedure usp_Case_Add.
| at Symantec.EnterpriseVault.DatabaseAccess.EVSqlBase.Do[T](Func`1 action)
| at Symantec.EnterpriseVault.DatabaseAccess.EVSqlDataAdapter.Update(DataTable dataTable)
| at KVS.Accelerator.Case.Case.UpdateDS(CaseDS DS)
|ClientConnectionId:670929eb-4b81-4bdd-84d2-89af9c1f4788
|Error Number:8145,State:1,Class:16 Diag: Type:System.Exception ST: Inner:None
CA or DA release updates cannot be installed by themselves. They require the base version be installed first. For example, attempting to install 12.5.1 by itself without first installing 12.5.0 will return the following errors:
- When running setup.exe:
An error occurred installing the package. Windows installer returned '1642'.
- When running the ...Accelerator Server.msp:
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.
Part of the installation process is to connect to the EVBAAdmin administration website and upgrade the Configuration and Customer databases. This should be done when upgrading to the base version, e.g. 12.5.0, and when upgrading to the release update version, e.g. 12.5.1. This is called a 'stepped' upgrade.
This issue is caused by upgrading from an Accelerator version prior to 12.5.0 directly to a release upgrade version without upgrading the databases to the base version first. For example, upgrading the databases to 12.5.1 without first upgrading them to 12.5.0. This 'non-stepped' upgrade causes certain processes that upgrade the databases not to run, thus resulting in a missing Configuration Setting and missing stored procedure updates.
For example, DA is currently at 12.4.0 and needs to be upgraded to 12.5.1. The correct upgrade sequence would be to upgrade the databases to 12.5.0 first, then upgrade the databases to 12.5.1. The example steps below will only focus on the DA application and will omit any EV binaries upgrade steps as the EV binaries do not have an effect in this issue. In reality and in practice, the EV binaries should be upgraded to match the version and release update on the EV servers. Additionally, the steps presume the existing Configuration and Customer databases have been backed up. The correct 'stepped' sequence to upgrade DA is as follows:
1. Install DA Server 12.5.0 to upgrade the DA server to 12.5.0.
2. When the DA Server 12.5.0 installation is complete, access the EVBAAdmin administration website and follow the prompts to upgrade the Configuration database. At the "The update is complete. Restart the Accelerator Manager Service and then click 'OK'" prompt, restart the EV Accelerator Manager Service before clicking on the OK button.
3. Once in the EVBAAdmin administration website, right-click each Customer, click on Properties, then click on the applicable Upgrade or Update button at the bottom of the Properties window to upgrade the Customer to 12.5.0.
4. Click on the Customer and monitor the Current Status pane until the upgrade has completed and the Customer's tasks shows Running.
5. Repeat for any remaining Customers.
6. After all Customers have been upgraded to 12.5.0, then install DA Server 12.5.1 to upgrade the DA server to 12.5.1.
7. When the DA Server 12.5.1 installation is complete, access the EVBAAdmin administration website and follow the prompts to upgrade the Configuration database. At the "The update is complete. Restart the Accelerator Manager Service and then click 'OK'" prompt, restart the EV Accelerator Manager Service before clicking on the OK button.
8. Once in the EVBAAdmin administration website, right-click each Customer, click on Properties, then click on the applicable Upgrade or Update button at the bottom of the Properties window to upgrade the Customer to 12.5.1.
9. Click on the Customer and monitor the Current Status pane until the upgrade has completed and the Customer's tasks shows Running.
10. Repeat for any remaining Customers.
An example of an incorrect, 'non-stepped' sequence might look like this:
1. Install DA Server 12.5.0 to upgrade the DA server to 12.5.0.
2. When the DA Server 12.5.0 installation is complete, close the installer or close the browser for the EVBAAdmin administration website.
3. Install DA Server 12.5.1 to upgrade the DA server to 12.5.1.
4. When the DA Server 12.5.1 installation is complete, access the EVBAAdmin administration website and follow the prompts to upgrade the Configuration database. At the "The update is complete. Restart the Accelerator Manager Service and then click 'OK'" prompt, restart the EV Accelerator Manager Service before clicking on the OK button.
5. Once in the EVBAAdmin administration website, right-click each Customer, click on Properties, then click on the applicable Upgrade or Update button at the bottom of the Properties window to upgrade the Customer to 12.5.1.
6. Click on the Customer and monitor the Current Status pane until the upgrade has completed and the Customer's tasks shows Running.
7. Repeat for any remaining Customers.
The differences in these sequences are clear - the 'stepped' database upgrades to 12.5.0 are missing.
Please contact technical support for assistance with this issue.
'An error occurred. Contact your administrator for help'. Once this condition is seen, cancelling the New Search causes the Discard option to loop until the Client is closed with acknowledging the Abandon Changes option.
Attempting to configure and save a new Export causes the New Export pane to clear to a white pane. Once this condition is seen, cancelling the New Export may require the Client to be is closed.
Review of the EV Event Logs on the Accelerator server may show errors as listed below. Running a DTrace on the Accelerator server on the AcceleratorService process may show entries similar to the Event Log entries below.
Other symptoms can include:
- Unable to preview items in the Review Set.
Selecting an item for preview after clearing the filter facets and applying the applicable filter facets results in a blank Item List pane and the message 'No item selected' in the Reading pane, even when the filters show there are items to be previewed (indicated by a number in parenthesis next to the filter).
- Cannot create a new Case