Ok, so what the heck does that error mean? I took code working in SSMS and pasted it into the job step command window. I then ran the job and generated the error in the title of this post. After pulling it out of the job step window and pasting it back into SSMS…it ran w/o error! I then pulled out various white spaces (blank lines). I then pasted this back into the job step window and the job then ran. Go Figure!