- In Microsoft SQL Server 2008, you use the DTExec.exe or DTExecUi.exe utility to run a SQL Server Integration Services (SSIS) package.
- You specify a configuration file by using the /ConfigFile option when you run the DTExec.exe or DTExecUi.exe utilities.
- The configuration file contains many configurations for objects in the package. However, the paths of the objects that are referenced in the configuration file do not exist in the current package. For example, you use a shared configuration file for many packages. However, some variables, connection managers, tasks, or other objects that are referenced in the shared configuration file are not contained in all packages.
Description: The package path referenced an object that cannot be found: "Path". This occurs when an attempt is made to resolve a package path to an object that cannot be found.
DTExec: Could not import the configuration file Configuration File.
Additionally, if you specify the shared configuration file in Business Intelligence Design Studio (BIDS) when you design the SSIS package, instead of specifying the shared configuration file by using the /ConfigFile option, the package can run successfully. The SupressConfigurationWarnings package setting does not affect this issue.
Note This issue does not occur in SQL Server 2005 Integration Services. In SQL Server 2005 Integration Services, the command provides warning messages as expected for the invalid values. However, the command can run successfully.
The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
Note When you use this method, the path of the configuration file is written to the package at the design time. However, some development environments may have different drive and folder structures compared to the production or test environments where the packages are deployed to run.
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
Artikel-id: 974076 - Laatst bijgewerkt: 22 sep. 2009 - Revisie: 1