Hi @nononame2021 ,
Please check below:
Package Protection Level issue
- Check what the Protection Level is in your SSIS package.
- If the Protection Level is set to EncryptSensitiveWithUserKey, check the Creator in your SSIS package and compare it with the SQL Server Agent Service account.
- If the Creator is different from the SQL Server Agent Service account, then the sensitive data of the SSIS package could not be correctly decrypted, which will lead to the failure.
seems I run ssis manually while it causes error when deployed to environment
Please check the account permissions:
- The user account that is used to run the package under SQL Server Agent differs from the original package author.
- The user account does not have the required permissions to make connections or to access resources outside the SSIS package.
Details see here ssis-package-doesnt-run-when-called-job-step
Regards,
Zoe
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.