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
In the interest of having an actual answer on this question and having just run into this very frustrating issue myself, the problem lies in package/environment parameters. When a package is run on a schedule, if required package parameters are not supplied, SSIS just... sits there. No errors are reported, but the package never actually starts.
Providing values for the required parameters will resolve this issue.