SSIS and WZUNZIP.exe
Before presenting my problem I just want to say hello to all of the members. As you can see I'm new here although I have been reading this group for some time now.I'm stuck on a problem...actually it's more of an annoyance then a problem, but still...I have a foreach loop with process task that uses wzunzip.exe and error tolerance (I don't want my job to stop because of few damaged zip files). So what's the annoyance? When a damaged zip file comes, my job continues to run normally, but when it's finished unpacking all of the files it is reported as if the job have failed, although everything was done. Setting property FailTaskIfReturnCodeIsNotSuccessValue to False is not an option for me, because I want to know whitch zip file is damaged.Thanks in advance
June 27th, 2008 11:37am

Nobody stumbled upon this issue?
Free Windows Admin Tool Kit Click here and download it now
June 28th, 2008 9:50am

The Execute Process task will report an error, since one occurred. Are you trying to prevent it there, or are you trying to prevent it from being reported at the package level? If it's the package level that is the problem, you need to set the Propagate system variable in the OnError event handler to FALSE. I posted a similar example on my blog yesterday: http://agilebi.com/cs/blogs/jwelch/archive/2008/06/29/continuing-a-loop-after-an-error.aspx. The use of the Sequence container and the combination of setting Propagate to FALSE and setting the MaximumErrorCount to 0 means that any error that occurs inside the Sequence container is never reported outside the Sequence container, and the package will report a successful completion.
June 29th, 2008 5:18pm

I have no problem continuing a loop after an error, I have set exceptable MaximumErrorCount and package executes normally. I have a process task with wzunzip and an execute sql task (in control flow) that inserts a custom message into a table when process task has failed. Everything works fine when I execute it from BIDS and when I execute it from a job it finishes all of the work (after an error happened) and then reports that job have failed even though it really didn't. That's what's really weird... Your example might be the solution for me...I will try it as soon as I get to work tommorow and report if it helps. TNX for your help.
Free Windows Admin Tool Kit Click here and download it now
June 29th, 2008 10:06pm

When I was preparing the sample, I was having the same issue you are describing - running it from DTEXEC would report a failure at the end. Changing the Propagate and the MaximumErrorCount on the Sequence container (not the Package) seemed to fix it so that the package reported success.
June 29th, 2008 10:16pm

Worked like a charm! Big thanks!
Free Windows Admin Tool Kit Click here and download it now
June 30th, 2008 5:57pm

I am working on unzipping a bunch of files in one directory. I have created a ForEach Loop with a Execute Process Task Set the Process Task Executable Property to C:\Program Files\WinZip\WZUNZIP.EXE The went and created an Expression Arguments = "-o -ybc " + @[User::FileName] + " C:\\WellCare\\UnZip\\" I get the following error: [Execute Process Task] Error: In Executing "C:\Program Files\WinZip\WZUNZIP.EXE" "-o -ybc C:\WellCare\WellCare_InFile\PHARMACY_07012008_07312008_10242008_1_1000000.txt.gz C:\WellCare\UnZip\" at "", The process exit code was "2" while the expected was "0". HELP PLEASE!!!
October 28th, 2008 6:53pm

Anonymous4515 did you ever figure out the solution to the issue you were having. I am coming across the same problem and have spent the last two days trying to track down a solution. Any help would greatly be appreciated.
Free Windows Admin Tool Kit Click here and download it now
November 17th, 2010 4:40pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics