The task Transfer SQL Server Objects Task cannot run on this edition of Integration Services
Error code: 0xc0012024
Using "Integration Services Project" template in Business Intelligence Studio. Using platforms Visual Studio 2005 along with SQL Server 2005.
Getting the error while trying to execute package after loading it programmaticaly.
I've just one task "Transfer SQL Server Objects Task" on my Integration Services package. But when I try to execute it from VS 2005 project programmaticaly, it gives the above mentioned error.
The commands I use:
Package pkg = new Package();
pkg = a.LoadPackage(@"C:\Documents and Settings\abc\My Documents\Visual Studio 2005Projects\lSSIS\SSIS\Package.dtsx", null, true);
DTSExecResult dResult = pkg.Execute();
The the error comes like: error: 0xc0012024 The task Transfer SQL Server Objects Task cannot run on this edition of Integration Services. It requires higher level edition.
Please help me.
Thanks in advance,
Bhupesh
yes, integration services are installed on my computer as I can see a project Integration Services Project template when I open a new project from Business Intelligence Proejcts.
Do Integration Services are to be installed specifically while installing VS 2005 ? if it is the case then I've to install it seprately.
Waiting for reply.
Thanks in advance.
Bhupesh
There are two pieces that can be installed separately during SQL Server installation:
- SSIS Designer, this gives you SSIS Project inside VS, and lets you design and debug packages. During setup it is subset of the Tools group.
- SSIS itself - this gives you the service, and the ability to execute packages outside of the designer. To install, check SSIS checkbox during SQL setup.
The licensing requirements for these pieces are different. See the license for details, but generally speaking the first can be installed on any number of computers if you have one SQL license, while the second requires SQL license for every installation.
The error you get usually means you've only installed the first part.
as Michael Entin mention
"The licensing requirements for these pieces are different. See the license for details, but generally speaking the first can be installed on any number of computers if you have one SQL license, while the second requires SQL license for every installation. "
SSIS require a license for every installation, that means if you want to install SSIS on a web server, u need a separate license or am I misunderstanding something here?
Kevin
Your posting here helped me figure out my problem.
HOWEVER !
Unless I understand something wrong, it leaves us with three options:
- Give all our users remote login privileges to our SQL server to run the SSIS packages saved there - Great for system and data security!
- Purchase individual SQL licenses for all our workstations that need to run SSIS packages - Great for our finances!
- Install the visual studio / designer on all our workstations, which means people can erroneously modify things - Great for our IT deparment and very confusing for everybody else who has to use it!
None of these solutions are satisfactory to me.
With SQL 2000 / DTS we were able to write a package and had a VB.net frontend that ran the package - albeit with very little feedback to the user.
Is there a way to achieve something similar: where the VB apps on the workstations can trigger the SSIS service on the SQL server to run a package stored over there ?
Thanks.
DC.
