/CONFIGFILE ignored?

Question

/CONFIGFILE ignored?

edwardelliott

SSCommitted

Points: 1863
More actions
June 22, 2009 at 9:31 am

#211206

Hi,
I have a server (sql 2005 sp 3) and am using sql agent to run the package. I have specified the correct config file to use under "Configuration Files" but it tries to use the one that is in the package xml (if I edit it manually it works but I don't want to do this as it gets rid of the point of having a config file).
If I run it using DTExec using the /CONFIGFILE parameter it still tries to use the one that was specified in the dev environment.
Does anyone know how to get SSIS to use the correct config file?
Thanks,
Ed

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Scott Coleman One Orange Chip Points: 27452 More actions · Answer 1

Using /CONFIGFILE on the dtexec command line does not turn off the configuration files set up in the package. All configuration items set up in the package (files, tables, environment variables) will be applied before command line switches. The idea is that the command line switches might be overriding a previous config item, so the command line goes last.

When the package is loaded all properties are set up with their design-time values. These may be overridden by config files, then by command line switches, then by parent package configuration. Whichever change was made last wins, but all config items will be used.

edwardelliott SSCommitted Points: 1863 More actions · Answer 2

Hi Scott, Thanks for the reply.

OK so I have taken the config file setting out of the package and now it isn't trying to use any dtsconfig at all - it just isn't reading the file passed in using /CONFIGFILE. Do you know any reason this wouldn't get read??

Cheers

ed

Scott Coleman One Orange Chip Points: 27452 More actions · Answer 3

I don't know any reason why it would just ignore the /CONFIGFILE parameter, my guess is that an error is occurring that you're overlooking (or is not being reported to you).

Someone has come up with a version of DTEXEC that does more detailed logging, called DTLoggedExec. It may help you determine what is going on.

http://dtloggedexec.davidemauri.it/MainPage.ashx

I've never used it, but it looks like it might help debug this. The logging example shown on their page includes detailed info on the configuration process, while the normal DTEXEC doesn't start logging until after configuration has finished (except for parent package configuration).

edwardelliott SSCommitted Points: 1863 More actions · Answer 4

Thanks Scott - using DTLoggedExec actually works so I don't know what is wrong but I will just use that, plus as well as working the output is about a thousand times more useful than DTExec.

ed