We moved the process from a virtual machine to a standalone machine and the problem appears to have gone away. I wonder if anyone else has seen this behavior...

Occasionally when we run the package manually we get the same result, but most of the time it runs without an issue. Doesn't seem to be related to any...

I've seen this problem too, but can't find the root cause. Anyone out there have any ideas or why a package appears to start but never really executes?