none
Error: To run a ssis package outside of sql server data tools you must install standard edition of integration services or higher

    Dotaz

  • Hi,

    If I run SSIS Execute sql task through DTEXEC package then its executing fine but if I run script task in package through DTEXEC - getting error as
    Error: To run a ssis package outside of sql server data tools you must install standard edition of integration services or higher.

    I am using:

    SQL Server 2016 Developer edition , Visual studio Shell (SSDT BI) 2015 , SQL Server Execute Package Utility
    Version 13.0.4466.4 for 32-bit, windows server 2016, SQL Server 2016 SP1.

    How to fix this ?


    • Upravený Venkatzeus čtvrtek 12. července 2018 11:56
    čtvrtek 12. července 2018 11:48

Všechny reakce

  • what was the TargetServerVersion set for the package when you created it from SSDT?

    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue
    Visakh
    ----------------------------
    My Wiki User Page
    My MSDN Page
    My Personal Blog
    My Facebook Page

    čtvrtek 12. července 2018 12:01
  • Hi Venkatzeus,

    You need to install SSIS service on your server, just add SSIS feature from SQL Server Installer.

    Dtexec Tool is fine to execute SSIS package with simple tasks outside developer tool, however you may not be able to execute the complex SSIS packages that contains any tasks / components like Script tasks, Script components, Sort / Aggregate/ Fuzzy Lookup transformations etc.

    Please install SSIS Service with Standard Edition or higher. In your scenario, you can install Develop Edition as your SQL Sever instance is develop edition.

    Running SSIS packages outside the Developer tools using DTEXEC.exe without installing the Integration services.

    Check if this issue persist.

    Regards,

    Pirlo Zhang 


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.


    pátek 13. července 2018 6:56
    Moderátor
  • Hi ,

    Thanks for the reply.

    SSIS Service has been installed for developer edition on server . But still the same issue.


    • Upravený Venkatzeus pátek 13. července 2018 8:16
    pátek 13. července 2018 8:07
  • Hi ,

    Thanks for the reply.

    SSIS Service has been installed for developer edition on server . But still the same issue.

    WHats the target server version you set in your SSDT project?

    I assume you installed SSIS service from 2016 version itself


    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue
    Visakh
    ----------------------------
    My Wiki User Page
    My MSDN Page
    My Personal Blog
    My Facebook Page

    pátek 13. července 2018 8:12
  • Hi, Thanks for the reply.

    SSDT target version was 2012.

    pátek 13. července 2018 8:18
  • Hi, Thanks for the reply.

    SSDT target version was 2012.

    Ok

    That explains it

    So my guess is that what might have happened is you might have had some references in Script Task which is 2012 version compatible. While running in the server using dtexec it would have incompatibility as server is in 2016 version

    Can you open the package in SSDT and set TargetServerVersion as 2016 and redeploy the package to your server and try running it? 


    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue
    Visakh
    ----------------------------
    My Wiki User Page
    My MSDN Page
    My Personal Blog
    My Facebook Page

    pátek 13. července 2018 8:32
  • HI,

    Tried this as well. But not working

    pátek 13. července 2018 8:57
  • HI,

    Tried this as well. But not working

    did you rebuild the script tasks after you changed targetserver version in SSDT to 2016?

    Also do you've multiple instances of SSIS installed on the machine?


    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue
    Visakh
    ----------------------------
    My Wiki User Page
    My MSDN Page
    My Personal Blog
    My Facebook Page

    pátek 13. července 2018 9:04
  • Hi Venkatzeus,

    What happens if you run the package via SQL Server Agent job?

    Please make sure you are using correct version and edition of Dtexec Tool.

    Try to execute the command with full path of Dtexec Tool.

    For example (32 bit):

    "C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn\dtexec.exe" -f ...

    Regards,

    Pirlo Zhang 


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.


    pátek 13. července 2018 9:20
    Moderátor
  • Hi Pirlo Zhang,

    Tried this as well. But no changes.

    čtvrtek 19. července 2018 12:32