December 17, 2008 at 4:00 pm
Hello all,
I'm experiencing a weird situation where a foreach container (enumerator: foreach file) always ends abruptly after processing the 29th text file. What the 29th or 30th file is doesn't matter - it seems to be tied simply to the count. These are simple fixed width text files and no error is produced - the package simply moves on to the next step.
I don't see any logical flaw within the container that would cause it to end early - I was thinking that it might have to do with some type of limit on the number of open file connections, etc. Maybe a property somewhere that is set too low.
Has anyone ever experienced anything like this - any thoughts or suggestions for things to check would be greatly appreciated.
Thanks in advance for your help!
December 19, 2008 at 2:07 pm
What pattern are you using to search for the files? If its just .txt then i don't see any issue. but if you are using any pattern search then it might be possible that its not able to find that pattern in the filename.
Have you tried printing the filename in script task just to see if its actually finding all the files O.K.?
December 22, 2008 at 10:22 am
The pattern was simply *.txt.
I think I figured out a workaround. I went through all the steps in the loop and disabled/enabled them one at a time until I found the one that seemed to be causing the problem. When it was disabled all the files processed correctly. The step in question copied the files to another directory and then deleted them from the current directory (move operation).
I took this step and put it in its own loop that fired off immediately after the original loop and - so far - no problems. This makes me think that the error was somehow network related (too many operations going on at the same time). We have some old network technologies at my work so it wouldn't suprise me.
Anyway - I'm happy with a workaround - assuming it holds up.
Thanks.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply