Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 981
  • Last Modified:

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.




0
wingkchan
Asked:
wingkchan
1 Solution
 
mfreudenCommented:
Try changing the useraccount that the SQL Agent process runs under to a Domain account with Local Admin access on the SQL server.
0
 
wingkchanAuthor Commented:
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.
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now