February 12, 2016 at 2:29 am
Hi All,
I've had a task that I've been using on SSIS for about 6 months and has been working fine. Yesterday, however, it decided to not work and I have no idea why.
The dataflow has 5 Script Components (all sources), which grabs data from an Excel file. If I run the Script without any breakpoints, the components runs indefinitely (I left it over night yesterday when i went home and it quite literally spent 16 hours doing nothing).
I opened up one of the sources, and put a breakpoint on the very first line and started stepping through each line, however, it runs an if statement a few lines in (if (DateTime.TryParse(excelReader[0].ToString(), out dtInputDate))), and then never runs another line of code after. This happens in all 5 data sources (as they all run in a very similar fashion).
Does anyone have any idea Visual Basic suddenly decide it doesn't want to run anymore code, but continue to run? I've not changed anything on the package since last month, so I'm stumped and need to get it up and running before EoD.
Thanks!
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
February 12, 2016 at 4:11 am
Exception handling with a dialog box causing it to wait on user input?
February 12, 2016 at 6:08 am
Have there been any environment changes? Software updates? Permissions changes (including at network/file level)?
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.
February 12, 2016 at 6:09 am
In your debugging, were you able to detect whether the ExcelReader was retrieving any data?
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.
February 12, 2016 at 7:52 am
Environment did change late last month, as we installed sharepoint designer on my PC, but we removed it later on, as it didn't meet our needs. That did seem to break my Excel drivers on my PC, as I had to reinstall them, so seem that this is actually the crux of the problem.
The Excel Data source works fine, so does anyone know if a different driver or software is required for the ExcelReader to work? After further testing, the debugger just stops running code as soon as it uses the Excel reader, and running on another PC (not a long term solution, as I had to borrow a collegues) ran the package fine.
Thanks.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
February 22, 2016 at 3:43 am
Hi All,
Is anyone able to suggest which driver/files I may be missing to be able top get this operation to start running locally again? I've not had much success so far.
Many thanks!
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply