Thanks for the replies! 

Thanks.  I do have quite a bit of logging and error trapping but unfortunately when this error occurs, the job just stops and does not output anything to the log...

Here it is.  I've had it happen on a couple different .bat files though so I don't think it is an error in the .bat file as it runs successfully...

I too am experiencing this error in SQL 2000.  Anyone have any luck preventing it?  Thanks.