Post reply

SSIS calling exe process then on success another dtsx package

  • July 27, 2009 at 11:51 am

    #136611

    Hello,

    I have a question regarding the order of operation within SSIS. I have a dtsx package which uses a Execute Process task to call an exe that does some file manipulation. Then using the Success constraint (the green arrow) this first dtsx package will call another dtsx package. This other dtsx package will look for text files that the exe is supposed to create. I sometimes run into an error which says that the text file does not exist.

    My question is does the Success constraint just reflect that the exe was just successfully called or that the exe has completely finished with no errors?

    Going from the error that I sometimes get, I am thinking that it is just on the calling of the exe. If this is true, then looking at the Execute Process Task's (which calls the exe) properties, I see that there is a Success Value and a TimeOut value and both of these are set to 0. Does anyone know how to incorporate the Success Value? Also how exactly does the TimeOut value work (I am guessing that the Success constraint will not be given until the time specified has elapsed)?

    Thanks

  • July 27, 2009 at 12:29 pm

    #1030687

    I believe it reflects whether the process returned an ERRORLEVEL other than zero. There is a field called SuccessValue in the process tab of the Execute Process Task editor, it is almost always zero. It has been the default forEVER that an applicatation that completed with no errors will return a zero for an errorlevel. Now I'm *guessing* that the application that you are using for the file manipulation may well report errors but still reports a zero ERRORLEVEL which would lead your process to choke when there is no file..

    i know that this isn't entirely clear.. If you try to start an EXE or another executable in a command shell and it fails to start the ERRORLEVEL will be non-zero.

    CEWII

  • July 27, 2009 at 6:19 pm

    #1030796

    When the error is reported, is it because the exe has failed (ie, the text files truly do not exist), or is it that the text file is in the process of being created and may still be locked?

    The absence of evidence is not evidence of absence.
    Martin Rees

    You can lead a horse to water, but a pencil must be lead.
    Stan Laurel

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply