Reputation: 1
Currently, the SSIS 2012 package is deployed in MSDB on SQL Server 2012, and it's working fine.
We have migrated the same packages in MSDB to SQL Server 2016 through batch utility, after created the SQL Server job & mapping the "Master" package from MSDB (SQL Server 2016) and executing the same job, it executes successfully within 2 minutes, but package is not triggered.
Please help me resolve this issue.
Upvotes: 0
Views: 118