SSIS 2008 - Could not import the configuration file - by Mike Forman

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 424487 Comments
Status Closed Workarounds
Type Bug Repros 7
Opened 3/17/2009 12:18:37 PM
Access Restriction Public


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.
Sign in to post a comment.
Posted by ktrock 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.
Posted by qwert4444 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?
Posted by Microsoft 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.