Hello all,I just installed the June CTP Client Tools on a fresh hard drive (no previous CTPs installed). I am trying to run a package that was written in the April CTP and runs successfully on other computers with the June CTP installed.When I run the package, it fails on an 'Execute Package Task', and I get the error message:"The task cannot run on this edition of Integration Services. It requires a higher level edition."I know the package is okay because it runs on other June CTP computers. Did I miss something in my install? Any suggestions?Thanks for your time,Jessica

Did you install SSIS on the PC in question or just tools. If just the tools then that is your problem as you must install SSIS in order to run packages outside of the designer. As a workaround you can set the execute package task to run in process instead of out of process and that will also allow the package to run. We have changed the default from out of process to in process for the next CTP to try and mitigate this issue somewhat, although running outside of the designer still won't work but that is by design.HTH,

That was the problem!Thanks!Jessica

this is SOS callhey.i have the same problem. like I have One is Production Server where we have installed complete SQL,SSAS<SSIS etc.I have anouther machine on which i have installed client tool only..on other machine i have made SSIS package ans save on local machine. its run fine from Visual studio,... when i run package.DTSX file it shows me the same error as above."The task ... cannot run on this edition of integration services. It requires a higher level edition."Is there any way that i can run SSSIS by command prompt or other??thanks in advance.Reply ASAPKalash.

As the response above from Matt states, you must install the SSIS component (not just the client tools) to be able to run the SSIS package outside of BIDS.John Welch | www.mariner-usa.com | www.agilebi.com

Hi I have a question regarding the workaround...I have an app that let's the user kick off a ssis package based on parameters they have selected. The package runs via cmd line...It's not feasible to install ssis on every client machine...can you explain the work around a bit more? Not sure I understand what you mean by "in process" instead of "out process"

When I've experienced this error, i've double checked that i'm launching the packages with the correct path to the correct version of dtexec.exe. Also, i've reopened the package in a later BIDS (i.e 2008, rather than 2005), which automatically prompted me to upgrade and convert it all. when resaved afterwards, with the right version of dtexec, everything worked.