SQL Server Home
SSIS 2008 - Could not import the configuration file
as By Design
3/17/2009 12:18:37 PM
User(s) can reproduce this bug
When an SSIS package run via the command line using dtexec.exe or a SQL Agent job uses a config file that contains variables not defined in the package, the package will fail with the error: DTExec: Could not import the configuration file <filename>
When running the package in Visual Studio, the package will execute successfully.
The package setting SupressConfigurationWarnings has no effect on this problem.
SQL Server 2008 - Enterprise Edition
Integration Services (DTS)
Windows Server 2008
Operating System Language
Steps to Reproduce
1. Create a new SSIS package in Visual Studio
2. Add two variables to the package (Variable1 and Variable2). The data type for both was string
3. Create a configuration file containing the Value property for both variables
4. Remove Variable2 from the package
5. Copy the package and configuration file to the server
6. Create a SQL agent job with a step to execute the package using the config file
7. Run the job
The package fails with the error: DTExec: Could not import the configuration file <file>
If you then add Variable2 back to the package, and redeploy it, the job will run sucessfully
The package should execute successfully with no error or warning messages
to post a comment.
Please enter a comment.
on 7/12/2010 at 12:17 PM
Good submission. This led me to discover that I had a variable in my configuration file spelled incorrectly.
on 3/31/2009 at 1:34 PM
We came across with the same issue above and is there any solution/workaround expect reconfigure all the packages to point to multiple configuration files?
on 3/17/2009 at 2:19 PM
Thank you for your submission. We will be reviewing your information and providing you with updates on our progress. Thank you for your interest in and support of SSIS.
to post a workaround.
Please enter a workaround.
on 5/25/2010 at 6:19 PM
I found that if the identity of the SQL Agent service cannot access the configuration folder (permissions) you will receive this error. Ensure your service account can read the configuration file path.
© 2014 Microsoft