Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. 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”

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”

Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.

↑ Back to the top

Symptoms

Consider the following scenario:
  • 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.
In this scenario, when you run the command, you receive the following error message:
Code: 0x80012017

Source: Package

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.

↑ Back to the top

Resolution


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:
973602 Cumulative update package 4 for SQL Server 2008 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

↑ Back to the top

Workaround

To work around this issue, specify the shared configuration file in BIDS when you design the package.

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.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

References

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:

935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems



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:

822499 New naming schema for Microsoft SQL Server software update packages


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: kb, kbexpertiseadvanced, kbqfe, kbfix, kbsurveynew

↑ Back to the top

Article Info
Article ID : 974076
Revision : 6
Created on : 9/29/2020
Published on : 9/29/2020
Exists online : False
Views : 102