FIX: You receive an error message when you try to build a project for deployment and the project contains multiple packages that are configured to use a shared configuration file in SQL Server 2005 Integration Services (910419)


The information in this article applies to:

  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium Based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition
  • SQL Server 2005 Standard Edition for Itanium-based Systems
Bug #: 408202 (SQLBUDT)
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.

SUMMARY

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
  • Information about whether you must restart your computer after you install the hotfix package
  • Information about whether the hotfix package is replaced by any other hotfix package
  • Information about whether you must make any registry changes
  • The files that are contained in the hotfix package

SYMPTOMS

Consider the following scenario. You try to build a project for deployment in Microsoft SQL Server 2005 Integration Services (SSIS). The project contains multiple packages that are configured to use a shared configuration file. In this scenario, the deployment manifest file is not created in the deployment folder, and some of the package configuration files may not be copied to the deployment folder. Additionally, you receive the following error message:
Error 3 System.ApplicationException: Could not copy file "MUDWETLConfig.dtsConfig" to the deployment utility output directory "C:\MUDWETL\bin\Deployment". ---> System.IO.IOException: The file 'C:\MUDWETL\bin\Deployment\MUDWETLConfig.dtsConfig' already exists. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite) at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.CopyFiles(ICollection fileNames, String outputPath) --- End of inner exception stack trace --- at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.CopyFiles(ICollection fileNames, String outputPath) at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.CreateDeploymentUtility(IOutputWindow outputWindow)

CAUSE

This problem occurs because the build process tries to copy an XML file to the deployment destination. An existing file name already exists from the first package. Therefore, the file that is created again uses the same file name and the problem occurs.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft SQL Server 2005 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

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

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have Microsoft SQL Server 2005 installed to apply this hotfix.

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 after you apply this hotfix.

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 tool in Control Panel.SQL Server 2005 32-bit versions
File nameFile versionFile sizeDateTimePlatform
Dtspipeline.dll2005.90.1500.0600,28009-Nov-200504:19x86
Msmdlocal.dll9.0.1500.015,581,91209-Nov-200504:19x86
Msmdpp.dll9.0.1500.03,824,85609-Nov-200504:19x86
Msmdpump.dll9.0.1500.03,912,40809-Nov-200504:19x86
Msmdredir.dll9.0.1500.03,926,74409-Nov-200504:19x86
Msmdsrv.exe9.0.1500.014,559,44809-Nov-200504:19x86
Msmgdsrv.dll9.0.1500.05,935,32009-Nov-200504:19x86
Msolap90.dll9.0.1500.04,202,20009-Nov-200504:19x86
Nsservice.exe9.0.1500.018,64809-Nov-200504:19x86
Sqlaccess.dll2005.90.1500.0349,40009-Nov-200504:19x86
Sqlca.dll2005.90.1500.03,207,38409-Nov-200504:19x86
Sqldiscoveryapi_s.dll2005.90.1500.0527,06409-Nov-200504:19x86
Sqlncli.dll2005.90.1500.02,208,52809-Nov-200504:19x86
Sqlservr.exe2005.90.1500.028,769,04009-Nov-200504:20x86
SQL Server 2005 64-bit version
File nameFile versionFile sizeDateTimePlatform
Dtspipeline.dll2005.90.1500.01,054,93609-Nov-200518:50x64
Msmdlocal.dll9.0.1500.030,001,36809-Nov-200518:51x64
Msmdpp.dll9.0.1500.04,881,11209-Nov-200518:51x64
Msmdpump.dll9.0.1500.04,951,25609-Nov-200518:51x64
Msmdredir.dll9.0.1500.04,830,93609-Nov-200518:51x64
Msmdsrv.exe9.0.1500.029,326,04009-Nov-200518:51x64
Msmgdsrv.dll9.0.1500.08,907,99209-Nov-200518:51x64
Msolap90.dll9.0.1500.05,663,96009-Nov-200518:51x64
Nsservice.exe9.0.1500.018,64809-Nov-200518:50x86
Sqlaccess.dll2005.90.1500.0356,56809-Nov-200518:50x86
Sqlca.dll2005.90.1500.04,278,48809-Nov-200518:50x64
Sqldiscoveryapi_s.dll2005.90.1500.0745,68809-Nov-200518:50x64
Sqlncli.dll2005.90.1500.03,151,63209-Nov-200518:50x64
Sqlservr.exe2005.90.1500.039,466,71209-Nov-200518:51x64
SQL Server 2005 IA-64 bit version
File nameFile versionFile sizeDateTimePlatform
Dtspipeline.dll2005.90.1500.01,915,60809-Nov-200517:17IA-64
Msmdlocal.dll9.0.1500.048,409,30409-Nov-200517:18IA-64
Msmdpp.dll9.0.1500.06,469,84809-Nov-200517:17IA-64
Msmdpump.dll9.0.1500.06,519,51209-Nov-200517:17IA-64
Msmdredir.dll9.0.1500.06,071,51209-Nov-200517:17IA-64
Msmdsrv.exe9.0.1500.047,369,94409-Nov-200517:18IA-64
Msmgdsrv.dll9.0.1500.012,840,15209-Nov-200517:18IA-64
Msolap90.dll9.0.1500.07,683,80009-Nov-200517:17IA-64
Nsservice.exe9.0.1500.018,64809-Nov-200517:17x86
Sqlaccess.dll2005.90.1500.0351,44809-Nov-200517:17x86
Sqlca.dll2005.90.1500.010,563,28809-Nov-200517:18IA-64
Sqldiscoveryapi_s.dll2005.90.1500.01,924,31209-Nov-200517:17IA-64
Sqlncli.dll2005.90.1500.05,384,46409-Nov-200517:17IA-64
Sqlservr.exe2005.90.1500.072,186,58409-Nov-200517:18IA-64
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

WORKAROUND

To work around this problem, manually create the ProjectName.SSISDeploymentManifest file. Then, save the file in the Drive:\FullPathToTheSSISProject\Bin\Deployment folder. Use the following template as a guideline:
<?xml version="1.0" ?> 
<DTSDeploymentManifest GeneratedBy="<Domain>\<UserName>" GeneratedFromProjectName="<ProjectName>" GeneratedDate="<Date><Time>" AllowConfigurationChanges="true">
<Package>Package1.dtsx</Package> 
<Package>Package.dtsx</Package> 
<ConfigurationFile>cp.xml</ConfigurationFile> 
<ConfigurationFile>cc.xml</ConfigurationFile> 
</DTSDeploymentManifest>
Note In this template, <Domain> represents the domain name, <UserName> represents the user name, <ProjectName> represents the name of the project, <Date> represents the date, and <Time> represents the time.

STATUS

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 the terminology that Microsoft uses when it corrects software after the software is released, 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

Modification Type:MinorLast Reviewed:7/26/2006
Keywords:kbsql2005presp1fix kbsql2005ssis kbfix kbbug kbHotfixServer kbQFE kbpubtypekc KB910419 kbAudDeveloper kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.