Passing arguments to Execute process task in ssis 2005
Hi, we are using third party tool checksum insted of SCD in our project.here if we select more than 50 columns in a check sum it is not calculating the check sum value for these columns in 64-bit System,for this to consider the check sum we have to run the executable file before this package in Master package.i am using Executeprocesstask beforore this package,for this in process window i am giving Executable file path and in Arguments i am passing like "D:Packages\RunningHistorical.dtsx /MAXCONCURRENT -1 /CHECKPOINTING OFF but i am getting error like In Executing "E:\Binn\DTExec.exe" "D:\Packages\RunningHistorical.dtsx /MAXCONCURRENT -1 /CHECKPOINTING OFF " at "", The process exit code was "6" while the expected was "0". plese help me how to pass arguments here. Thanks.............
May 11th, 2012 9:51am
Why don't you use the Execute Package Task?MCTS, MCITP - Please mark posts as answered where appropriate.
May 11th, 2012 10:21am
Hi PVENKAT, The error looks like the task was expecting a return code of 0 and your script returned 6. You can change the expected result in the task by changing the SuccessValue property. And here are some related threads, please refer to: http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/22229629-3f44-4fb7-afe0-dee53960ee8b http://social.msdn.microsoft.com/Forums/en/sqlintegrationservices/thread/4a2a758d-c0c2-4a65-b659-349d1b5622ff Thanks, Eileen
May 17th, 2012 5:09am
first try to execute process from command promp and after that write into execute process task. and add arguments to argument field in ssis execute process task.Regards, nishantcomp2512 Please mark posts as answered where appropriate
May 17th, 2012 8:44am
That's pretty bad advice, Eileen. "6" is not an expected success code for DTExec. (If this were some other application, your suggestion might be OK - with some explanation.) There's obviously a problem with the execution that DTExec is complaining about. Rvenkat - you need more information about what's going wrong with the execution. Here's what you can do: Create two new SSIS variables: StdOutput and StdError. Edit your Execute Process Task, and set the StandardOutputVariable property to User::StdOutput, and the StandardErrorVariable property to User::StdError. Place a breakpoint on the Execute Process Task. Specifically, right click on the EPT, select Breakpoints, and place one on the Post-Execute. Run the package. When the breakpoint is hit, open the Locals window, expand the Variables node, and examine what's in the StdOutput and StdError variables. Talk to me now on
May 17th, 2012 11:15am