March 17, 2010 at 11:12 am
Hi,
I'm using a configuration file to set the path to an Excel spreadsheet, and then defining the Filename using an Expression from this variable in the Excel Connection Manager. It works great if the file exists, but if the file isn't there the SSIS package exits before running anything saying it can't connect to the file.
The first step in the SSIS package is a Script Task I wrote to verify the file exists, and if it doesn't it logs this and sends an email. This what I want to happen, but SSIS is erroring out right when the package starts. If the file exists all runs as it should.
I've enabled DelayValidation for the Excel Spreadsheet but is there anything else I can do to prevent SSIS from verifying the file exists until it actually needs to connect to it? I'd rather have my logic check this then SSIS so I can get warning that the file isn't there.
Thanks --
Sam
March 17, 2010 at 11:16 am
What happens after the Script Task - does the process try to run the dataflow, regardless of the existence of the file? Or have you used precedence constraints to send the flow down a different path if the file does not exist?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
March 17, 2010 at 11:20 am
Actually I found the fix... I had to enable DelayedValiation at the package level instead of on the Excel Connection. That seemed to work.
Thanks --
Sam
March 17, 2010 at 11:22 am
No problem, well done for figuring it out.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply