locked
DTExec: Could not import the configuration file RRS feed

  • Question

  • Hello everyone.

    I've developed a SSIS package that reads info from a config file. In BIDS 2008 it works like a charm.

    I've deployed the package on the SSIS server as always. I've then created a SQL Job that invokes this job and uses that config file during execution.
    This is the same process I've done so many times, same SSIS Server, same folder for config files, same user to invoke SQL Job... but every time I run the SQL Job, I get the following error:
    "DTExec: Could not import the configuration file BlaBlaBla.dtsConfig"

    I understand this is most likely a permission issue, but what permission is failinh here? Like I said earlier, I've done this so many times with the same servers / folders...

    Please please please HELP


    Thanks in advance,
    JB

    JB

    Tuesday, June 4, 2013 2:32 PM

Answers

  • Hi everyone,

    I finally sorted out the problem. Gotta thank BIDS 2008 for not working properly :-/
    So I had a local variable on the package setup as a string. On the config file, this same variable was setup as a int32 (totally my fault, must have been a stupid copy paste I did).
    But, BIDS2008 gave me absolutely NO WARNING, NO ERROR and the package ran perfectly on my local machine via BIDS.

    When deploying to the SSIS Server and trying to run the package with that config file, SQL Server looks at the config file, sees a variable typed as int32 with a string value and gives the error:
    "DTExec: Could not import the configuration file

    Thanks to anyone who replied to this!

    SuperJB


    JB


    • Marked as answer by SuperJB Thursday, June 6, 2013 9:43 AM
    • Edited by SuperJB Thursday, June 6, 2013 9:59 AM
    Thursday, June 6, 2013 9:43 AM

All replies

  • It must be due to the SSIS step in the Agent not running under the proxy that has access to the config directory. Consider creating a domain proxy that has the needed level of access.

    Arthur My Blog

    Wednesday, June 5, 2013 2:47 AM
  • Hello Arthur, 

    Thank you for your feedback.
    I have developed several other SSIS Packages, deployed them to the same SSIS Server, created the new SQL Job on a server where other SQL Jobs are already running, put the config file in the exact same folder where other config files are, set the SQL Job to run as the same owner as the other SQL Jobs and configured the Step (there is only one step in the SQL Job) to run as the same proxy account as all the other steps in the SQL Jobs.

    I understand the error is 99% due to some permission issue, but, given that everything is configured the same way as other SQL Jobs that are running, do you see anything else I may be missing?


    Thanks,
    JB

    JB

    Wednesday, June 5, 2013 8:19 AM
  • Hi JB,

    Please check whether the following KB article resolves your issue:
    FIX: Error message when you use the DTExec.exe or DTExecUi.exe utility to run a SQL Server 2008 Integration Services package by specifying a configuration file: “The package path referenced an object that cannot be found”

    Regards,
    Mike Yin

    If you have any feedback on our support, please click here


    Mike Yin
    TechNet Community Support

    Thursday, June 6, 2013 3:34 AM
  • Hi everyone,

    I finally sorted out the problem. Gotta thank BIDS 2008 for not working properly :-/
    So I had a local variable on the package setup as a string. On the config file, this same variable was setup as a int32 (totally my fault, must have been a stupid copy paste I did).
    But, BIDS2008 gave me absolutely NO WARNING, NO ERROR and the package ran perfectly on my local machine via BIDS.

    When deploying to the SSIS Server and trying to run the package with that config file, SQL Server looks at the config file, sees a variable typed as int32 with a string value and gives the error:
    "DTExec: Could not import the configuration file

    Thanks to anyone who replied to this!

    SuperJB


    JB


    • Marked as answer by SuperJB Thursday, June 6, 2013 9:43 AM
    • Edited by SuperJB Thursday, June 6, 2013 9:59 AM
    Thursday, June 6, 2013 9:43 AM