Microsoft KB Archive/920882

= 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 =

Article ID: 920882

Article Last Modified on 7/24/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Service Pack 1

-



Bug: #794 (SQL Hotfix)



Notice
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 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



SYMPTOMS
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 &quot;\Childxml.dtsConfig&quot;

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 &quot;C&quot; (.dtsConfig).

This issue does not occur in the original version of SQL Server 2005.



CAUSE
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.



RESOLUTION
A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
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, Itanium architecture-based versions


WORKAROUND
To work around this issue, use the lowercase file name for the XML configuration file of an SSIS package.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; 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

Keywords: kbtshoot kbexpertiseadvanced kbfix kbsql2005ssis kbhotfixserver kbqfe kbpubtypekc KB920882

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.