February 21, 2011 at 12:28 am
I do have the following problem.
I created an Upadte-Package in SSIS with 2 configuration files. Works fine on my local environment.
If I deploy the package to the SQL Server, the package still works, but anyhow if I change the configuration file it seems that the Execute Package Utility just ignores that configuration file and always uses the config file which was last time used in my local development environment.
Does anyone had the same issue before?
Thanks for your help.
cheers
February 24, 2011 at 1:22 am
Are you placing the config files at EXACTLY the same path as they existed in development? I have seen cases where it remembered the original values.. In the output from the run it would mention a warning about not finding the config file, once I put the config file in the right location it took it.
You configured the package to use configuration files at design-time by setting them up under package configurations? Just checking.
CEWII
February 26, 2011 at 6:19 am
In addition to what Elliot said make sure that either the SQL agent or the proxy account has access to the files. I suggest using a proxy account you don't want to be giving the agent account rights all over the place. Another thing to remember is not putting theses files in a my documents location or on a mapped drive since the server will most likely have different mappings.
HTH
February 28, 2011 at 12:57 am
Good thought Tom. I made a bit of an assumtion about access.. I typically have SQL logged in with an account that can do nearly anything. It may not be ideal but it happens a lot.. Checking out the log will help the OP determine what is going on..
CEWII
March 1, 2011 at 7:58 pm
Hi all,
I was following this thread as I am also using config files but they are still in the development stage on my system. So, for development purpose we need to provide a local path on the machine.I have provided "C:\mydocuments\abc.log" as the path for the log file. I was just wondering how can we provide exactly the same path as on the server for testing on the local machine?
Can't we can change the location/path of the config file when we deploy the packages on the sql server?
Thank You.
August 22, 2012 at 3:10 pm
I depolyed my package to the SQL Server. I want to change the configuration file at run time. When I do that using the Package Execution Utility, it still take the original values defined duing development.
The same applies if the try to change file at the job step that run the package. What am I missing?
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply