SSIS Package Stuck at “Created Execution” Status

Question

I recently deployed a update to one of my SSIS projects, and ever since the project has failed it\'s scheduled runs.

The SSIS package appears to be stuck at the \"Cr

Answer 1

I found that this can also happen if a new version of a package no longer has, previously configured, parameters. The only solution I found is to re-create the job-step after updating the Environment Variables' configuration. Somehow the Job seems to 'remember' the no longer existing parameters, and will not actually start the package because it thinks that some parameter-configurations are missing.