Good morning, all -
I'm having a very strange problem with SSIS on VS2017.
Yesterday, I was having a problem with a script that corrected. It was throwing an exception - giving me that wildly useful popup dialog[/sarc] - on sending an email and failing when attaching a signature that I subsequently corrected.
Today, I'm running a different package that has a script to return the oldest file in a selected folder. This script has worked perfectly for about five years now on earlier versions of VS; VS2015 or earlier. But, today, it threw an exception.
When I examined the contents of that popup dialog, I noticed something strange and verified it by examining my notes from yesterday; it was the exact same exception that I had already corrected - in a different script in a different package.
I told myself, "Self, this looks odd."
So, I put a breakpoint in the script to see what on Earth was causing this issue and stepped through the whole script. It ran through to completion successfully; no errors at all.
I stopped the package, removed the breakpoint and reran it. This time, it ran fine with no exceptions, even though I changed nothing.
There are four similar packages in this project that do the same basic thing, but on different folders. Each uses the same script, but with the baseline folder changed to provide the proper template for the path to the necessary files. Each of the four do this same thing;
- They throw an exception giving the error from yesterday from an entirely different project,
- I add a breakpoint to the script,
- Step through it, it runs fine,
- I make no changes,
- I remove the breakpoint and run again,
- It runs fine with no exceptions.
Any ideas on what may be happening? I get it to work, but I'm worried something else is going on somewhere, hidden from me, that may cause other, more serious problems down the road.
Many thanx for any assistance!