Ali,

You may want to verify the account used to run the job vs. the one you're using to run the batch file when it works. There could be a path issue there where your logged-in account has all of the necessary configurations and paths set properly but the service account doesn't. That would definitely cause issues. You may want to try piping the output of your batch to a text file when run as a job to see if you can catch more of the errors that way. I suspect that there's a setup or configuration issue when running as a job that would need to be resolved - either by logging in as the service account or some similar means.