asked on

SQL Job that calls a windows batch file cannot start

Hi Experts,

I have just created a SQL job, which will do 3 steps:
- step 1, call a batch file to ftp a text file
- step 2, import that text file into a table by using a DTS
- sync the table to other servers

I created the step 1 batch file, run perfectly on command prompt. Then I created a SQL job, make the first step to run, but it couldn't go. The error return is:

The job failed. The Job was invoked by User sa. The last step to run was step 1 (Name of Step1). The job was requested to start at step 1 (Name of Step1).

When I show the step details, this is what I got:

Executed as user: Server\UserAccount. The step did not generate any output. Process Exit Code 1. The step failed.

I couldn't figure out what this job cannot be started, I made sure that the "owner" is sa, but still no help. Tried digging around the forums, some said that it might be permission issue... does anyone has an idea of why I couldn't get it start? thanks very much.

ASKER CERTIFIED SOLUTION

mfreuden

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

wingkchan

ASKER

Mfreuden, thanks for your advice. From the information I gathered on Google, I thought it would be the permission problem that cause the failure. I tried changing the "owner" under the Job's property page; tried assigning full control of the folder where the batch file existed... but then, at last, I realized that it was the batch's file's syntax error. Although the batch file completed flawlessly on Command Prompt, but I guess some minor synatx errors are capable of completing there... as when the batch file is ran by SQL Job calling, it refused. I found this out, but removing the "@echo off" line, and make a output of the job to a logfile... at then, I see that the batch hangs on a del statment. Before this, application log, job history didn't tell me this... so kinna stumped me there. thank you for your input.