July 14, 2016 at 11:36 am
Hi SSIS experts,
I was trying to assist a co-worker, but am at a loss. I'm hoping someone can assist me.
We have an SSIS package that has been deployed to MSDB (we exported a copy from MSDB to ensure it was the same package as what we found on the server). In the package is a task that creates an Excel file and emails the file - however these two tasks are disable in the package. Yet, when the job runs it creates the file and emails it out. How is this possible - why would the deployed package ignore the disabled tasks? I am up for any suggestions.
Thanks!!!
Shair
July 14, 2016 at 12:11 pm
two possibilities
1 - package runs with a config file or /set parameters that enable those steps when running on sql server - this may either be from the dtexec command line, or it can also be point 2 below on reverse
2 - package does have them enabled on the server, but it was designed using a configuration file that does disable them, and when you open the package that same configuration file is available and is loaded thus disabling the steps
edit the package using a normal text editor (assuming package is not encrypted) and manually look at the enabled flag of those tasks before opening it with VS.
and look for command line and/or config files
July 14, 2016 at 12:31 pm
Thanks for the quick response!
Going to check now and will respond back with results.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply