Using SSIS package but not able to execute SSIS package

[Douglas Darbyshire]

We have a on going problem be able to connect to Sql Server using a Domain Userid   so have to create a local User in SQL Server that is a sysadmin.  I can run this with no issue
PCK.CUSTOM_EXECUTE_SSIS_PACKAGES.PUB.ACTION.GET_SSIS_ENVIRONMENT_INFO
but when I try and run 
PCK.CUSTOM_EXECUTE_SSIS_PACKAGES.PUB.ACTION.EXECUTE_SSIS_PACKAGES  we get the following:

2018-01-18 09:01:03 - U02000005 Job 'PKG.JS.SQL.EXEC.SSIS.PARAM.PACKAGE' with RunID '1462506' started. 2018-01-18 09:01:03 - U02012001 Successfully established connection to 'ndstella:1433/SSISDB' with user 'AUTOMIC'. 2018-01-18 09:01:03             Microsoft SQL Server 2018-01-18 09:01:03             11.00.3513 2018-01-18 09:01:03 - U02012014 JDBC Driver version: 4.0.2206.100 2018-01-18 09:01:03             set implicit_transactions off; 2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             Declare @execution_id bigint, @environment_id bigint, @etl_status varchar(100) 2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             EXEC SSISDB.catalog.create_execution 2018-01-18 09:01:03             2018-01-18 09:01:03               @package_name=N'TestAutomic' 2018-01-18 09:01:03             2018-01-18 09:01:03               , @execution_id=@execution_id OUTPUT 2018-01-18 09:01:03             2018-01-18 09:01:03               , @folder_name=N'TestAutomic' 2018-01-18 09:01:03             2018-01-18 09:01:03               , @project_name=N'TestAutomic' 2018-01-18 09:01:03             2018-01-18 09:01:03               , @use32bitruntime=False 2018-01-18 09:01:03             2018-01-18 09:01:03               , @reference_id=NULL 2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             EXEC SSISDB.catalog.set_execution_parameter_value 2018-01-18 09:01:03             2018-01-18 09:01:03               @execution_id 2018-01-18 09:01:03             2018-01-18 09:01:03               ,  @object_type=50 2018-01-18 09:01:03             2018-01-18 09:01:03               , @parameter_name=N'SYNCHRONIZED' 2018-01-18 09:01:03             2018-01-18 09:01:03               , @parameter_value=1 2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             EXEC SSISDB.catalog.start_execution @execution_id; 2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             with execution_status as 2018-01-18 09:01:03             2018-01-18 09:01:03             ( 2018-01-18 09:01:03             2018-01-18 09:01:03             select 'Created' as status, 1 as status_code 2018-01-18 09:01:03             2018-01-18 09:01:03             union all 2018-01-18 09:01:03             2018-01-18 09:01:03             select 'Running' as status, 2 as status_code 2018-01-18 09:01:03             2018-01-18 09:01:03             union all 2018-01-18 09:01:03             2018-01-18 09:01:03             select 'Canceled' as status, 3 as status_code 2018-01-18 09:01:03             2018-01-18 09:01:03             union all 2018-01-18 09:01:03             2018-01-18 09:01:03             select 'Failed' as status, 4 as status_code 2018-01-18 09:01:03             2018-01-18 09:01:03             union all 2018-01-18 09:01:03             2018-01-18 09:01:03             select 'Pending' as status, 5 as status_code 2018-01-18 09:01:03             2018-01-18 09:01:03             union all 2018-01-18 09:01:03             2018-01-18 09:01:03             select 'Ended unexpectedly' as status, 6 as status_code 2018-01-18 09:01:03             2018-01-18 09:01:03             union all 2018-01-18 09:01:03             2018-01-18 09:01:03             select 'Succeeded' as status, 7 as status_code 2018-01-18 09:01:03             2018-01-18 09:01:03             union all 2018-01-18 09:01:03             2018-01-18 09:01:03             select 'Stopping' as status, 8 as status_code 2018-01-18 09:01:03             2018-01-18 09:01:03             union all 2018-01-18 09:01:03             2018-01-18 09:01:03             select 'Completed' as status, 9 as status_code 2018-01-18 09:01:03             2018-01-18 09:01:03             ) 2018-01-18 09:01:03             2018-01-18 09:01:03             SELECT 2018-01-18 09:01:03             2018-01-18 09:01:03               @etl_status = 'Status: ' + cast(e.Status as varchar(2)) + ' - ' + s.Status 2018-01-18 09:01:03             2018-01-18 09:01:03             FROM 2018-01-18 09:01:03             2018-01-18 09:01:03               SSISDB.catalog.executions e WITH (NOLOCK) 2018-01-18 09:01:03             2018-01-18 09:01:03             LEFT JOIN 2018-01-18 09:01:03             2018-01-18 09:01:03               execution_status s 2018-01-18 09:01:03             2018-01-18 09:01:03             on 2018-01-18 09:01:03             2018-01-18 09:01:03               e.status = s.status_code 2018-01-18 09:01:03             2018-01-18 09:01:03             WHERE 2018-01-18 09:01:03             2018-01-18 09:01:03               e.execution_id = @execution_id 2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             PRINT 'EXECUTION_ID:' + cast(@execution_id as varchar(10)) 2018-01-18 09:01:03             2018-01-18 09:01:03             PRINT coalesce(@etl_status, 'Unknown status') 2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             2018-01-18 09:01:03             IF coalesce(@etl_status, 'Unknown status') <> 'Status: 7 - Succeeded' 2018-01-18 09:01:03             2018-01-18 09:01:03             BEGIN 2018-01-18 09:01:03             2018-01-18 09:01:03             SELECT 2018-01-18 09:01:03             2018-01-18 09:01:03               e.execution_id, e.environment_name + '\' + e.folder_name + '\' + e.project_name + '\' + e.package_name as Package  , m.Package_Path , m.Message 2018-01-18 09:01:03             2018-01-18 09:01:03             FROM 2018-01-18 09:01:03             2018-01-18 09:01:03               SSISDB.catalog.executions e WITH (NOLOCK) 2018-01-18 09:01:03             2018-01-18 09:01:03             LEFT JOIN 2018-01-18 09:01:03             2018-01-18 09:01:03               SSISDB.catalog.operations o WITH (NOLOCK) 2018-01-18 09:01:03             2018-01-18 09:01:03             ON 2018-01-18 09:01:03             2018-01-18 09:01:03               e.process_id = o.process_id 2018-01-18 09:01:03             2018-01-18 09:01:03             LEFT JOIN 2018-01-18 09:01:03             2018-01-18 09:01:03               SSISDB.catalog.event_messages m WITH (NOLOCK) 2018-01-18 09:01:03             2018-01-18 09:01:03             ON 2018-01-18 09:01:03             2018-01-18 09:01:03               o.operation_id = m.operation_id 2018-01-18 09:01:03             2018-01-18 09:01:03             WHERE 2018-01-18 09:01:03             2018-01-18 09:01:03               e.execution_id = @execution_id 2018-01-18 09:01:03             2018-01-18 09:01:03               and m.Event_Name = 'OnError' 2018-01-18 09:01:03             2018-01-18 09:01:03             ORDER BY 2018-01-18 09:01:03             2018-01-18 09:01:03               m.event_message_id 2018-01-18 09:01:03             2018-01-18 09:01:03             END 2018-01-18 09:01:03             The operation cannot be started by an account that uses SQL Server Authentication. Start the operation with an account that uses Windows Authentication. 2018-01-18 09:01:03 - U02004025 Job-script execution was aborted. 2018-01-18 09:01:03 - U02012006 SQL Rollback executed

[Douglas Darbyshire]

I would love to just have a example of a working job that calls a SSIS with out using the prompt interface. I've never worked with SSIS before so an help would be appreciated 

[Pete Wirfs]

In our case, we assigned a service account to the startup properties of our SQLServer agent, and granted the necessary rights to that service account within our SSIS database.

Note that your messages say "Start the operation with an account that uses Windows Authentication".  This is important.

[Douglas Darbyshire]

I can not even get the svcAutomic which is our service account to pass the Connection test.  svcAutomic is a sysadmin at the highest level.  

[Michael Pirson]

What do you have set in the Agent INI for WindowsAuthentication= ? By default this is set to SQL server authentication 

[Douglas Darbyshire]

that was it worked once we set the WindowsAuthentication=1 in the ini on the Agent thanks for help