Rights needed for Surface Area Configuration tool?

Greetings.

Can a non-local admin run the Surface Area Configuration tool? Our dba wants to be able to use the tool, but is not a local admin on the SQL Server. Would we be able to assign a minimal set of rights to him without giving him full local admin?

Thanks.

Dale.

The SAC tool pretty much assumes that a local admin is setting up the configuration of the system. It uses WMI to access the services and it some cases needs to create a connection to the server within the contenct of the SQL Admin. If there is a standard setup you need for your SQL instances, you might consider having an administrator setup a configuration file and run it across your servers using the SAC command line utility.

Thank you,

Bill Ramos, Lead PM, SQL Manageability

Reusing package configuration in child packages

I currently have multiple (parent and child) packages using the same config file. The config file has entries for connections to a number of systems. All of them are not used from the child packages. Hence, my child package throws an error when it tries to configure using the same config file because it can't find the extra connections in my connection collection.

Does anyone have any ideas on the best way to go about resolving this? Is multiple config files (one for each connection) the only way?

Sachin

I have found that one file per connection is ultimately the best way to go. You may be able to have more than that, if you are sure you will always use the same configurations at the same time, but that seems to be more useful when you have some variables, perhaps a couple of file paths used for all of your packages to do logging or check pointing, but you need to be careful of not falling into the same trap again of over grouping. Keep it at the lowest level you can, it is just more flexible I have found, and copes better with change as well. (Deleted Post?)

|||

Darren

Looks like that might very well be the way to go then. I wonder if there is any way to include other config files into a single file, but that's for another day.

Thanks for the prompt reply.

Sachin

|||

Nice idea, support for XML Inclusions (XInclude) would do it (http://www.w3.org/TR/xinclude/).

One for MS Connect I think - http://connect.microsoft.com

Reusing package configuration file across all packages in a solution?

I have 5 packages in a solution.

For 1st package, I add a package configuration file (xml) named common.dtsConfig containing only Database Connection configurations.
For the same package, I add another package configuration file names first.dtsConfig containing configurations specific to 1st package.

Now for 2nd package, when I reuse from existing package configuration (common.dtsConfg) with same name, it allows me to do that. I also create a package specific configuration file for 2nd package.

And so on for all 5 packages.

This works fine for development. If my database user/password changes, I edit onyl one file i.e. common.dtsConfig.

But, when I want to create the deployment utility, it fails by throwing error that "cannot copy common.dtsConfig from <src_directory> to .\bin\Deployment because it already exists". Due to this failure, I do not get the DTSInstall.EXE.

Surprisingly, this was working with June CTP and has failed with September CTP.

What should I do to reuse the package configuration file across all packages for deployment with September CTP?

thanks,
Nitesh

This is a known problem.

We fail to create a deployment manifest if 2 packages in the project share the same config file

Problem Description:

Build of a SSIS project with duplicate package config files reports the following –

Error 1 System.ApplicationException: Could not copy file "C:\VITAL\Prosjekter\Test\SmallProject\connectionLOG.dtsConfig" to the deployment utility output directory "C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment". > System.IO.IOException: The file 'C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment\connectionLOG.dtsConfig' already exists.

and as a consequence the deployment manifest file is not created and some of the package config files may not be copied to the deployment folder.

Workaround:

Create Proj.SSISDeploymentManifest manually using below template. Additionally verify that all config files and miscellaneous files (if you have it in your project) are present in deployment folder and copy in those that are missing.

<?xml version="1.0" ?>

- <DTSDeploymentManifest GeneratedBy="REDMOND\usr" GeneratedFromProjectName="Integration Services Project15" GeneratedDate="2005-09-20T16:17:42.4195337-07:00" AllowConfigurationChanges="true">

<Package>Package1.dtsx</Package>

<Package>Package.dtsx</Package>

<ConfigurationFile>cp.xml</ConfigurationFile>

<ConfigurationFile>cc.xml</ConfigurationFile>

</DTSDeploymentManifest>

Resolution:
We will fix the problem in SP1.

For meantime we consider releasing a QFE

|||

I have 2 packages within a project that each have their own config file. When I build them and have the deployment package created, it doesn't put a DTSInstall.exe file in the directory.

I haven't created a deployment package since the June CTP, so I'm wondering if this has changed? I see some posts out there referring to DTUtil, should I be using that instead, or can I just copy the packages, change the config file settings and I'll be set?

Thanks in advance for your help.

-Chris

|||Just downloaded SP1. I dont see this fixed.|||

I am experiencing the same problem even after the installation of the Cumulative Hotfix 2153.

Regards,
Yitzhak Khabinsky

|||

Jamie, what is your word on the subject?

I know that you are using shared config files quite extensively.

Microsoft’s article (Article ID: 910419) mistakenly claims that it is fixed:

http://support.microsoft.com/?kbid=910419.

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

Regards,

Yitzhak

|||

Yitzhak,

Up to now I have never used the deployment wizard so have not come across the problem.

-Jamie

|||

The error actually is happening during the Build process

It is very easy to reproduce.

BIDS project should have a couple of SSIS packages. Shared *.dtsConfig file should be explicitly added to the project. After that the config file shows up under the Miscellaneous node on the project tree. Right click on the SSIS project node and select Build option. The error shows up in the Output window.

Regards,

Yitzhak

|||Hi has anyone checked out the hotfix to see if the issue is resolved?|||I'm still having this issue as well. I installed service pack 1 a while ago. Is MS going to fix this soon? I use SSIS a lot and have found source control options VERY lacking. My company paid a lot of money to get TFS, and I'm not seeing a lot of value where SSIS is concerned.|||

I checked it out today. It did NOT work for me. I still get the same error.

|||

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

|||

Rafael Salas wrote:

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

I concur with Rafael. We're a *little* bit more scientific than that because we use WiX to build our deployment MSIs. I never go near the deployment wizard.

The beauty of WiX is that it is MSBuild compliant which means it can run in conjunction with TFS so all our MSIs are getting built using continuous integration (that's in answer to the guy that mentioned TFS).

Sorry, I know that's not much use to the people on this thread that are experiencing grief. It may be worth posing on another thread the question "is this fixed in SP2". The guy on this thread that replied from Microsoft (Nick Berezansky) no longer works on the SSIS team.

-Jamie

|||

Not fixed in SP2 - just tested it.

I realize this may not be an optimal solution, but have you tried removing the *.dtsconfig from the project (that is, don't include it in the misc. files). When I do this, the project builds with no errors, and the deployment utility is created with the *.dtsconfig file in the Deployment folder. The file can still be under source control, through the source code explorer with TFS, or VSS, or whatever tool you are using.

In general, though, I'd agree with Jamie and Rafael on this. I haven't used the deployment wizard since the first iteration of my first SSIS project.

Reusing package configuration file across all packages in a solution?

I have 5 packages in a solution.

For 1st package, I add a package configuration file (xml) named common.dtsConfig containing only Database Connection configurations.
For the same package, I add another package configuration file names first.dtsConfig containing configurations specific to 1st package.

Now for 2nd package, when I reuse from existing package configuration (common.dtsConfg) with same name, it allows me to do that. I also create a package specific configuration file for 2nd package.

And so on for all 5 packages.

This works fine for development. If my database user/password changes, I edit onyl one file i.e. common.dtsConfig.

But, when I want to create the deployment utility, it fails by throwing error that "cannot copy common.dtsConfig from <src_directory> to .\bin\Deployment because it already exists". Due to this failure, I do not get the DTSInstall.EXE.

Surprisingly, this was working with June CTP and has failed with September CTP.

What should I do to reuse the package configuration file across all packages for deployment with September CTP?

thanks,
Nitesh

This is a known problem.

We fail to create a deployment manifest if 2 packages in the project share the same config file

Problem Description:

Build of a SSIS project with duplicate package config files reports the following –

Error 1 System.ApplicationException: Could not copy file "C:\VITAL\Prosjekter\Test\SmallProject\connectionLOG.dtsConfig" to the deployment utility output directory "C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment". > System.IO.IOException: The file 'C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment\connectionLOG.dtsConfig' already exists.

and as a consequence the deployment manifest file is not created and some of the package config files may not be copied to the deployment folder.

Workaround:

Create Proj.SSISDeploymentManifest manually using below template. Additionally verify that all config files and miscellaneous files (if you have it in your project) are present in deployment folder and copy in those that are missing.

<?xml version="1.0" ?>

- <DTSDeploymentManifest GeneratedBy="REDMOND\usr" GeneratedFromProjectName="Integration Services Project15" GeneratedDate="2005-09-20T16:17:42.4195337-07:00" AllowConfigurationChanges="true">

<Package>Package1.dtsx</Package>

<Package>Package.dtsx</Package>

<ConfigurationFile>cp.xml</ConfigurationFile>

<ConfigurationFile>cc.xml</ConfigurationFile>

</DTSDeploymentManifest>

Resolution:
We will fix the problem in SP1.

For meantime we consider releasing a QFE

|||

I have 2 packages within a project that each have their own config file. When I build them and have the deployment package created, it doesn't put a DTSInstall.exe file in the directory.

I haven't created a deployment package since the June CTP, so I'm wondering if this has changed? I see some posts out there referring to DTUtil, should I be using that instead, or can I just copy the packages, change the config file settings and I'll be set?

Thanks in advance for your help.

-Chris

|||Just downloaded SP1. I dont see this fixed.|||

I am experiencing the same problem even after the installation of the Cumulative Hotfix 2153.

Regards,
Yitzhak Khabinsky

|||

Jamie, what is your word on the subject?

I know that you are using shared config files quite extensively.

Microsoft’s article (Article ID: 910419) mistakenly claims that it is fixed:

http://support.microsoft.com/?kbid=910419.

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

Regards,

Yitzhak

|||

Yitzhak,

Up to now I have never used the deployment wizard so have not come across the problem.

-Jamie

|||

The error actually is happening during the Build process

It is very easy to reproduce.

BIDS project should have a couple of SSIS packages. Shared *.dtsConfig file should be explicitly added to the project. After that the config file shows up under the Miscellaneous node on the project tree. Right click on the SSIS project node and select Build option. The error shows up in the Output window.

Regards,

Yitzhak

|||Hi has anyone checked out the hotfix to see if the issue is resolved?|||I'm still having this issue as well. I installed service pack 1 a while ago. Is MS going to fix this soon? I use SSIS a lot and have found source control options VERY lacking. My company paid a lot of money to get TFS, and I'm not seeing a lot of value where SSIS is concerned.|||

I checked it out today. It did NOT work for me. I still get the same error.

|||

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

|||

Rafael Salas wrote:

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

I concur with Rafael. We're a *little* bit more scientific than that because we use WiX to build our deployment MSIs. I never go near the deployment wizard.

The beauty of WiX is that it is MSBuild compliant which means it can run in conjunction with TFS so all our MSIs are getting built using continuous integration (that's in answer to the guy that mentioned TFS).

Sorry, I know that's not much use to the people on this thread that are experiencing grief. It may be worth posing on another thread the question "is this fixed in SP2". The guy on this thread that replied from Microsoft (Nick Berezansky) no longer works on the SSIS team.

-Jamie

|||

Not fixed in SP2 - just tested it.

I realize this may not be an optimal solution, but have you tried removing the *.dtsconfig from the project (that is, don't include it in the misc. files). When I do this, the project builds with no errors, and the deployment utility is created with the *.dtsconfig file in the Deployment folder. The file can still be under source control, through the source code explorer with TFS, or VSS, or whatever tool you are using.

In general, though, I'd agree with Jamie and Rafael on this. I haven't used the deployment wizard since the first iteration of my first SSIS project.

Reusing package configuration file across all packages in a solution?

I have 5 packages in a solution.

For 1st package, I add a package configuration file (xml) named common.dtsConfig containing only Database Connection configurations.
For the same package, I add another package configuration file names first.dtsConfig containing configurations specific to 1st package.

Now for 2nd package, when I reuse from existing package configuration (common.dtsConfg) with same name, it allows me to do that. I also create a package specific configuration file for 2nd package.

And so on for all 5 packages.

This works fine for development. If my database user/password changes, I edit onyl one file i.e. common.dtsConfig.

But, when I want to create the deployment utility, it fails by throwing error that "cannot copy common.dtsConfig from <src_directory> to .\bin\Deployment because it already exists". Due to this failure, I do not get the DTSInstall.EXE.

Surprisingly, this was working with June CTP and has failed with September CTP.

What should I do to reuse the package configuration file across all packages for deployment with September CTP?

thanks,
Nitesh

This is a known problem.

We fail to create a deployment manifest if 2 packages in the project share the same config file

Problem Description:

Build of a SSIS project with duplicate package config files reports the following –

Error 1 System.ApplicationException: Could not copy file "C:\VITAL\Prosjekter\Test\SmallProject\connectionLOG.dtsConfig" to the deployment utility output directory "C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment". > System.IO.IOException: The file 'C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment\connectionLOG.dtsConfig' already exists.

and as a consequence the deployment manifest file is not created and some of the package config files may not be copied to the deployment folder.

Workaround:

Create Proj.SSISDeploymentManifest manually using below template. Additionally verify that all config files and miscellaneous files (if you have it in your project) are present in deployment folder and copy in those that are missing.

<?xml version="1.0" ?>

- <DTSDeploymentManifest GeneratedBy="REDMOND\usr" GeneratedFromProjectName="Integration Services Project15" GeneratedDate="2005-09-20T16:17:42.4195337-07:00" AllowConfigurationChanges="true">

<Package>Package1.dtsx</Package>

<Package>Package.dtsx</Package>

<ConfigurationFile>cp.xml</ConfigurationFile>

<ConfigurationFile>cc.xml</ConfigurationFile>

</DTSDeploymentManifest>

Resolution:
We will fix the problem in SP1.

For meantime we consider releasing a QFE

|||

I have 2 packages within a project that each have their own config file. When I build them and have the deployment package created, it doesn't put a DTSInstall.exe file in the directory.

I haven't created a deployment package since the June CTP, so I'm wondering if this has changed? I see some posts out there referring to DTUtil, should I be using that instead, or can I just copy the packages, change the config file settings and I'll be set?

Thanks in advance for your help.

-Chris

|||Just downloaded SP1. I dont see this fixed.|||

I am experiencing the same problem even after the installation of the Cumulative Hotfix 2153.

Regards,
Yitzhak Khabinsky

|||

Jamie, what is your word on the subject?

I know that you are using shared config files quite extensively.

Microsoft’s article (Article ID: 910419) mistakenly claims that it is fixed:

http://support.microsoft.com/?kbid=910419.

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

Regards,

Yitzhak

|||

Yitzhak,

Up to now I have never used the deployment wizard so have not come across the problem.

-Jamie

|||

The error actually is happening during the Build process

It is very easy to reproduce.

BIDS project should have a couple of SSIS packages. Shared *.dtsConfig file should be explicitly added to the project. After that the config file shows up under the Miscellaneous node on the project tree. Right click on the SSIS project node and select Build option. The error shows up in the Output window.

Regards,

Yitzhak

|||Hi has anyone checked out the hotfix to see if the issue is resolved?|||I'm still having this issue as well. I installed service pack 1 a while ago. Is MS going to fix this soon? I use SSIS a lot and have found source control options VERY lacking. My company paid a lot of money to get TFS, and I'm not seeing a lot of value where SSIS is concerned.|||

I checked it out today. It did NOT work for me. I still get the same error.

|||

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

|||

Rafael Salas wrote:

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

I concur with Rafael. We're a *little* bit more scientific than that because we use WiX to build our deployment MSIs. I never go near the deployment wizard.

The beauty of WiX is that it is MSBuild compliant which means it can run in conjunction with TFS so all our MSIs are getting built using continuous integration (that's in answer to the guy that mentioned TFS).

Sorry, I know that's not much use to the people on this thread that are experiencing grief. It may be worth posing on another thread the question "is this fixed in SP2". The guy on this thread that replied from Microsoft (Nick Berezansky) no longer works on the SSIS team.

-Jamie

|||

Not fixed in SP2 - just tested it.

I realize this may not be an optimal solution, but have you tried removing the *.dtsconfig from the project (that is, don't include it in the misc. files). When I do this, the project builds with no errors, and the deployment utility is created with the *.dtsconfig file in the Deployment folder. The file can still be under source control, through the source code explorer with TFS, or VSS, or whatever tool you are using.

In general, though, I'd agree with Jamie and Rafael on this. I haven't used the deployment wizard since the first iteration of my first SSIS project.

Reusing package configuration file across all packages in a solution?

I have 5 packages in a solution.

For 1st package, I add a package configuration file (xml) named common.dtsConfig containing only Database Connection configurations.
For the same package, I add another package configuration file names first.dtsConfig containing configurations specific to 1st package.

Now for 2nd package, when I reuse from existing package configuration (common.dtsConfg) with same name, it allows me to do that. I also create a package specific configuration file for 2nd package.

And so on for all 5 packages.

This works fine for development. If my database user/password changes, I edit onyl one file i.e. common.dtsConfig.

But, when I want to create the deployment utility, it fails by throwing error that "cannot copy common.dtsConfig from <src_directory> to .\bin\Deployment because it already exists". Due to this failure, I do not get the DTSInstall.EXE.

Surprisingly, this was working with June CTP and has failed with September CTP.

What should I do to reuse the package configuration file across all packages for deployment with September CTP?

thanks,
Nitesh

This is a known problem.

We fail to create a deployment manifest if 2 packages in the project share the same config file

Problem Description:

Build of a SSIS project with duplicate package config files reports the following –

Error 1 System.ApplicationException: Could not copy file "C:\VITAL\Prosjekter\Test\SmallProject\connectionLOG.dtsConfig" to the deployment utility output directory "C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment". > System.IO.IOException: The file 'C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment\connectionLOG.dtsConfig' already exists.

and as a consequence the deployment manifest file is not created and some of the package config files may not be copied to the deployment folder.

Workaround:

Create Proj.SSISDeploymentManifest manually using below template. Additionally verify that all config files and miscellaneous files (if you have it in your project) are present in deployment folder and copy in those that are missing.

<?xml version="1.0" ?>

- <DTSDeploymentManifest GeneratedBy="REDMOND\usr" GeneratedFromProjectName="Integration Services Project15" GeneratedDate="2005-09-20T16:17:42.4195337-07:00" AllowConfigurationChanges="true">

<Package>Package1.dtsx</Package>

<Package>Package.dtsx</Package>

<ConfigurationFile>cp.xml</ConfigurationFile>

<ConfigurationFile>cc.xml</ConfigurationFile>

</DTSDeploymentManifest>

Resolution:
We will fix the problem in SP1.

For meantime we consider releasing a QFE

|||

I have 2 packages within a project that each have their own config file. When I build them and have the deployment package created, it doesn't put a DTSInstall.exe file in the directory.

I haven't created a deployment package since the June CTP, so I'm wondering if this has changed? I see some posts out there referring to DTUtil, should I be using that instead, or can I just copy the packages, change the config file settings and I'll be set?

Thanks in advance for your help.

-Chris

|||Just downloaded SP1. I dont see this fixed.|||

I am experiencing the same problem even after the installation of the Cumulative Hotfix 2153.

Regards,
Yitzhak Khabinsky

|||

Jamie, what is your word on the subject?

I know that you are using shared config files quite extensively.

Microsoft’s article (Article ID: 910419) mistakenly claims that it is fixed:

http://support.microsoft.com/?kbid=910419.

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

Regards,

Yitzhak

|||

Yitzhak,

Up to now I have never used the deployment wizard so have not come across the problem.

-Jamie

|||

The error actually is happening during the Build process

It is very easy to reproduce.

BIDS project should have a couple of SSIS packages. Shared *.dtsConfig file should be explicitly added to the project. After that the config file shows up under the Miscellaneous node on the project tree. Right click on the SSIS project node and select Build option. The error shows up in the Output window.

Regards,

Yitzhak

|||Hi has anyone checked out the hotfix to see if the issue is resolved?|||I'm still having this issue as well. I installed service pack 1 a while ago. Is MS going to fix this soon? I use SSIS a lot and have found source control options VERY lacking. My company paid a lot of money to get TFS, and I'm not seeing a lot of value where SSIS is concerned.|||

I checked it out today. It did NOT work for me. I still get the same error.

|||

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

|||

Rafael Salas wrote:

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

I concur with Rafael. We're a *little* bit more scientific than that because we use WiX to build our deployment MSIs. I never go near the deployment wizard.

The beauty of WiX is that it is MSBuild compliant which means it can run in conjunction with TFS so all our MSIs are getting built using continuous integration (that's in answer to the guy that mentioned TFS).

Sorry, I know that's not much use to the people on this thread that are experiencing grief. It may be worth posing on another thread the question "is this fixed in SP2". The guy on this thread that replied from Microsoft (Nick Berezansky) no longer works on the SSIS team.

-Jamie

|||

Not fixed in SP2 - just tested it.

I realize this may not be an optimal solution, but have you tried removing the *.dtsconfig from the project (that is, don't include it in the misc. files). When I do this, the project builds with no errors, and the deployment utility is created with the *.dtsconfig file in the Deployment folder. The file can still be under source control, through the source code explorer with TFS, or VSS, or whatever tool you are using.

In general, though, I'd agree with Jamie and Rafael on this. I haven't used the deployment wizard since the first iteration of my first SSIS project.

Reusing package configuration file across all packages in a solution?

I have 5 packages in a solution.

For 1st package, I add a package configuration file (xml) named common.dtsConfig containing only Database Connection configurations.
For the same package, I add another package configuration file names first.dtsConfig containing configurations specific to 1st package.

Now for 2nd package, when I reuse from existing package configuration (common.dtsConfg) with same name, it allows me to do that. I also create a package specific configuration file for 2nd package.

And so on for all 5 packages.

This works fine for development. If my database user/password changes, I edit onyl one file i.e. common.dtsConfig.

But, when I want to create the deployment utility, it fails by throwing error that "cannot copy common.dtsConfig from <src_directory> to .\bin\Deployment because it already exists". Due to this failure, I do not get the DTSInstall.EXE.

Surprisingly, this was working with June CTP and has failed with September CTP.

What should I do to reuse the package configuration file across all packages for deployment with September CTP?

thanks,
Nitesh

This is a known problem.

We fail to create a deployment manifest if 2 packages in the project share the same config file

Problem Description:

Build of a SSIS project with duplicate package config files reports the following –

Error 1 System.ApplicationException: Could not copy file "C:\VITAL\Prosjekter\Test\SmallProject\connectionLOG.dtsConfig" to the deployment utility output directory "C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment". > System.IO.IOException: The file 'C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment\connectionLOG.dtsConfig' already exists.

and as a consequence the deployment manifest file is not created and some of the package config files may not be copied to the deployment folder.

Workaround:

Create Proj.SSISDeploymentManifest manually using below template. Additionally verify that all config files and miscellaneous files (if you have it in your project) are present in deployment folder and copy in those that are missing.

<?xml version="1.0" ?>

- <DTSDeploymentManifest GeneratedBy="REDMOND\usr" GeneratedFromProjectName="Integration Services Project15" GeneratedDate="2005-09-20T16:17:42.4195337-07:00" AllowConfigurationChanges="true">

<Package>Package1.dtsx</Package>

<Package>Package.dtsx</Package>

<ConfigurationFile>cp.xml</ConfigurationFile>

<ConfigurationFile>cc.xml</ConfigurationFile>

</DTSDeploymentManifest>

Resolution:
We will fix the problem in SP1.

For meantime we consider releasing a QFE

|||

I have 2 packages within a project that each have their own config file. When I build them and have the deployment package created, it doesn't put a DTSInstall.exe file in the directory.

I haven't created a deployment package since the June CTP, so I'm wondering if this has changed? I see some posts out there referring to DTUtil, should I be using that instead, or can I just copy the packages, change the config file settings and I'll be set?

Thanks in advance for your help.

-Chris

|||Just downloaded SP1. I dont see this fixed.|||

I am experiencing the same problem even after the installation of the Cumulative Hotfix 2153.

Regards,
Yitzhak Khabinsky

|||

Jamie, what is your word on the subject?

I know that you are using shared config files quite extensively.

Microsoft’s article (Article ID: 910419) mistakenly claims that it is fixed:

http://support.microsoft.com/?kbid=910419.

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

Regards,

Yitzhak

|||

Yitzhak,

Up to now I have never used the deployment wizard so have not come across the problem.

-Jamie

|||

The error actually is happening during the Build process

It is very easy to reproduce.

BIDS project should have a couple of SSIS packages. Shared *.dtsConfig file should be explicitly added to the project. After that the config file shows up under the Miscellaneous node on the project tree. Right click on the SSIS project node and select Build option. The error shows up in the Output window.

Regards,

Yitzhak

|||Hi has anyone checked out the hotfix to see if the issue is resolved?|||I'm still having this issue as well. I installed service pack 1 a while ago. Is MS going to fix this soon? I use SSIS a lot and have found source control options VERY lacking. My company paid a lot of money to get TFS, and I'm not seeing a lot of value where SSIS is concerned.|||

I checked it out today. It did NOT work for me. I still get the same error.

|||

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

|||

Rafael Salas wrote:

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

I concur with Rafael. We're a *little* bit more scientific than that because we use WiX to build our deployment MSIs. I never go near the deployment wizard.

The beauty of WiX is that it is MSBuild compliant which means it can run in conjunction with TFS so all our MSIs are getting built using continuous integration (that's in answer to the guy that mentioned TFS).

Sorry, I know that's not much use to the people on this thread that are experiencing grief. It may be worth posing on another thread the question "is this fixed in SP2". The guy on this thread that replied from Microsoft (Nick Berezansky) no longer works on the SSIS team.

-Jamie

|||

Not fixed in SP2 - just tested it.

I realize this may not be an optimal solution, but have you tried removing the *.dtsconfig from the project (that is, don't include it in the misc. files). When I do this, the project builds with no errors, and the deployment utility is created with the *.dtsconfig file in the Deployment folder. The file can still be under source control, through the source code explorer with TFS, or VSS, or whatever tool you are using.

In general, though, I'd agree with Jamie and Rafael on this. I haven't used the deployment wizard since the first iteration of my first SSIS project.