CODEWITHSUNDEEP
sqlservicessisintegrationbids
madguy
madguy

Reputation: 45

SSIS Deployment : The task <task name> cannot run on this edition of integration services. It requires a higher level edition

My SQL Server Database Engine is installed on a remote machine and the Development Tools(BIDS and SQL Server Management Studio) is installed on my local machine.

Using BIDS, I have created a SSIS package. It runs without any issue when executed from BIDS (By pressing F5). But, when I deployed this package onto the SQL Server and tried to execute it from SQL Server Management Studio, it gave me the following error :

The task <task name> cannot run on this edition of integration services. It requires a higher level edition.

After a little research, I found that the version of Integration Services installed with Database Engine on remote machine is different from what is installed with Dev. Tools on the local machine.

Also, the SQL Server is an Enterprise Edition whereas, the BIDS on local machine is Professional Edition.

1) Are the above 2 facts possible reasons for this error? 2) What are the ways (other than Tool upgrade) to get rid of this error?

Thanks

Upvotes: 2

Views: 5194

Answers (3)

rio
rio

Reputation: 763

On the remote server create a foolish import export pkg with the wizard in ssms and save the pkg some where... do the same on the dev machine and the open the pkgs with notepad and look to the difference in the headers (usually the problem is there).

Ex of a 2008 pkg

<?xml version="1.0"?><DTS:Executable xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:ExecutableType="SSIS.Package.2">
<DTS:Property DTS:Name="PackageFormatVersion">3</DTS:Property>
<DTS:Property DTS:Name="VersionComments"></DTS:Property>

Upvotes: 1

madguy
madguy

Reputation: 45

Thanks everyone!!!

Here is what worked for me :

When we run the package by right clicking it in the Object Explorer(in SSMS), the package runs on the machine where we start it. It does not run the package on the server machine. We either need to install SSIS on the machine where we are trying to run the package from, or run the package on the server machine directly.

Reference

I executed the package on a different dev machine (with SSIS installed), and it worked!!!

Upvotes: 0

Diego
Diego

Reputation: 36146

where qre you running the package from? Bear in mind that the package is run on the box that called it, not the one xhere it is stored.

Also you said: that the version of Integration Services installed with Database Engine on remote machine is different from what is installed with Dev I think thats the issue, you cant run a package built on 2008 on a 2005 server

Upvotes: 1

Related Questions