how to capture the error value when Execute Process Task batch job fails?

  • Hello,

    I'm using SSIS Execute Process Task to issue a 'reload file' command on a QlikView qvw.file using command line. I used this link to learn how to do:http://community.qlik.com/thread/30728 .

    <<<<elective reading>>>>>>

    This is working as follows:

    Executable: C:\Program Files\QlikView\Distribution Service\QVDistributionService.exe

    Arguments: /C "C:\Program Files\QlikView\Distribution Service\QVDistributionService.exe" -out="G:\Qlikview\Qlikview_Documents\Affiliate Reporting_reload.log" -r="G:\Qlikview\Qlikview_Documents\Affiliate Reporting.qvw"

    When I run this, a command is sent to QlikView to refresh(reload) a report file. After that's done the cmd window closes and the task completes. The subsequent task in my control flow is a Send Mail and on success I get an email.

    I need to make this a notch better. I want an email only on failure and I want an email issued only if the refresh command is run 2 or more times. So I need to understand how to handle for errors. I went looking for help from a colleague who told me to sabotage a document so I could see what kind of error cmd line will return when I type echo %errorlevel% . So, I did that and I get a 2. Apparently 0 is for success. But, I need to get this error returned to SSIS so that I can do something with it.

    At minimum I want SSIS to try to issue the reload file command at least once, because in reality, I'm running multiple Process Tasks for multiple reload file commands inside a sequence container, and sometimes one of them fails due to resource constraints.

    <<<<<Main Question>>>>>>>>

    How do you capture batch file request errors in SSIS so that I can issue a second or third reload request upon failure?

  • You could try Craig's approach, detailed here

    Steve.

  • http://www.sqlis.com/sqlis/post/Have-you-used-the-ExecutionValue-and-ExecValueVariable-properties.aspx Can I apply the steps here to Process task to return error back to ssis?

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

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