You are currently offline, waiting for your internet to reconnect

FIX: You cannot deploy a SQL Server 2005 Integration Services package if you use an XML configuration file whose file name contains an uppercase letter

Bug: #794 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.
This article has been archived. It is offered "as is" and will no longer be updated.
This article describes the following about this hotfix release:
  • The issues that are fixed by this hotfix package
  • The prerequisites for installing the hotfix package
  • Whether you must restart the computer after you install the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes
  • The files that are contained in the hotfix package
When you deploy an SSIS package to a new server in SQL Server 2005 Service Pack 1, you receive an error message that resembles the following:
The package is attempting to configure from the XML file "<Development Path>\Childxml.dtsConfig"
This problem occurs if the following conditions are true:
  • A SQL Server 2005 Integration Services (SSIS) parent package calls a child package by using the Execute Package task.
  • An XML configuration file stores the connection string of the child package.
  • The name of the XML configuration file contains an uppercase letter. In the error message that this article describes, the default file name extension of the XML configuration file contains a "C" (.dtsConfig).
This issue does not occur in the original version of SQL Server 2005.
This issue occurs because of a regression from SQL Server 2005 Service Pack 1. In SQL Server 2005 Service Pack 1, a change was made to convert the deployed configuration file name to lowercase letters. However, the lookup of the configuration file name is always case sensitive.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


This hotfix requires SQL Server 2005 Service Pack 1.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
SQL Server 2005 32-bit version
File nameFile versionFile sizeDateTimePlatform
SQL Server 2005, x64-based versions
File nameFile versionFile sizeDateTimePlatform
SQL Server 2005, Itanium architecture-based versions
File nameFile versionFile sizeDateTimePlatform
To work around this issue, use the lowercase file name for the XML configuration file of an SSIS package.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information
For more information about the naming schema for Microsoft 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

Article ID: 920882 - Last Review: 01/15/2015 16:41:27 - Revision: 3.0

  • kbnosurvey kbarchive kbautohotfix kbtshoot kbexpertiseadvanced kbfix kbsql2005ssis kbHotfixServer kbqfe KB920882