December 13, 2012 at 1:00 pm
I'm using ssis 2008 R2 running on local pc in test mode in BIDS
I've designed a package to process csv files that come to me from various sources in zipped format. Sometimes there are several batches of csv's that are zipped separately and then combined in an outer zip. So I might have say three csv's in A.zip and three in B.zip and then A and B have been zipped together in C.zip.
My package loops thru the folder I drop the zips into and extracts (say) C.zip. It gets A.zip and B.zip (and I then move C.zip away from that folder).
I then have a 'script task' that examines the folder for the existence of csv files. In this case it dosn't find any and I run an 'execute package task' to call the same package again.
Next time round the script task should find csv files and my work flow should move on. However the package only executes successfully the second time round up to the second instance of the script to test for csv's and then hangs.
I have csv files extracted and the zip file they came from has been moved ... then nothing ... the second instance of the script task is like its waiting for something.
Has anyone any ideas why this script file might work once and then not work the second time?
:hehe:
December 14, 2012 at 12:32 am
Maybe SSIS hates being called recursively? 🙂
Why don't you build a recursive function right into the script task? Unzip the file, check for .csv and if there are no csv files, call the zip function again.
That way you won't have to execute your SSIS package multiple times.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
December 14, 2012 at 3:42 am
Thank you for your response but . . .
Actually there's no problem with the ssis at all! It's just the user that's defective!
Let this be a lesson to all - if you use a MessageBox command in a ssis script task for debugging MAKE SURE YOU REMEMBER.
The fact is (I'm ashamed to say) that I had a MessageBox command in the script task that checked for the csv files. When I ran the package in BIDS the MessageBox was displayed but minimised on the task bar. So indeed the package was waiting for something - me. And I just didn't see it until after I'd posted a forum question - Doh!
My embarrasment is complete.
December 14, 2012 at 5:08 am
Don't worry, we all had this happening to us once 😀
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
December 18, 2012 at 2:55 pm
Or more than once... :crazy:
December 22, 2012 at 9:53 am
I am an SSIS newbie.
I have been trying to figure out this same
problem for days.
Thanks for the info.
Does anybody else feel that this is an absolutely
ridiculous behavior on SSIS's part ??????
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply