Post reply

Error: The task "script task" cannot run on this edition of Integration Services.

  • May 11, 2006 at 7:43 am

    #172557

    We are running SQL 2005 Standard Edition 64bit in our lab and are getting this error:

    Error: The task "script task" cannot run on this edition of Integration Services. It requires a higher level edition.

    DTS_E_TASKPRODUCTLEVEL

    073668060

    0xC0012024

    We get this when trying to run a SSIS package (upgraded from a SQL2k DTS job) which contains an ActiveX script.  Is it true that script tasks are not supported in SQL 2005 Standard edition and is there any workaround?  Thanks.

  • May 11, 2006 at 4:05 pm

    #637416

    Hmm... this error seems familiar.  If memory serves, this would indicate that you're trying to run this from the command prompt instead of the BI Studio client tools.  What this means is that you have the client tools installed on the computer you're trying to run this from, but not SSIS itself.  I believe you need to run the SQL Server installer and just install SSIS on the computer you're trying to run this from... assuming my assumption that you're trying to run this from the command prompt is correct. 

  • May 15, 2006 at 8:59 am

    #637887

    Ryan,

    I'm keen to know if Robert's suggested fix worked for you.

    -Jamie

     

    Jamie Thomson
    http://sqlblog.com/blogs/jamie_thomson

  • May 16, 2006 at 5:40 am

    #638106

    Yes, we were running the job from a remote machine which did not have SSIS installed.  When the job is run directly on the server it works.  Thanks for your comments.

  • February 22, 2008 at 4:38 am

    #781039

    I've just hit this problem. Yes, my SSIS service is installed on a different machine to my client.

    What I don't understand is why I can run a package with file system task in debug mode with no problem, but as soon as I have a parent package that calls the file system package, the child package develops this error.

    I guess I'm hoping there is a way round this as I can't do my development on the same machine as the SSIS service, or install the service on my machine.

    Any ideas, anyone?

  • January 7, 2009 at 8:00 am

    #922551

    I'm encountering the same problem here when calling child packages. Have you been able to figure out how to tackle this issue?

  • January 7, 2009 at 10:15 am

    #922702

    We ended up following robertk's suggestion and set up a scheduled SQL job to run the SSIS package from a command like this:

    dtexec.exe /FILE "d:\Program Files\Microsoft SQL Server\90\DTS\Packages\mySSIS_job.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING V /CONSOLELOG NCOSGXMT

  • March 18, 2009 at 5:39 am

    #961728

    hi guys,

    The same issue i had when executing a child package from the parent package. In the child package the first control am using is the script editor to collect the vaues from the parent package. The error i got is as follows...Any ideas to solve this ..share friends

    Error: The task "Script Task" cannot run on this edition of Integration Services. It requires a higher level edition.

    Thanks

    vijay

  • March 18, 2009 at 5:49 am

    #961732

    Hi Guys,

    This is really a nice topic to discuss. Let me add my experience about the error. I have created a SSIS Package 2005, and in debug mode [VS IDE], I didn't get any error. When I deployed the same package in my machine as File System/SQL Server System I got the same error.

    I did some research and finally I came to know, if I need to run a package which is deployed in a Desktop/Server, it should have MS SQL Server Installed with SSIS Components. I have only MS SQL Client version, thats why I was getting the error. Then, I deployed the same package with no change in the Server Machine and it was working fine as expected.

    Regards,

    Ashok S

  • March 18, 2009 at 5:57 am

    #961740

    hi,

    The problem arises when i try to execute the parent child package.when i execute each package seperaetly from my system both works fine. I had used file system deployment of packages.

    Thanks

    vijay

  • March 18, 2009 at 12:28 pm

    #962164

    when you say you can run each package separetely and have them complete successfully, are you running them from a command prompt or are you running them from a job or Business Intelligence Dev Studio?

  • March 18, 2009 at 10:37 pm

    #962469

    hi,

    I had executed those packages seperately frm the BIDS only which gives positive result.The same packages when i tried run with parent child combination, it throws me error. Any ideas Share mate.

    Thanks

    Vijayalaya cholan k

  • March 19, 2009 at 12:21 am

    #962496

    I'm willing that if you try to run these without BIDS, you're going to see the error. I'm not 100% certain on this, but when a child package is called, it's probably called outside the context of BIDS. So, if you don't have Integration Services installed on the machine, you're going to see this error. Try running the child package via command line and I'm thinking it won't run, even though it'll run just fine in BIDS.

    If that's the case, verify that you have Integration Services installed (it's a separate component accessible in the SQL Server installer program). Good luck and let me know if that's it.

  • March 19, 2009 at 12:30 am

    #962498

    hi,

    I have SSIS installed in my system. The packages running fine when it was running seperaetly. SO parentchild execution must also run.But it fails with the script error.Why is it so ?

    Thanks

    Vijayalaya cholan .K

  • March 19, 2009 at 1:03 am

    #962505

    My hunch is that there's still something missing here. You said you only ran these packages from BIDS, but try dtexec.exe from the command prompt. Do you still get the same error message? This'll help me determine where to direct you.

    Time for bed, I'm guessing you're on a different side of the globe, but I'll answer your question in the morning. Good luck.

Viewing 15 posts - 1 through 15 (of 19 total)

You must be logged in to reply to this topic. Login to reply