I am confused by your description, What is the run.cmd?

If I use a simple .Net console application exe, and "return" a value from
it, when run from the exec process task it will fail or succeed as expected
when the return set in the program value does not match the "Return code"
set in the task. If the return value does not match the task configured
return code, then the task is failed, and the on failure workflow is
followed as expected.

Just for info here is my simple test app-

using System;

namespace ConsoleReturn
{
/// <summary>
/// Summary description for ConsoleReturn.
/// </summary>
class ConsoleReturn
{
/// <summary>
/// The main entry point for the application.
/// </summary>
[STAThread]
static int Main(string[] args)
{
int ret = 0;

Console.WriteLine("ConsoleReturn.exe <return value>");

try
{
ret = Convert.ToInt32(args[0]);
Console.WriteLine("Return value " + ret.ToString() + " will be
returned.");
}
catch
{
ret = 0;
Console.WriteLine("No return value supplied. A default of 0 will be
used.");
}

return ret;
}
}
}


--
Darren Green
http://www.sqldts.com



"stoffi" <stoffi (AT) discussions (DOT) microsoft.com> wrote

To be honest I don't understand your batch file, but a simple test shows
that I can wrap my EXE inside a batch file and the Exec Process Task works
as expected.

Try breaking the process down and testing each step in isolation to see what
may hide the error.


--
Darren Green
http://www.sqldts.com


"stoffi" <stoffi (AT) discussions (DOT) microsoft.com> wrote

port.exe %1 %2 %3 %4 %5 %6 %7 >%filename%.log 2>%filename%.err