Error Message

Error in a DTrace log of the AcceleratorService process (example from DA):

[1234]    (AcceleratorService)    <5678>    EV-L    {EVSqlBase.ShouldExcludeSqlException} Error 'Only a member of the sysadmin server role can add a job for a different owner with @owner_login_name.' is not transient. 'EVSqlDataAdapter: Select: EVSqlCommand: DB: server=;Initial Catalog=;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Discovery Accelerator - Command: [usp_Schedule_Sel] | . . .

Errors in the EV Event Logs on the Accelerator server:

Log Name: Veritas Enterprise Vault
Source: Accelerator Service Processor
Event ID: 147
Level: Error
Description: APP AS - Customer ID: X - An error occured updating a schedule. 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.EVSqlDataAdapter.Update(DataTable dataTable)
at KVS.Accelerator.Common.Schedule.UpdateDS(ScheduleDS DS)
V-437-147

Log Name: Veritas Enterprise Vault
Source: Accelerator Service Processor
Event ID: 147
Level: Error
Description:
APP AS - Customer ID: 1 - An error occured updating a schedule. System.Data.SqlClient.SqlException (0x80131904): The specified @schedule_id ('X') does not exist.
ERROR_usp_Schedule_upd
  at Symantec.EnterpriseVault.DatabaseAccess.EVSqlBase.Do[T](Func`1 action)
  at Symantec.EnterpriseVault.DatabaseAccess.EVSqlDataAdapter.Update(DataTable dataTable)
  at KVS.Accelerator.Common.Schedule.UpdateDS(ScheduleDS DS)
V-437-147

Editing or creating Search Schedules requires the Vault Service Account (VSA) to have sysadmin rights on the SQL server. In the event local security requirements prevent the continued assignment of the SQL sysadmin role to the VSA, sufficient permissions need to be provided to the VSA to allow creating and editing Search Schedules.

In order for the VSA to create and edit Search Schedules, the following are required:

- Access to the msdb system database.
- Select permissions on the msdb tables: sysjobhistory, sysjobs, sysjobschedules, sysjobservers, sysjobsteps, sysschedules.
- Execute permissions on the msdb stored procedures: sp_add_category, sp_add_job, sp_add_jobschedule, sp_add_jobserver, sp_add_jobstep.
- The database role SQLAgentUserRole.

Here are the steps to grant VSA access to the msdb system database:

1. Start SQL Server Management Studio on the SQL Server computer with an account having rights to edit permissions.
2. Browse to Databases | System Databases | msdb | Security | Users.
3. Right-click Users | New User.
4. In the User name box, enter the user name of the VSA | In the Login name box, enter the domain and the user name of the VSA in the form domain\user_name | Click OK.
5. Right-click the newly created user, and then click Properties | Select the Securables page.
6. Add the following msdb tables to the list of securables and grant the Select permission to the VSA: sysjobhistory, sysjobs, sysjobschedules, sysjobservers, sysjobsteps, sysschedules.
7. Add the following msdb stored procedures to the list of securables, and then grant the Execute permission to the VSA: sp_add_category, sp_add_job, sp_add_jobschedule, sp_add_jobserver, sp_add_jobstep.
8. Browse to Databases | System Databases | msdb | Security | Roles | Database Roles.
9. Right-click SQLAgentUserRole | Properties.
10. On the General page, click Add, and then select the VSA that was just created.

Once the above steps are completed, log in to the Accelerator Client with an account having permissions to edit the Application Settings, usually the VSA and test creating/editing a Search Schedule. If the issue persists:

1. Log in to the Accelerator Client with an account having rights to edit the Configuration Settings, such as the Vault Service Account (VSA).
2. Navigate to Configuration | Settings | Security.
3. Find the setting Use SQL Server SysAdmin Server Role for Schedules and de-select the check mark under the Value column.
4. Click outside the Value column, then click on Save to save the change. Acknowledge any prompts to restart Remoteing, Background Tasks or the Enterprise Vault Accelerator Manager Service.
5. Close the Accelerator Client and restart the Enterprise Vault Accelerator Manager Service from the Windows Services management console.

For more detailed SQL security settings in CA and DA, review the Accelerator Installation Guide for the specific version in use. These guides may found in the Enterprise Vault Product Documentation. Additionally, refer to article Using SQL Database Roles in Enterprise Vault, Compliance Accelerator and Discovery Accelerator for using SQL roles. Note that these instructions must be followed to the letter.