Deployed package is not picking up dtsconfig file

  • Still learning SSIS.

    I have built a really simple package in BIDS2005

    SMTP server connection

    SendMailTask

    Sends me an email (bob@myaddress.com) - Works a treat in BIDS

    Build puts a copy of the dtsx in the Bin folder. Copied to the server and ran with DTEXEC - works a treat.

    In BIDS, Package configuration to get the TO address from the XML (fred@myaddress.com)

    Run from BIDS - works a treat

    Build puts the dtsx in the Bin folder, but not the dtsconfig

    Copy the dtsx from Bin and the dtsconfig from the project folder(i have put them in the same folder)

    Run with DTEXEC - Sends the email to Bob@myAddress.com, NOT Fred@myAddress.com

    What have I done wrong?

  • OK, update.

    opening the dtsx in notepad on the deployed version shows the dtsconfig path as being the full path of my laptop (the development machine). When I change the path to the server path, the config was picked up correctly.

    How do I build a package and have the dtsonfig be in a relative or different specified path?

  • Resolved but not happy:angry:

    from the command line I have to use the /conf[iguration] switch to specify the location of the config file which will then override the location specified in the dtsx. I can understand why you would want that functionality in the DTEXEC armoury, but it shouldn't be the default method - you would have to specify it for every config file for every package - makes it a right PITA for support!

  • aaron.reese (2/6/2013)


    Resolved but not happy:angry:

    from the command line I have to use the /conf[iguration] switch to specify the location of the config file which will then override the location specified in the dtsx. I can understand why you would want that functionality in the DTEXEC armoury, but it shouldn't be the default method - you would have to specify it for every config file for every package - makes it a right PITA for support!

    Which is probably why most people use an SSISConfig db to contain all config settings & indirect XML config to point to the SSISConfig db to use (dev/QA/Prod etc).

    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.

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

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