SQL 2008 Agent - run batch file not working

Question

Hello,
I am having some strange issues with a batch file running out of SQL agent I'm hoping I can get some help with.
The batch file's purpose is to send some log files to a SFTP server.
The job has been working great for the past 3 weeks, however this morning it stopped working. The job doesn't error out, however the entire job completes in 00:00:00 duration and I'm given the following message 
Date 4/7/2014 3:38:00 PM
Log Job History (***Log Transfer)
Step ID 1
Server *******
Job Name **** Log Transfer
Step Name run batch
Duration 00:00:00
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Executed as user: USERNAMERemoved . The step did not generate any output.  Process Exit Code 0.  The step succeeded.
The batch file looks like 
echo  *********************************
echo  ** JOB EXECUTED %date% %time%  ** 
if %errorlevel% neq 0 exit /b
C:
cd "C:\Program Files (x86)\WinSCP"
winscp /console /script=G:\Batch\LogTransfer.txt
call G:\Batch\LogTransfer2.bat
echo ** COMPLETED %date% %time%  ** 
echo  *********************************
I have numerous other batch jobs running on this server, no other job has had this issue.  I have deleted and recreated both the job step and the entire job.  I have recreated the batch files from scratch.   I have also deleted the entire
contents of the batch file and just simply put in echo **** and still received the message so I'm near positive it has nothing to do with the actual batch file.  
I have reset SQL Agent, as well rechecked that the SQL Agent account has run batch rights granted to it.
I moved the batch files to another folder, and they worked for about 4 runs until the same issue happened!!!
The job does execute 100% perfect if I run it manually via batch or if I kick it off starting the job out of SQL.
I am out of options here, does anyone have any ideas that could help me out?
Thanks,
Ryan

Answer 1

Hello,
Try to edit the step, and on the Advanced page of that step try to configure the job to create a log on the location you specify (Output file). Try to run the step again and examine the log created.
Could you try to change the owner of the job to “sa” or to your Windows account? Maybe the SQL Server Agent account does not have access
to the following folders:
G:\Batch\
C:\Program Files (x86)\WinSCP
Alternatively, you can try to create a proxy account.
http://technet.microsoft.com/en-US/library/ms190698(v=SQL.105).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com