April 24, 2017 at 1:45 pm
Hello everyone. I am unsure where to go next with this, so here I am. I have developed an SSIS package that executes fine in the BIDS studio but won execute as a job.
The main detail that seems to cause the problem is the first step where I connect to an XLSM file that opens and then save a couple on the sheets in there to a PDF file.
I have done it a few ways.
I wrote a console app that handles the opening and exporting.
I also wrote a script task that opens and exports the PDF.
Again, note this all completes correctly in BIDS. The package was developed on the same machine as the SQL Server. I have also tried executing the package from a proxy account.
My guess is it has something to do with when the file is exporting. I started out with it executing on a network share and move to the local machine.
Any ideas my friends?
April 24, 2017 at 1:54 pm
Make sure to select the option "32-bit runtime" on the job step.
Job Step -> Configuration Tab -> Advanced Tab
April 24, 2017 at 2:11 pm
Just tried. It was a no go.
Another note. In the task manager...the executable is open and the XLSM is open as well. I have to manuallly stop the job and both of those processes.
April 24, 2017 at 3:07 pm
Are you logging your package errors? Sounds like you need to do that to track down the error.
If the XLSM file is open and the other program then you know it makes it to <the whatever you ended up using to go to the PDF> . You said you did this a few ways so it's hard to say but that's one of the ways things can behave when waiting for user interaction or an answer to some prompt. Just one of a ton of possibilities.
Sue
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply