I am using a CmdExec job to execute an .exe that handles alot of our companys repeated tasks. The .exe accepts a parameter that tells it was module to run. I have created a module that requires a second parameter. I created a CmdExec job and in the steps->Command: field I entered the following:
"file path to .exe" parameter1 parameter2
The first parameter is recognized fine. When it gets to the second parameter I get an error from the application telling me that the index was outside the bounds of the array. I have a job on a 2000 server that executes this job using a DTS Package and runs fine. We are converting and this is giving me an issue. Please let me know how to pass multiple parameters to an .exe from the sql job. thanks
asked Feb 11 '10 at 04:10 PM in Default
I suspect it's because the cmdexec step is only passing in the first parameter and your exe is trying to access the second one.
I had a problem with calling an exe in a job. It was more about capturing the result but I think you might find this method helps you with your problem too. Make the step a T-SQL step and call your exe like this:
Note the double quotes around the exe path because it has a space in and the double quotes around the whole command line. The exe is written in VB starts in Module1.Main which, instead of being a Sub, is function that returns an Integer. The convention is 0 means success and non-zero means failure.
This way you should crack your parameter problem and get the job to fail if the exe has a problem.
answered Feb 12 '10 at 04:50 AM