OK, this one had me going for quite a while! If you mis-spell the executable
name on a Job step of type "Command Line" , this error may result. I know
because I mis-spelled "DTSRun" and it took another set of eyes to spot the
offending letter! Of course, because other posters were suggesting "bad
hardware" and because I would have expected "executable not found" or
something similar, I focused on other things.

Way to go team!