The problem has something to do with permissions on the underlying server and not SSIS or the MSDB. We had the same problem. Temporarily adding the user's AD account to the local administrators group fixed this for us. Adding their AD account to PowerUsers or Users did not; however, I am certain that we could have found what was missing in the Local Security Policy to make it happen.