This is the problem with cmdline batch files..... SQL Server cannot catch the exceptions from there....You need to check the errors in the batch file and then handle it accordongly... My wild guess... it could be permiissions issues.... You may need to setup a proxy account or make sure the owner of the job have sufficient rights to execute the batch properly... Another way to troubleshoot in this scenrio is to have an job output file.... The job output file could reflect the errors may occured...
What results are you expecting? There is no 'window' for the results to be shown on screeen anywhere when the SQL Agent job runs the batch file. Have you tried piping your results into a txt file? e.g. Dir > C:\
MyDirectoryList.txt or Dir >> C:\
MyDirectoryList.txt a single > will create/overwrite the output file, a double >> will append results to an existing file [Edit - after more info on question] Your SQL Agent service account will have to have permission to write to the location chosen in the FTP process. check this and then llok into handling the error within the batch file so that at least the error details are passed into a file to help debugging.