Error in the EVBAAdmin Customer Info section:
The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).
Errors seen in a DTrace of the AcceleratorManager process:
[1234] (AcceleratorManager)
Error 'The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).' is not transient.
'EVSqlCommand: DB: server=
Command:
...
|' will not be retried
[1234] (AcceleratorManager)
Error 'The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).' is excluded.
'EVSqlCommand: DB: server=
Command:
...
|' will not be retried
[1234] (AcceleratorManager)
Failed to execute
'EVSqlCommand: DB: server=
Command:
...
|' - This command was not retried - Error Error Code: 14234 / 80131904 - Severity 16 - The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).
[1234] (AcceleratorManager)
Exception:
Error Application_InstallExecutingScript
Info:
{AcceleratorEvent} {C} Error Executing : C:\Program Files (x86)\Enterprise Vault Business Accelerator\....sql
|Line: X
|Failed to Execute the following command:
...
|. System.Data.SqlClient.SqlException (0x80131904): The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).
| at Symantec.EnterpriseVault.DatabaseAccess.EVSqlBase.Do[T](Func`1 action)
| at Symantec.EnterpriseVault.DatabaseAccess.EVSqlCommand.ExecuteNonQuery()
| at KVS.Accelerator.Application.Install.RunScript(String ScriptName, EVSqlCommand CMD, Int32 CustomerID)
|ClientConnectionId:f9b28dcd-9333-434c-bfdc-d7d017f113f6
|Error Number:14234,State:1,Class:16 Diag: Type:System.Exception ST: Inner:None
[1234] (AcceleratorManager)
Exception:
Error Application_InstallFailedUpdateDatabase
Info:{AcceleratorEvent} {C} Failed to update database. System.Data.SqlClient.SqlException (0x80131904): The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).
| at Symantec.EnterpriseVault.DatabaseAccess.EVSqlBase.Do[T](Func`1 action)
| at Symantec.EnterpriseVault.DatabaseAccess.EVSqlCommand.ExecuteNonQuery()
| at KVS.Accelerator.Application.Install.RunScript(String ScriptName, EVSqlCommand CMD, Int32 CustomerID)
| at KVS.Accelerator.Application.Install.UpdateDatabase(CustomerRow theCustomerRow, String configDSN, ProductType productType)
|ClientConnectionId:f9b28dcd-9333-434c-bfdc-d7d017f113f6
|Error Number:14234,State:1,Class:16 Diag: Type:System.Exception ST: Inner:None
[1234] (AcceleratorManager)
|Install Thread - worker thread (0)
|Customer ID: X
|Number of tries: 1
|Cause: The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]). Diag: Type:System.Exception ST: Inner:None
The SQL SysAdmin account's default name is sa. Renaming the SQL SysAdmin account is a guideline recommended by some security best practices. The issue is caused when the SQL SysAdmin account is renamed from sa to a different name and the upgrade process attempts to upgrade certain SQL stored procedures that are hard-coded to use the default SysAdmin name.
The issue was first discovered in CA version 15.2.0 and may be present in other versions up to any fix version(s) listed below.
A workaround is to rename the SQL SysAdmin account back to sa temporarily, perform the Customer database upgrades, then rename the SysAdmin back to its previous name. If this cannot be performed due to business restrictions, please contact Technical Support for assistance.
There are no plans to address this issue by way of a patch or hotfix in earlier versions of the software at the present time. However, the issue has been addressed in the revision of the product specified at the end of this article.
Please contact your Veritas Sales representative or the Veritas Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue.
This issue is fixed in the following release(s), available in the Download Center at https://www.veritas.com/support:
- Enterprise Vault 15.2.2