There was an issue with the linked server that had caused this error. The user is fully permissioned as sa so no security issue.

Am now able to remotely execute...

Kerberos authentication is now working - verified by querying sys.dm_exec_connections

EXEC [LinkedServer].[SSISDB].[catalog].[create_execution] @package_name=N'Package.dtsx', @execution_id=@execution_id OUTPUT, @folder_name=N'Test', @project_name=N'ETLMaster', @use32bitruntime=False, @reference_id=Null

Select @execution_id

DECLARE @var0 smallint = 1

EXEC [LinkedServer].[SSISDB].[catalog].[set_execution_parameter_value] @execution_id, @object_type=50, @parameter_name=N'LOGGING_LEVEL', @parameter_value=@var0

EXEC [LinkedServer].[SSISDB].[catalog].[start_execution]...

Still trying to get the network guys engaged to sort add the SPN entries.

In the meantime could someone pls confirm whether the double hop issue can be resolved using SQL...

Hi Journeyman, Both Server A and B have enabled 'trust this computer for delegation to any service'

and the domain account enabled as 'Account is trusted for delegation'

How else can I...