SSIS Packages Connection Copy Error RRS feed

  • Question

  • In SSDT 2017, I get the following error when copying the connection from one package to another package. Connection is Project type connection.


    TITLE: Microsoft Visual Studio

    The SSIS designer could not initialize the pasted components for design-time operations.  


    At least one connection manager could not be pasted correctly.
    The connection manager with the name 'XXXXXXXXXXX 1' could not be pasted successfully.
    The connection manager could not be created.
    Object reference not set to an instance of an object. (Microsoft.DataTransformationServices.Design)

    Tuesday, June 18, 2019 2:48 PM

All replies

  • Hi there,

    you need to use Visual Studio and be in a SSIS project to copy the connections across




    Tuesday, June 18, 2019 2:57 PM
  • Hi scuderia82,

    There is a conceptual issue in the question.

    There are 2 types of connections in SSIS:

    • Project level.
    • Package level.

    It is possible to copy a Package level connection between different packages.

    A project level connection is one and only for the entire SSIS project. It is impossible to copy it to the individual package.

    Though it is possible to toggle connection type between package vs. project level. Right mouse click on a connection, and its context menu shows that option.

    Tuesday, June 18, 2019 3:00 PM
  • I can only use SSDT. Do I need to install Visual Studio separately?
    Tuesday, June 18, 2019 3:06 PM
  • Hi scuderia82,

    You do need both: Visual Studio (VS) and SSDT for that particular version of VS.

    Tuesday, June 18, 2019 3:08 PM
  • Which version should I choose? Can I use Community
    Tuesday, June 18, 2019 3:45 PM
  • I can copy Project Level connection in VS 2017 Enterprise.
    Tuesday, June 18, 2019 3:46 PM
  • I would refrain from using any "Community" tooling.

    You need a standard or better VS to do the task.




    Tuesday, June 18, 2019 3:49 PM
  • I have tested older VS.

    VS 2017 Enterprise 15.3.5 Success - Copied

    VS 2017 Enterprise 15.9.13 - Failed - Not Copied

    Tuesday, June 18, 2019 4:50 PM
  • Did you install them side-by-side?




    Tuesday, June 18, 2019 5:01 PM
  • VS 2017 Enterprise 15.3.5 - installed on windows server machine

    VS 2017 Enterprise 15.9.13 - installed My local computer

    Wednesday, June 19, 2019 5:34 AM
  • Hi scuderia82,

    Package level and project level connection managers
    A connection manager can be created at the package level or at the project level. The connection manager created at the project level is available all the packages in the project. Whereas, connection manager created at the package level is available to that specific package.

    So, there is no need to copy the project level connection manager.

    Please refer to Integration Services (SSIS) Connections .

    Best Regards,


    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

    Wednesday, June 19, 2019 5:41 AM