Not being able to run the job at all still sounds to me as if the user running the job step was unable to decrypt the package, this was also the behavior I was experiencing. Are you also moving packages from different environments? If so, Perhaps you used DontSaveSensitive when ...
Not being able to run the job at all still sounds to me as if the user running the job step was unable to decrypt the package, this was also the behavior I was experiencing. Are you also moving packages from different environments? If so, Perhaps you used DontSaveSensitive when ...
Not being able to run the job at all still sounds to me as if the user running the job step was unable to decrypt the package, this was also the behavior I was experiencing. Are you also moving packages from different environments? If so, Perhaps you used DontSaveSensitive when sa...