none
Integration Services class cannot be found. - SSIS - SQL Server 2014 RRS feed

  • Question

  • Hi,


    We are facing some problem in SSIS on SQL Server 2014. We had used MSSQL Server 2014 Standard Edition(64 bit) with sql server data tools visual studio 2012 (Shell).

    When we open / create any SSIS package, We receive attached error screen and unable to check or edit SSIS packages. Due to this SSIS Jobs are unable to run. But earlier we were able to run schedule jobs in same environment and we have not any changes on server.

    I am attaching snapshot of error for better understanding.

    Kindly help to resolve this issue. Thanks in Advance.

    Regards,
    Rajesh


    Rajesh Agravat

    Monday, August 3, 2015 10:06 AM

Answers

  • Hi Rajesh,

    Did you install SQL Server Integration Services on your server? Did you install a 32 bit version of SSIS on a 64-bit Windows operating system (OS)?

    Based on my research, the issue always occurs when you are using a 32 bit version of SSIS which is not compatible with your 64 bit OS. Please make sure you install SQL Server and select Integration Services for installation, then Setup would install all available 64-bit Integration Services features and tools. For more details, please refer to the following two documents:
    https://msdn.microsoft.com/en-us/library/ms143731(v=sql.120).aspx
    https://msdn.microsoft.com/en-us/library/ms141766.aspx

    Besides, if you really have a damaged Integration Services, here is the MSDN link that describes about Running an SSIS Package Programmatically on a Remote Computer. But we still need to have at least one server with Integration Services installed to be able to do what the MSDN article describes.

    Thanks,
    Katherine Xiong


    Katherine Xiong
    TechNet Community Support

    Thursday, August 6, 2015 3:23 AM
    Moderator

All replies

  • Hi Rajesh,

    Sorry to hear about this trouble, the error you are depicting is pertaining to the inability to edit a package and the error points to a damaged Integration Services engine.

    To remedy, I therefore suggest to simply re-install it from the same media you used to have it installed originally.


    Arthur

    MyBlog


    Twitter

    Monday, August 3, 2015 4:01 PM
    Moderator
  • Hi Arthur,

    Thanks for your reply! But, is there any other solution to this problem, as the package is installed on a production server, and if we need to reinstall it, other applications will be affected. Thank you once again.

    Regards,

    Rajesh.


    Rajesh Agravat

    Tuesday, August 4, 2015 2:28 PM
  • Hi,

    Is there any other solution to this problem, other than reinstalling the package? Your help is highly appreciated.

    Thanks & Regards,

    Rajesh.


    Rajesh Agravat

    Tuesday, August 4, 2015 2:32 PM
  • Hi Arthur,

    Thanks for your reply! But, is there any other solution to this problem, as the package is installed on a production server, and if we need to reinstall it, other applications will be affected. Thank you once again.

    Regards,

    Rajesh.


    Rajesh Agravat


    You should have your packages backed up elsewhere then re-deployed

    Arthur

    MyBlog


    Twitter

    Tuesday, August 4, 2015 11:25 PM
    Moderator
  • Hi Rajesh,

    Did you install SQL Server Integration Services on your server? Did you install a 32 bit version of SSIS on a 64-bit Windows operating system (OS)?

    Based on my research, the issue always occurs when you are using a 32 bit version of SSIS which is not compatible with your 64 bit OS. Please make sure you install SQL Server and select Integration Services for installation, then Setup would install all available 64-bit Integration Services features and tools. For more details, please refer to the following two documents:
    https://msdn.microsoft.com/en-us/library/ms143731(v=sql.120).aspx
    https://msdn.microsoft.com/en-us/library/ms141766.aspx

    Besides, if you really have a damaged Integration Services, here is the MSDN link that describes about Running an SSIS Package Programmatically on a Remote Computer. But we still need to have at least one server with Integration Services installed to be able to do what the MSDN article describes.

    Thanks,
    Katherine Xiong


    Katherine Xiong
    TechNet Community Support

    Thursday, August 6, 2015 3:23 AM
    Moderator